CtrlK
BlogDocsLog inGet started
Tessl Logo

exa-sdk-patterns

Apply production-ready exa-js SDK patterns with type safety, singletons, and wrappers. Use when implementing Exa integrations, refactoring SDK usage, or establishing team coding standards for Exa. Trigger with phrases like "exa SDK patterns", "exa best practices", "exa code patterns", "idiomatic exa", "exa wrapper".

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 skill body is a lean, fully-actionable set of production exa-js patterns with clear sequencing and well-organized sections. It avoids verbosity and provides copy-paste-ready code without unnecessary concept explanation.

DimensionReasoningScore

Conciseness

The body is dense executable TypeScript with a lean overview and no concept-explaining fluff (no 'what is async/await' or 'what is a singleton'), assuming Claude's competence throughout.

3 / 3

Actionability

Each step provides complete, copy-paste-ready, executable code with imports (getExa, exaSearch, safeExaCall, withRetry, Zod schemas) plus a composed resilientSearch example, not pseudocode.

3 / 3

Workflow Clarity

Steps 1-5 are explicitly sequenced with file paths and build incrementally (client -> search -> errors -> retry -> validation); the operations are non-destructive API calls so the destructive-cap does not apply, and validation/composition are demonstrated.

3 / 3

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into Overview/Prerequisites/Instructions/Examples/Resources/Next Steps with only one-level-deep external doc links and a single sibling-skill pointer, avoiding 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 concise, specific, and third-person, with explicit capability actions, a clear 'Use when' trigger clause, and a good set of natural trigger phrases. It cleanly satisfies all four dimensions.

DimensionReasoningScore

Specificity

Names multiple concrete actions—'type safety, singletons, and wrappers', 'implementing Exa integrations, refactoring SDK usage'—matching the multi-action anchor rather than the single-domain anchor at 2.

3 / 3

Completeness

Explicitly answers both what ('Apply production-ready exa-js SDK patterns...') and when ('Use when implementing Exa integrations, refactoring SDK usage...'), so it is not capped at 2 for a missing Use-when clause.

3 / 3

Trigger Term Quality

Lists several natural phrases users would say ('exa SDK patterns', 'exa best practices', 'idiomatic exa', 'exa wrapper'), giving good coverage of variations rather than just one keyword.

3 / 3

Distinctiveness Conflict Risk

The repeated 'exa' qualifier and SDK-specific triggers carve a clear niche unlikely to conflict with other skills, fitting the clear-niche anchor.

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.