endor
Main Endor Labs security router. Use when the user says "endor", "endor labs", or asks a general security question without specifying a particular endor command. Routes ambiguous requests like "check my security", "help with this dependency", or "what security tools are available" to the right specialized skill. Do NOT use when the user names a specific command like /endor-scan, /endor-check, /endor-fix, etc. — those skills handle themselves directly.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 router skill description that excels at completeness and distinctiveness. It clearly defines its role as a dispatcher for ambiguous Endor Labs security requests, includes natural trigger terms, and explicitly delineates boundaries with related specialized skills. The only minor weakness is that the core capability (routing) is inherently less specific than action-oriented skills, but this is appropriate for a router pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Endor Labs security routing) and describes the action of routing ambiguous requests, but the concrete actions are limited to routing/dispatching rather than listing multiple specific capabilities. It does mention examples of what it routes ('check my security', 'help with this dependency') which adds some specificity. | 2 / 3 |
Completeness | Clearly answers both 'what' (routes ambiguous Endor Labs security requests to specialized skills) and 'when' (explicit 'Use when' clause with trigger terms, plus a 'Do NOT use when' clause for exclusions). This is a thorough and explicit description of both dimensions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'endor', 'endor labs', 'check my security', 'help with this dependency', 'what security tools are available'. It also includes negative triggers (when NOT to use it) like '/endor-scan', '/endor-check', '/endor-fix', which helps Claude disambiguate. | 3 / 3 |
Distinctiveness Conflict Risk | Very clearly distinguished from other skills by explicitly naming what it handles (ambiguous/general Endor requests) and what it does NOT handle (specific commands like /endor-scan, /endor-check, /endor-fix). The negative boundary conditions make conflict risk very low. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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-crafted routing skill that is concise, well-structured, and serves its purpose effectively as a dispatcher. The routing table is comprehensive and the error handling section provides clear fallback paths. The only weakness is that actionability is slightly limited since it's a routing skill by nature, but it compensates with concrete error handling guidance and a clear MCP fallback policy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a clear purpose — routing table, error handling, fallback policy — with no unnecessary explanations of what Endor Labs is or how security scanning works. Every token earns its place. | 3 / 3 |
Actionability | The routing table and error handling table provide concrete guidance on what to do, but the skill is primarily a dispatcher with no executable code or commands. The MCP fallback section mentions `npx -y endorctl` but doesn't provide executable examples. For a routing skill this is reasonable but still lacks copy-paste ready commands. | 2 / 3 |
Workflow Clarity | For a routing/dispatcher skill, the workflow is unambiguous: detect intent → match routing table → route. Ambiguous cases have clarifying questions, first-time user detection has a clear 2-step sequence, and error handling has explicit actions per error type. The MCP fallback policy includes a clear decision flow (never silently fall back, show error, suggest setup). | 3 / 3 |
Progressive Disclosure | The skill is itself a progressive disclosure mechanism — it's an overview that routes to 20+ specialized skills. It references one external file (references/data-sources.md) clearly. Content is well-organized into distinct sections with tables for quick scanning. | 3 / 3 |
Total | 11 / 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.