endor-api
Execute custom queries against the Endor Labs API for advanced use cases. Use when the user asks to query findings, projects, packages, or metrics directly, says "endor api", "raw api query", "custom query", "list resources", or needs to run API filters not covered by other endor skills. Do NOT use for standard scanning (/endor-scan), dependency checks (/endor-check), or finding display (/endor-findings).
89
86%
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 clearly defines its purpose, provides rich natural trigger terms, and explicitly delineates its boundaries against related skills. The 'Do NOT use' clause is particularly effective for preventing conflicts in a multi-skill environment. The description is concise yet comprehensive, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'execute custom queries', 'query findings, projects, packages, or metrics', 'run API filters'. Also specifies what it does NOT do (scanning, dependency checks, finding display), which adds clarity. | 3 / 3 |
Completeness | Clearly answers both 'what' (execute custom queries against the Endor Labs API) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios). Also includes explicit 'Do NOT use' guidance for disambiguation. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'endor api', 'raw api query', 'custom query', 'list resources', 'API filters', plus domain objects like 'findings', 'projects', 'packages', 'metrics'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally distinctive due to the explicit 'Do NOT use for...' clause that delineates boundaries against related endor skills (endor-scan, endor-check, endor-findings). The trigger terms like 'raw api query' and 'custom query' are highly specific to this skill's niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid API reference skill with strong actionability—concrete commands, real filter syntax, and specific resource types make it immediately useful. The main weaknesses are minor verbosity (Step 1 is unnecessary for Claude) and lack of validation checkpoints in the workflow, particularly for verifying query results before presenting them to users. The progressive disclosure and reference structure are well done.
Suggestions
Remove Step 1 ('Understand the Query') as Claude inherently parses user requests—this adds tokens without value.
Add a validation step between execution and presentation, e.g., 'Verify response contains expected fields and non-empty results before formatting output; if empty, suggest broadening filters.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables, but includes some unnecessary structure like the 'Step 1: Understand the Query' section which tells Claude to parse user requests—something it inherently does. The presentation format template in Step 4 is also somewhat unnecessary. | 2 / 3 |
Actionability | Provides concrete, executable CLI commands with real flag syntax, specific filter examples with actual field paths, exact MCP tool names, and real resource type names. The filter syntax section with examples is copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and the workflow is logical, but there's no validation checkpoint—no step to verify the query returned expected results or handle malformed responses. The error handling table is present but disconnected from the workflow steps rather than integrated as checkpoints. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate use of tables for reference data, and one-level-deep references to external files (references/cli-parsing.md, references/data-sources.md) that are clearly signaled with context about what they contain. | 3 / 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.