exa-known-pitfalls
Identify and avoid Exa anti-patterns and common integration mistakes. Use when reviewing Exa code, onboarding new developers, or auditing existing Exa integrations for correctness. Trigger with phrases like "exa mistakes", "exa anti-patterns", "exa pitfalls", "exa what not to do", "exa code review".
91
91%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 well-structured skill description with strong completeness and trigger term coverage. Its main weakness is that the 'what' portion could be more specific about the concrete anti-patterns or categories of mistakes it addresses, which would help Claude better understand when this skill adds value versus a general Exa skill. Overall it is above average and clearly distinguishable.
Suggestions
Add 2-3 specific examples of the anti-patterns or mistake categories covered (e.g., 'incorrect query formatting, missing error handling, improper pagination') to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Exa anti-patterns/mistakes) and some actions (identify, avoid, review, audit), but doesn't list specific concrete anti-patterns or integration mistakes. It stays at a moderate level of specificity without enumerating what kinds of mistakes or what specific corrections it provides. | 2 / 3 |
Completeness | The description clearly answers both 'what' (identify and avoid Exa anti-patterns and common integration mistakes) and 'when' (reviewing Exa code, onboarding new developers, auditing existing integrations) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | The description explicitly lists natural trigger phrases like 'exa mistakes', 'exa anti-patterns', 'exa pitfalls', 'exa what not to do', 'exa code review'. It also includes contextual triggers like 'reviewing Exa code', 'onboarding new developers', and 'auditing existing Exa integrations', providing good coverage of terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The skill is narrowly scoped to Exa-specific anti-patterns and integration mistakes, which is a clear niche. The 'exa' prefix on all trigger terms and the focus on anti-patterns/pitfalls rather than general Exa usage makes it unlikely to conflict with a general Exa integration skill. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality anti-patterns skill that excels at actionability and conciseness. Each pitfall is presented with executable BAD/GOOD code examples, minimal prose, and a useful review checklist. The only weakness is that the content is somewhat long for a single file and references related skills that aren't provided in the bundle, though the inline organization is clear enough to be effective.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. The brief overview sentence about embeddings-based search is justified as it frames the failure modes. Each pitfall is presented as a concise BAD/GOOD pattern with minimal prose — every token earns its place. | 3 / 3 |
Actionability | Every pitfall includes fully executable TypeScript code with clear BAD/GOOD contrasts. The examples are copy-paste ready, use real API methods with realistic parameters, and demonstrate concrete failure modes alongside correct usage. | 3 / 3 |
Workflow Clarity | This is a reference/checklist skill rather than a multi-step workflow, so the single-task clarity standard applies. The checklist at the end provides a clear review sequence, and Pitfall 4 includes a fallback/retry pattern. The structure is unambiguous for its intended use case (code review and auditing). | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a review checklist, plus references to external docs and related skills (exa-sdk-patterns, exa-common-errors). However, at ~150 lines with 9 pitfalls all inline, some content could be split into a separate detailed reference file, and the referenced related skills aren't provided in the bundle. | 2 / 3 |
Total | 11 / 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.