endor-demo
Demo Endor Labs capabilities using simulated data, no account required. Use when the user says "try endor", "demo", "endor without account", "show me what endor can do", or when MCP auth fails and user wants to see capabilities before signing up. Do NOT use when the user has a working Endor Labs account — use real scans instead.
86
83%
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 description with excellent trigger terms, clear completeness (both what and when), and a helpful negative boundary ('Do NOT use when...'). The main weakness is that the 'what' portion is somewhat vague — it says 'demo capabilities' without specifying what those capabilities are (e.g., dependency scanning, vulnerability detection, etc.).
Suggestions
Add specific concrete actions that the demo covers, e.g., 'Demonstrates dependency scanning, vulnerability detection, and risk scoring using simulated data' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'Demo Endor Labs capabilities using simulated data' which names the domain and a general action (demoing capabilities), but doesn't list specific concrete actions like what capabilities are demonstrated or what the simulated data includes. | 2 / 3 |
Completeness | Clearly answers both 'what' (demo Endor Labs capabilities using simulated data, no account required) and 'when' (explicit trigger phrases plus contextual triggers like auth failure). Also includes a helpful 'when NOT to use' clause for disambiguation. | 3 / 3 |
Trigger Term Quality | Excellent trigger term coverage with natural phrases users would say: 'try endor', 'demo', 'endor without account', 'show me what endor can do', plus the contextual trigger of MCP auth failure. These are highly natural and varied. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with very specific trigger terms tied to Endor Labs demo mode. The explicit 'Do NOT use when' clause further reduces conflict risk by clearly delineating this skill from the real Endor Labs scanning skill. | 3 / 3 |
Total | 11 / 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 well-structured demo skill that clearly communicates when and how to present Endor Labs capabilities using simulated data. Its strengths are conciseness and clear workflow sequencing. The main weakness is that the actionability could be improved with more concrete implementation details for project detection and output generation rather than relying on templates with placeholders.
Suggestions
Add concrete code or specific file-reading commands for the 'Detect Project Info' step (e.g., show how to check for package.json, parse dependency count)
Provide a second example simulated output for a different language ecosystem (e.g., Python/Go) to make the tailoring guidance more actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. Every section serves a clear purpose, there's no explanation of concepts Claude already knows, and the markdown template is compact yet informative. | 3 / 3 |
Actionability | The workflow provides a clear template and specific commands to showcase, but the 'Detect Project Info' step lacks concrete code for reading manifests, and the simulated scan output is a template rather than executable logic. It describes what to do more than showing exactly how. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced from welcome through call-to-action. Since this is a demo presentation skill (not a destructive or batch operation), validation checkpoints aren't critical, and the sequence is unambiguous with clear transitions between steps. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but everything is inline in a single file. The feature showcase commands and the simulated scan template could potentially be separated, though the skill is short enough that this is borderline acceptable. | 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.