create-property
Generate a visual property annotation in Figma showing each configurable property axis with component instance previews. Use when the user mentions "property", "properties", "property annotation", "create property", or wants to document a component's configurable properties visually.
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines a specific capability (generating visual property annotations in Figma), provides explicit trigger guidance with natural keywords, and occupies a distinct niche. It follows the recommended pattern of stating what the skill does followed by a 'Use when...' clause with concrete trigger terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists specific concrete actions: 'Generate a visual property annotation in Figma showing each configurable property axis with component instance previews.' This clearly describes what is being created and how it manifests visually. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate a visual property annotation in Figma showing configurable property axes with component instance previews) and 'when' (explicit 'Use when...' clause with specific trigger terms and intent description). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'property', 'properties', 'property annotation', 'create property', 'configurable properties', and 'Figma'. These cover natural variations a user would say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche of Figma property annotations with component instance previews. The combination of 'Figma', 'property annotation', and 'configurable property axis' makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with complete, executable code and a well-structured workflow with validation checkpoints and error recovery. However, it is extremely verbose — helper functions are duplicated across nearly every script template, and the sheer volume (~2000+ lines) makes it a poor use of context window. The content would benefit enormously from factoring shared code into referenced files and reducing inline repetition.
Suggestions
Extract the repeated helper functions (loadAllFonts, loadFontWithFallback, findNestedChild, findControllingBoolRawKey) into a shared utilities reference file and reference them once, rather than duplicating in every script template.
Move the individual rendering script templates (6a, 6a-ctx, 6a-matrix, 6b, 6b-ctx, 6c, 6e-i through 6g) into separate referenced files (e.g., templates/6a.md) to reduce the main skill file to a navigable overview.
Consolidate the MCP adapter section — the font-loading workaround explanation and replacement patterns could be a single referenced document rather than inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~2000+ lines, with massive code blocks that are largely repetitive (the same loadAllFonts, loadFontWithFallback helper functions are duplicated in nearly every script template). The MCP adapter section alone is substantial, and many patterns could be factored into shared references rather than repeated inline. | 1 / 3 |
Actionability | The skill provides fully executable JavaScript code for every step, with concrete placeholder patterns, specific Figma API calls, and copy-paste-ready script templates. Every operation has a complete, runnable implementation. | 3 / 3 |
Workflow Clarity | The workflow has a clear numbered checklist with explicit validation steps (Step 5 audit, Step 10 visual validation with up to 3 fix iterations), error recovery (try/catch with chapter.remove() rollback), and a well-sequenced multi-step process with dependencies clearly stated between steps. | 3 / 3 |
Progressive Disclosure | The skill references an external instruction file (agent-property-instruction.md) for detailed rules, which is good progressive disclosure. However, the SKILL.md itself is a monolithic wall of code — the 6a/6a-ctx/6a-matrix/6b/6b-ctx/6c/6e/6f/6g script templates could be split into separate referenced files rather than inlined, which would dramatically improve navigability. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (2617 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- redongreen/uSpec
- Commit
4eae941
- Reviewed
Table of Contents
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.