Borrowing it
Nothing to install: this file belongs to posit-dev/py-shiny-site. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/posit-dev/py-shiny-site/main/.claude/skills/writing-component-pages/SKILL.mdgit clone --depth 1 https://github.com/posit-dev/py-shiny-siteWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/posit-dev/py-shiny-site/writing-component-pages)<a href="https://agentmods.dev/skills/posit-dev/py-shiny-site/writing-component-pages"><img src="https://agentmods.dev/badge/skills/posit-dev/py-shiny-site/writing-component-pages/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/posit-dev/py-shiny-site/writing-component-pages"><img src="https://agentmods.dev/badge/skills/posit-dev/py-shiny-site/writing-component-pages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.04889 |
| Opus 5 | $0.00031 | $0.02445 |
| Sonnet 5 | $0.00012 | $0.00978 |
| Haiku 4.5 | $0.00006 | $0.00489 |
Grade A, and why
writing-component-pages scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Component Pages
Overview
A component page is a directory under components/{inputs,outputs,display-messages,layout}/<name>/
containing an index.qmd plus a set of app-*.py example files. The index.qmd
front matter is data-driven: EJS templates in components/_partials/ turn it into
the rendered page (gallery card, live preview, tabbed Core/Express code, variations,
kitchen sink). Get the file names and front-matter keys right and the build does the rest.
Reference implementations to copy from:
- Minimal input:
components/inputs/action-button/(example + kitchen sink) - Rich output with variations:
components/outputs/data-grid/
Anatomy of a component directory
components/inputs/<name>/
index.qmd # required — page content + front matter
app-preview.py # required — gallery-card thumbnail app (Core style)
app-detail-preview.py # the live "Preview" app shown atop the example
app-core.py # Core-mode example (shown in "Core" tab)
app-express.py # Express-mode example (shown in "Express" tab)
app-kitchensink-core.py # optional — every-parameter demo (Core)
app-kitchensink-express.py # optional — every-parameter demo (Express)
app-variation-<slug>-core.py # optional — one set per variation
app-variation-<slug>-express.py
app-variation-<slug>-preview.py # dedicated live Preview app for that variation
thumbnail.png # optional — static image for the kitchen-sink block
File-role cheat sheet:
| File | Rendered as | Style |
|---|---|---|
app-preview.py |
Gallery-list card (via appPreview: + make docs-static-previews) |
Core, module-level app_ui, viewport-filling (vh-100 d-flex justify-content-center align-items-center) |
app-detail-preview.py |
Live standalone app at top of #example (the "Preview" tab) |
Core, module-level app_ui; may use ## file: app.py multi-file marker |
app-core.py / app-express.py |
Static code blocks in the Core/Express tabs, each with an "Open in editor" shinylive link | Idiomatic Core / Express; mark the key line with a trailing # << comment |
app-variation-*-{core,express}.py |
One entry in the #variations block |
Same as core/express |
app-kitchensink-*.py |
Linked from the #kitchen-sink block |
All parameters exercised |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 362 lines · 62 tokens per session scan A a41a751b0836
writing-component-pages is a skill published in the GitHub repository posit-dev/py-shiny-site (22 stars, last pushed 26d ago), licensed MIT. It adds 62 tokens to every session and 4,889 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…