CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

78

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured pitfall catalog: lean per-section explanations, fully executable BAD/GOOD code for each issue, a consolidated review checklist, and clean organization with no nested references or unnecessary concept explanations. It models the good-example patterns and avoids the bad-example pitfalls.

DimensionReasoningScore

Conciseness

Each pitfall is a tight one-line explanation plus BAD/GOOD code with no filler explaining concepts Claude already knows; the dense, non-redundant sections earn their tokens even though the catalog is long.

3 / 3

Actionability

Every pitfall ships fully executable TypeScript (real imports, real Exa method calls and options) with concrete BAD vs GOOD comparisons, making the guidance copy-paste ready.

3 / 3

Workflow Clarity

As a catalog-style review skill it provides a clear 'Quick Review Checklist' that sequences the review; it involves no destructive or batch operations that would require validation checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist; the content is self-contained and well-organized into Overview, nine Pitfalls, a Review Checklist, Resources, and Next Steps, with only one-level external pointers rather than nested references.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-triggered: it states concrete actions, an explicit Use-when clause with natural trigger phrases, and a distinct Exa niche that avoids conflict with other skills. It follows the good-example pattern closely and uses third-person voice throughout.

DimensionReasoningScore

Specificity

Names the Exa anti-patterns/integration-mistakes domain and lists several concrete actions (identify, avoid, review, onboard, audit for correctness), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Identify and avoid Exa anti-patterns and common integration mistakes') and when ('Use when reviewing Exa code, onboarding new developers, or auditing existing Exa integrations'), with an explicit Use-when clause.

3 / 3

Trigger Term Quality

Provides a broad set of natural trigger phrases a user would actually say ('exa mistakes', 'exa anti-patterns', 'exa pitfalls', 'exa what not to do', 'exa code review'), satisfying the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

A clear Exa-specific niche with distinct triggers all containing 'exa', making it unlikely to fire for or conflict with unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.