endor-troubleshoot
Troubleshoot Endor Labs scan errors and failures. Use when the user says "scan failed", "why did the scan fail", "endor troubleshoot", "fix scan error", "diagnose error", or pastes an error message from a failed scan. Matches errors against known patterns across NPM, Maven, PyPI, Go, Cargo, NuGet, RubyGems, and Packagist. Do NOT use for setup issues (/endor-setup) or general scanning (/endor-scan).
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 capabilities, comprehensive natural trigger terms, explicit 'Use when' and 'Do NOT use' clauses, and clear differentiation from related skills. The inclusion of supported ecosystems and negative boundaries makes it particularly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: troubleshoot scan errors, match errors against known patterns, and specifies supported ecosystems (NPM, Maven, PyPI, Go, Cargo, NuGet, RubyGems, Packagist). Also explicitly states what it does NOT handle. | 3 / 3 |
Completeness | Clearly answers both 'what' (troubleshoot Endor Labs scan errors, match against known patterns across multiple ecosystems) and 'when' (explicit 'Use when...' clause with specific trigger phrases). Also includes explicit negative boundaries with 'Do NOT use for' guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'scan failed', 'why did the scan fail', 'endor troubleshoot', 'fix scan error', 'diagnose error', and 'pastes an error message from a failed scan' — these are highly natural phrases a user would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear boundaries — explicitly differentiates itself from /endor-setup and /endor-scan skills, and focuses narrowly on troubleshooting scan failures. The negative scope markers significantly reduce conflict risk. | 3 / 3 |
Total | 12 / 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 troubleshooting skill that is well-structured, concise, and highly actionable. The workflow is clearly sequenced with good decision trees (ecosystem detection, error classification), concrete resolution patterns, and appropriate references to external knowledge bases. The output template ensures consistent, useful diagnosis presentation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It uses tables for compact presentation, avoids explaining concepts Claude already knows, and every section serves a clear purpose. No unnecessary padding or explanations of basic concepts. | 3 / 3 |
Actionability | Provides concrete, specific guidance at every step: exact MCP tool parameters, specific file paths to check (~/.endorctl/config.yaml), specific env var names, exact commands (rm -rf ~/.endorctl), specific error indicators to match, and a complete output template. The resolution patterns are specific and actionable. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential workflow with explicit decision points (ecosystem detection table, error classification categories). Step 5 handles multiple errors with priority ordering. The diagnosis output template includes next steps for re-running/reconfiguring. Error handling table covers edge cases with specific actions. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview in the main file and one-level-deep references to external resources (references/error-knowledge-base.md, references/data-sources.md). Links to relevant docs (scan profiles, private registries) and related skills (/endor-scan, /endor-setup) are clearly signaled throughout. | 3 / 3 |
Total | 12 / 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.