Loading the registry…
Create or update a DESIGN.md design-system document (machine-readable YAML token front matter plus human-readable markdown rationale) so that design agents and tools share a single source of truth for colors, typography, spacing, shapes, and components. Invoke this skill whenever the user wants to generate, scaffold, refine, audit, validate, or update a DESIGN.md file; whenever they describe a visual identity, brand, palette, or design system in natural language ("a playful coffee app with warm colors", "make it feel like Stripe", "extract a design system from this URL"); whenever they paste a brand URL, screenshot, Figma reference, brand PDF, or color palette and ask for a structured design system; or whenever they mention "design tokens", "design system", "DESIGN.md", "Stitch", "tokens.json", "Tailwind theme", "Figma variables", "style guide", or "brand guidelines" -- even if they don't use those exact words. Also use when an existing DESIGN.md needs to be edited, extended with new tokens or components, validated against the spec, or migrated from an ad-hoc style guide.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
2 critical findings reported by cisco-skill-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'niranjan94/claude-marketplace (design-tokens)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'niranjan94/claude-marketplace (design-tokens)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
2 findings · 0.5s
v2.0.11
13 findings · 8.4s
v0.3.74
2 findings · 0.7s
v0.1.0
0 findings · 2.8s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 2.8s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 16, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 17 findings above stand exactly as their scanners reported them, at full severity.