exa-sdk-patterns
Apply production-ready Exa SDK patterns for TypeScript and Python. 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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exa-sdk-patterns88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 explicit 'Use when' and 'Trigger with' clauses that clearly define when Claude should select this skill. The main weakness is that the capabilities section is somewhat abstract - it mentions 'production-ready patterns' without specifying what those patterns actually do (e.g., search queries, content retrieval, error handling).
Suggestions
Add specific concrete actions the patterns cover, such as 'search queries, content retrieval, pagination handling, error management' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Exa SDK) and mentions actions like 'implementing integrations', 'refactoring SDK usage', and 'establishing team coding standards', but doesn't list specific concrete actions like what patterns or operations are covered. | 2 / 3 |
Completeness | Clearly answers both what ('Apply production-ready Exa SDK patterns for TypeScript and Python') and when ('Use when implementing Exa integrations, refactoring SDK usage, or establishing team coding standards') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'exa SDK patterns', 'exa best practices', 'exa code patterns', 'idiomatic exa'. Also mentions TypeScript and Python which are relevant language keywords. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Exa SDK specifically, with distinct triggers like 'exa SDK patterns' and 'idiomatic exa' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent actionability and conciseness - the code patterns are production-ready and the content respects Claude's intelligence. The main weakness is the lack of explicit validation steps to verify the implemented patterns work correctly before deployment. The structure and progressive disclosure are well-executed.
Suggestions
Add a validation step after implementing patterns, e.g., 'Step 4: Verify Setup - Run a test call to confirm the singleton and error handling work: `const result = await safeExaCall(() => getExaClient().ping());`'
Include a brief checklist at the end to verify all patterns are correctly integrated before moving to production use
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only production-ready patterns without explaining basic concepts like what an SDK is or how async/await works. Every code block serves a clear purpose. | 3 / 3 |
Actionability | All code examples are fully executable TypeScript and Python with proper imports, type annotations, and complete implementations. The singleton, retry logic, and context manager patterns are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced (1-3), but there's no validation checkpoint to verify the patterns work correctly. Missing feedback loop for testing the implemented patterns before production use. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Overview, Instructions, Examples, Resources). References to external docs and next steps are one level deep and clearly signaled. Content is appropriately split between core patterns and examples. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.