endor-setup
Onboarding wizard for Endor Labs. Guides users through prerequisites, MCP server configuration, authentication, namespace setup, and running their first scan. Use when the user says "endor setup", "configure endor", "endor auth", "set up endor", "install endor", "endor onboarding", or when any MCP tool fails with an auth or namespace error. Do NOT use when the user already has a working setup — route to specific skills instead.
90
88%
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 an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive natural trigger terms, explicit 'Use when' and 'Do NOT use when' clauses, and clear boundaries to distinguish it from other Endor Labs skills. The description is concise yet thorough, serving as a strong example of how to write skill descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'prerequisites, MCP server configuration, authentication, namespace setup, and running their first scan.' These are clear, actionable steps rather than vague language. | 3 / 3 |
Completeness | Clearly answers both 'what' (onboarding wizard guiding through prerequisites, config, auth, namespace, first scan) and 'when' (explicit 'Use when...' clause with specific trigger phrases and error conditions). Also includes a 'Do NOT use when' clause which adds further clarity. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'endor setup', 'configure endor', 'endor auth', 'set up endor', 'install endor', 'endor onboarding'. Also includes contextual triggers like 'auth or namespace error'. These are realistic phrases users would naturally type. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Endor Labs onboarding/setup with clear trigger terms. The 'Do NOT use when the user already has a working setup — route to specific skills instead' clause explicitly delineates boundaries against other Endor-related skills, minimizing conflict risk. | 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 onboarding wizard with excellent actionability and workflow clarity — clear steps, executable commands, validation checkpoints, and good conflict detection. The main weaknesses are moderate verbosity (some explanatory text Claude doesn't need, a congratulations template, and tool reference tables) and the monolithic structure that could benefit from splitting reference material into separate files.
Suggestions
Move the 'Available MCP Tools After Setup' table and the 'Troubleshooting' table into separate reference files (e.g., TROUBLESHOOTING.md, TOOLS.md) and link to them from the main skill.
Remove explanatory asides that Claude already knows (e.g., 'npx comes bundled with Node.js', 'The `-y` flag auto-confirms the download') to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient for a multi-step onboarding wizard, but includes some unnecessary verbosity — e.g., explaining what `-y` does, explaining that npx comes bundled with Node.js, the 'Available MCP Tools After Setup' table at the end, and the Step 6 'Success' congratulations template. Some tightening is possible without losing clarity. | 2 / 3 |
Actionability | Highly actionable throughout — provides executable bash commands, complete JSON configuration blocks for both workflows, specific verification commands, and concrete troubleshooting solutions. Every step has copy-paste ready content. | 3 / 3 |
Workflow Clarity | Excellent multi-step sequencing with clear numbered steps, explicit validation checkpoints (Step 5 verify setup with a specific test), conflict detection (Step 2.3), feedback loops (re-run init if namespace wrong), and a comprehensive troubleshooting table. The auth conflict warning and mutual exclusivity note are strong safety guardrails. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and logical sections, but it's quite long (~200+ lines) and could benefit from splitting detailed reference material (troubleshooting table, MCP tools table, CI/CD auth) into separate files. Everything is inline in a single monolithic document. | 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
- endorlabs/skills-ideas
- Commit
344e7ff
- 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.