Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
76
96%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
The canonical home for this skill is shadcn in shadcn-ui/ui
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The skill explicitly instructs the agent to fetch and read external component documentation and example URLs (e.g., "Run npx shadcn@latest docs <component>" and the `add`/`view` commands which accept arbitrary registry URLs, plus the MCP "view_items_in_registries" tool), meaning untrusted public registry/GitHub/raw docs are ingested and can directly influence install, merge, and update actions.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill explicitly instructs the agent at runtime to fetch component docs/examples (e.g. the example URL pattern https://raw.githubusercontent.com/... referenced by `npx shadcn@latest docs` and "Fetch these URLs to get the actual content") and to use that fetched content to drive how the agent composes/edits code, meaning remote content can directly control agent instructions.
45116fd
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.