Phoenix Storybook

What it does

When your agent uses it

• Touching .stories
• Tasks that involve LLM observability
• Tasks that involve Pull requests

Example prompts

• “Use the phoenix-storybook skill to convention for creating, modifying, and reviewing production-faithful Storybook stories in the Phoenix frontend…”
• “/phoenix-storybook”

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

1. 1Render production truth. Render the shipped component with its real
2. 2Three roots, grouped by subject. Every title starts with
3. 3Titles match paths. Design System/Overlays/Popover lives at
4. 4Tag every story on three axes, as plain string literals: provenance
5. 5One entry per piece of content. A file with one sidebar story tags it
6. 6Open on a compact Default, then the option grids. A foundational
7. 7States are their own axis, crossed with other options in small
8. 8Layers are shown open. A menu, popover, tooltip, or dialog story shows
9. 9Both themes, no horizontal scroll. Choose themeLayout deliberately;
10. 10No superfluous comments or docblocks. A story docblock renders on the
11. 11Removal goes through review. Propose each deletion or consolidation
12. 12Run pnpm lint:storybook (from js/app) after any story change. It

What it can do on your machine

Read from SKILL.md and the folder at commit e471315. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • pnpm

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Phoenix Storybook loads about 1.9k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 160 tokens; SKILL.md has 830 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~160

When it runs · the whole SKILL.md, loaded when a task matches

~1.9k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~19k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 830 words (~1,880 tokens).

name

phoenix-storybook

metadata.internal

true

Read the full SKILL.md on GitHub

Files

SKILL.md and 16 other files (references) in .agents/skills/phoenix-storybook of Arize-ai/phoenix.

• SKILL.md
• references/component-audit.md
• references/content-length.md
• references/docblocks-and-comments.md
• references/domain-stories.md
• references/entry-shape.md
• references/files-and-titles.md
• references/merging-and-removal.md
• references/option-grids.md
• references/overlays.md
• references/review.md
• references/storybook-config.md
• references/tags.md
• references/taxonomy.md
• references/themes.md
• references/toasts.md
• references/verification.md

Open the folder on GitHubat commit e471315