Setup Wizard — Configure environment for all skills
68
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/setup/SKILL.mdQuality
Discovery
22%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 description is too vague to be useful for skill selection. It fails to specify what configuration actions are performed, what environment aspects are configured, or when Claude should choose this skill. The phrase 'for all skills' is ambiguous and doesn't help distinguish this from other potential setup-related skills.
Suggestions
Add specific concrete actions like 'Installs dependencies, creates configuration files, validates API keys, and sets up project structure'
Include a 'Use when...' clause with trigger terms like 'Use when the user mentions first-time setup, project initialization, environment configuration, or onboarding'
Clarify what 'all skills' means - list the types of skills or systems being configured to improve distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Configure environment') without listing any concrete actions. It doesn't specify what configuration involves or what 'all skills' means in practice. | 1 / 3 |
Completeness | The 'what' is extremely vague ('configure environment') and there is no 'when' clause or explicit trigger guidance. Users cannot determine when this skill should be selected. | 1 / 3 |
Trigger Term Quality | 'Setup' and 'Configure' are somewhat natural terms users might say, but 'Wizard' is more of a UI pattern than a trigger term. Missing common variations like 'install', 'initialize', 'bootstrap', 'onboarding', or 'first-time setup'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Setup Wizard' and 'Configure environment' are somewhat specific to initial configuration tasks, but 'for all skills' is overly broad and could conflict with individual skill setup processes or general configuration tasks. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides clear, actionable commands for environment setup. The main weakness is the lack of explicit validation/verification guidance in the workflow - users should know how to confirm their setup succeeded and what to do if it fails.
Suggestions
Add a verification step after configuration, e.g., 'After running export commands, run `/setup check` to verify configuration succeeded'
Include brief error handling guidance, such as what to do if `/setup check` reports issues
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section serves a purpose - quick start commands, command reference table, and brief workflow description. No padding or concepts Claude already knows. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands throughout. The quick start section has executable bash commands, and the command table gives specific invocations with clear descriptions. | 3 / 3 |
Workflow Clarity | The 'How It Works' section lists steps but lacks validation checkpoints or error handling guidance. For a setup wizard that configures environments, there should be explicit verification steps (e.g., 'run /setup check after configuring to verify'). | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines, the content is well-organized with clear sections: Quick Start for immediate use, Commands table for reference, and How It Works for understanding. No need for external file references given the scope. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
2a8c94e
Table of Contents
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.