firstrun
First-time setup for uSpec. Prompts for MCP provider and environment (Cursor, Claude Code, Codex), syncs skills to the chosen platform, then configures your Figma template library. Use when the user mentions "firstrun", "first run", "setup", "setup library", "configure templates", or "link templates".
92
88%
Does it follow best practices?
Impact
100%
1.88xAverage score across 3 eval scenarios
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 well-crafted skill description that clearly communicates what the skill does (first-time setup involving MCP provider selection, skill syncing, and Figma template configuration) and when to use it (with an explicit 'Use when...' clause listing multiple natural trigger terms). It is specific, complete, and distinctive, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: prompts for MCP provider and environment, syncs skills to the chosen platform, and configures Figma template library. These are clear, actionable steps. | 3 / 3 |
Completeness | Clearly answers both 'what' (first-time setup: prompts for MCP provider/environment, syncs skills, configures Figma template library) and 'when' (explicit 'Use when...' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms users would say: 'firstrun', 'first run', 'setup', 'setup library', 'configure templates', 'link templates'. These cover common variations of how a user would invoke this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — it targets a very specific niche (first-time uSpec setup) with unique trigger terms like 'firstrun' and 'setup library'. Unlikely to conflict with other skills due to the specificity of the domain and triggers. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable setup skill with excellent workflow clarity including a progress checklist, validation steps, error recovery guidance, and clear conditional branching for different MCP providers and environments. The main weakness is moderate verbosity — some explanatory phrases and repeated context could be trimmed — and the document is fairly long for a single file, though the complexity of the multi-path workflow partially justifies this.
Suggestions
Trim explanatory rationale sentences (e.g., 'catching a broken connection early avoids wasting time on setup that will fail later') — Claude doesn't need motivation, just instructions.
Consider extracting the JavaScript font-detection code and the JSON config schema into referenced files to reduce the SKILL.md length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes some verbosity that could be tightened — e.g., the rationale in Step 1b ('catching a broken connection early avoids wasting time...') and some redundant explanations about what FILE_KEY is used for. However, most content is necessary given the multi-path workflow. | 2 / 3 |
Actionability | Highly actionable with specific MCP tool calls, exact bash commands, executable JavaScript code for font detection, concrete JSON output schema, and precise error messages to display. Every step has copy-paste ready guidance. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with a progress checklist, clear sequencing, explicit validation at Step 1b (MCP connection verification), error handling with user-facing messages at multiple steps (sync failure, missing templates, missing library URL), and conditional branching clearly documented for each MCP provider. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear headings and a checklist, but it's a long monolithic document (~180 lines of detailed instructions). The JavaScript code block and JSON schema could potentially be referenced from separate files, though for a setup skill this level of inline detail is somewhat justified. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- redongreen/uSpec
- Commit
b1213ef
- 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.