design-extract
Extract design tokens (color / typography / spacing) from imported source code, screenshots, or Figma exports into the canonical token bag token-map consumes.
64
76%
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
Fix and improve this skill with Tessl
tessl review fix ./plugins/_official/atoms/design-extract/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
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.
Why it was flagged
SKILL.md describes reading outsider-provided inputs such as `figma/tree.json` from `figma-extract` (figma-migration) or a folder of externally sourced screenshot images, which the daemon runner then “scans…extracts CSS, Tailwind, and JavaScript token evidence” into `code/tokens.json`; this implies runtime ingestion of outsider-authored free text from those files into the agent’s LLM context (via the extracted token evidence).
- Repository
- nexu-io/open-design
- Commit
f2760fd
- Audited
- Security analysis
Is this your skill?
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.