exa-core-workflow-b
Execute Exa findSimilar, getContents, answer, and streaming answer workflows. Use when finding pages similar to a URL, retrieving content for known URLs, or getting AI-generated answers with citations. Trigger with phrases like "exa find similar", "exa get contents", "exa answer", "exa similarity search", "findSimilarAndContents".
84
82%
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 a strong skill description that clearly identifies the Exa-specific workflows it handles, provides explicit 'Use when' guidance, and includes natural trigger phrases. The description is concise, uses third-person voice, and is highly distinctive due to the product-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: findSimilar, getContents, answer, and streaming answer workflows. Also describes concrete use cases like finding similar pages, retrieving content, and getting AI-generated answers with citations. | 3 / 3 |
Completeness | Clearly answers both 'what' (execute Exa findSimilar, getContents, answer, and streaming answer workflows) and 'when' (explicit 'Use when' clause with triggers, plus a 'Trigger with phrases like' section providing additional guidance). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'exa find similar', 'exa get contents', 'exa answer', 'exa similarity search', 'findSimilarAndContents'. These cover both natural language and API-style terms users would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the 'Exa' product name and specific API method names (findSimilar, getContents, answer). Very unlikely to conflict with other skills since it targets a specific tool's workflows. | 3 / 3 |
Total | 12 / 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 solid, actionable skill with excellent executable code examples covering multiple Exa API endpoints. Its main weaknesses are moderate verbosity (some unnecessary explanatory comments and a redundant Output section) and the lack of true workflow validation steps—the numbered steps are more of an API catalog than a dependent workflow. The references to companion skills are good for progressive disclosure but cannot be verified without bundle files.
Suggestions
Remove the 'Output' section entirely as it merely restates what the code examples already demonstrate, saving tokens.
Add error handling/validation within the batch retrieval example (e.g., try/catch per batch with retry logic) to improve workflow clarity for that destructive-adjacent batch operation.
Trim inline comments that explain obvious behavior (e.g., '// findSimilar takes a URL (not a query string)') to just the non-obvious gotchas.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary commentary (e.g., 'Useful when you have URLs from a previous search or external source') and the Output section restates what's already obvious from the code. Some inline comments are helpful but others explain what Claude would already know. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with real API calls, concrete options, and copy-paste ready patterns. The error handling table provides specific HTTP codes and solutions. The examples section includes practical use cases like competitive intelligence and batch retrieval. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and well-labeled, but these are largely independent API calls rather than a true multi-step workflow with dependencies. The batch URL retrieval example lacks validation/error handling within the loop (what if a batch fails?), and there are no explicit validation checkpoints or feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | References to related skills (exa-core-workflow-a, exa-common-errors, exa-sdk-patterns) and external docs are present, but no bundle files exist to support them. The content is somewhat long (~150 lines) with detailed examples that could potentially be split out, and the inline content is heavy for a skill that references companion files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.