endor-help
Quick reference for all available Endor Labs commands. Use when the user says "endor help", "what commands are available", "endor usage", "what can endor do", or wants to discover available security scanning capabilities. Do NOT use when the user already knows which specific command they want — route to that skill directly.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/endor-help/SKILL.mdQuality
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 well-crafted description with excellent trigger terms, clear completeness (both what and when), and strong distinctiveness through its explicit routing guidance. Its main weakness is that the 'what' portion is somewhat general — it could benefit from listing a few example commands or categories of commands to improve specificity. The 'Do NOT use when' clause is a particularly effective addition for disambiguation.
Suggestions
Add 2-3 specific examples of command categories or capabilities covered (e.g., 'Lists commands for dependency scanning, policy management, CI integration') to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain ('Endor Labs commands') and describes the general action ('quick reference'), but doesn't list specific concrete actions or capabilities beyond 'security scanning capabilities'. It tells you it's a reference guide but not what specific commands or actions it covers. | 2 / 3 |
Completeness | Clearly answers both 'what' (quick reference for all available Endor Labs commands) and 'when' (explicit 'Use when...' clause with multiple trigger phrases). Also includes a helpful 'Do NOT use when' clause for routing clarity. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases: 'endor help', 'what commands are available', 'endor usage', 'what can endor do', 'discover available security scanning capabilities'. These are realistic phrases a user would say when seeking help with Endor Labs. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — it's specifically for discovering/listing Endor Labs commands, not for executing them. The 'Do NOT use when the user already knows which specific command they want' clause explicitly delineates boundaries against other Endor Labs skills, reducing conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a clean, well-organized command reference that serves its purpose as a discovery/help skill. Its main strength is conciseness and clear categorization. Its weaknesses are the lack of explicit workflow guidance for new users (e.g., recommended order of operations) and the absence of references to detailed per-command documentation, which limits progressive disclosure.
Suggestions
Add a brief 'Recommended Workflow' section showing the typical sequence: setup → scan → review findings → fix → pre-PR review, to improve workflow clarity.
Include explicit references or links to per-command skill files (e.g., 'For detailed usage, see [endor-scan.md](endor-scan.md)') to improve progressive disclosure.
Make the final instruction ('If the user asks about a specific command, provide detailed usage for that command only') more actionable by specifying where to find that detailed usage or what format to use.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient — it's essentially a well-formatted reference table with no unnecessary explanations. Every line serves a purpose: command name and brief description. No concepts are over-explained. | 3 / 3 |
Actionability | The skill provides a clear command reference with examples, but the commands themselves are slash-commands whose behavior is defined elsewhere. The 'Quick Examples' section adds concrete usage patterns, but there's no executable code or detailed guidance on what each command actually does or returns. The final line ('provide detailed usage for that command only') is vague. | 2 / 3 |
Workflow Clarity | The commands are organized into logical categories (Getting Started → Scanning → Analysis → Findings → Compliance → Advanced), and the Tips section suggests a lightweight workflow (scan → review → fix). However, there's no explicit multi-step workflow with validation checkpoints — e.g., no guidance on 'run setup first, then scan, then review findings, then fix.' | 2 / 3 |
Progressive Disclosure | The content is well-organized into sections with tables, which is good structure. However, there are no references to detailed documentation files for individual commands. The skill mentions routing to specific command skills but doesn't provide any links or file references. With no bundle files, this is a missed opportunity for clear navigation to deeper content. | 2 / 3 |
Total | 9 / 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
b958adc
- 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.