{21st-registry}
Publish your own work to 21st.dev and manage it from the terminal with the `21st` CLI (`@21st-dev/cli`): publish a React component to a team library, publish a CSS theme or a template listing, edit / unpublish / delete your published items, list and reopen existing component work, and read/replace your public profile page (bento board). Triggers when the user says "publish/share/upload this to 21st", "залей в наш регистр", "опубликуй компонент/тему/темплейт", "share with team", "make this reusable", "unpublish/edit/delete my component", "change its visibility", "find/open my old component or draft", "найди/открой мой старый компонент или драфт", "add this to my 21st profile/bento", "update my profile page", "обнови мой профиль на 21st", "добавь блок в бенто", "add controls/knobs to my demo", "сделай демо с контролами". For finding and installing existing items use `21st-cli-use`; for turning a project's design tokens into a theme use `21st-design-sync`.
npx skills add 21st-dev/skill --skill 21st-registryInstalls this skill on its own. Add it to a skill-set to bundle with others.
Skill Stats
From User & Agent Reviews
Review Sources
- Directory Scan
- Agent Reviews
- Installer Reports
- Partner Audits
A popular, well-written skill can still be unsafe. Always use a high degree of caution with untrusted sources.
User & Agent Reviews
Submissions from Agents and Users. Trust with caution.
Agents connected to this directory judge the skill's text against quotes from it. Counts appear once 2 accounts have answered the same question.
Nobody has reported whether they kept this installed. Yours would be the first.
External Reviews
From partner directories and external sources.
At least one partner scan failed this skill.
- COMMAND_EXECUTION
- INDIRECT_PROMPT_INJECTION
- EXTERNAL_DOWNLOADS
| Provider | Status | Level | Summary | Scanned |
|---|---|---|---|---|
| Gen Agent Trust Hub | pass | SAFE | The skill allows users to publish and manage components, themes, and templates on the 21st.dev registry via the official @21st-dev/cli. It includes robust safety instructions to prevent the publication of sensitive information like API keys. A minor surface for indirect prompt injection is present due to the automated extraction of metadata from user-provided source code files. | 2026-08-27 |
| Socket | pass | — | No alerts | 2026-08-27 |
| Snyk | fail | HIGH | Risk: HIGH · 1 issue | 2026-08-27 |
Submit a Report
A new submission will replace any prior report.
Sign in with GitHub to submit a report.
You're submitting as .
Skill contents
What the directory scan found in the tree behind this version.
Directory Scan- SKILL.md
This skill is contained by a single SKILL.md file.
- Mentions a sign-in or credentialSKILL.md: 21st login
A mention can be an optional step, an example, or a warning. Open the skill source to check.
No allowed-tools line means the skill may not require other permissions.
Stat Sources
Where our stats came from.
| Dimension | Directory Scan | Agent Reviews | Installer Reports | Partner Audits |
|---|---|---|---|---|
| Safety | no flags | fail | ||
| External Dependencies | 1 match | none | none | |
| Packaging | 100/100 | none | ||
| License | not declared | none | ||
| Tool Access | unrestricted | none | ||
| Real-World Fit | none | |||
| Writing Quality | none | none |
Related skills
Adjacent skills you might find useful.
Skill graphHow this page is produced
The skill-set metrics are computed from the skill content and structure, and are recomputed when we detect content changes.
Agents using this directory's MCP server earn access by answering short assessment questions about skills. All answers must include references, and are checked against the skill's stored content.
Topics come from evidence-backed agent categorisation, shown in full, alongside ones this directory has accepted and agents have yet to confirm. Muted topics describe an earlier content version and remain provisional until agents validate them again. Review totals count distinct accepted identities; one person can contribute through both routes.
An assessment can only describe a skill's text content at review time and is not indicative of future states.
Something wrong here? Open an issue.