Unified setup entrypoint for install, diagnostics, and MCP configuration
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/setup/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description provides a basic overview of the skill's purpose but lacks the explicit trigger guidance needed for Claude to reliably select it from a large skill library. The terms used are somewhat technical and don't capture the natural language users would employ when needing setup help.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user needs to set up the environment, troubleshoot installation issues, or configure MCP servers'
Include natural user phrases such as 'getting started', 'first time setup', 'configuration problems', 'not working', or 'initialize'
Expand the specific actions to be more concrete, e.g., 'Installs dependencies, runs diagnostic checks, configures MCP server connections, and validates environment setup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (setup) and lists three actions (install, diagnostics, MCP configuration), but these are high-level categories rather than concrete specific actions like 'run dependency checks' or 'configure server connections'. | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'install', 'diagnostics', and 'setup', but 'MCP configuration' is technical jargon. Missing common user phrases like 'set up', 'configure', 'troubleshoot', 'initialize', or 'getting started'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Setup' and 'install' are fairly generic terms that could overlap with other installation or configuration skills. 'MCP configuration' adds some specificity but the overall description could still conflict with general setup utilities. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent routing/dispatcher skill that efficiently documents a unified setup entrypoint. It provides clear usage examples, explicit routing rules, and appropriately delegates to sub-skills without unnecessary explanation. The content is well-organized and respects token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only the necessary routing logic and usage examples without explaining what setup wizards or MCP servers are. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready command examples and explicit routing rules. The routing logic is unambiguous with clear argument-to-command mappings. | 3 / 3 |
Workflow Clarity | For this simple routing/dispatch skill, the workflow is crystal clear: check first argument, route to appropriate sub-command. No multi-step validation needed as this is a simple dispatcher. | 3 / 3 |
Progressive Disclosure | Appropriately structured as a routing overview that delegates to other skills (omc-setup, omc-doctor, mcp-setup). References are one level deep and clearly signaled. | 3 / 3 |
Total | 12 / 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 | |
48ffaac
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.