exa-reference-architecture
Implement Exa reference architecture with best-practice project layout. Use when designing new Exa integrations, reviewing project structure, or establishing architecture standards for Exa applications. Trigger with phrases like "exa architecture", "exa best practices", "exa project structure", "how to organize exa", "exa layout".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exa-reference-architecture74
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 excellent trigger term coverage and clear when/what guidance. The main weakness is the lack of specificity about what concrete actions the skill enables - it describes the domain well but doesn't detail what specific outputs or transformations it provides (e.g., specific file structures, configuration patterns, or architectural components).
Suggestions
Add specific concrete actions the skill performs, such as 'creates directory structure, configures API clients, sets up error handling patterns' to improve specificity
Consider briefly mentioning what Exa is (if not widely known) or what types of files/outputs are generated to make the capabilities more concrete
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Exa reference architecture) and mentions actions like 'designing new Exa integrations, reviewing project structure, establishing architecture standards', but lacks concrete specific actions like what files to create, what patterns to implement, or what the architecture actually contains. | 2 / 3 |
Completeness | Clearly answers both what ('Implement Exa reference architecture with best-practice project layout') and when ('Use when designing new Exa integrations, reviewing project structure, or establishing architecture standards') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'exa architecture', 'exa best practices', 'exa project structure', 'how to organize exa', 'exa layout'. Good coverage of variations users might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to 'Exa' integrations and architecture, which is a distinct niche. The explicit trigger terms all include 'exa' making it unlikely to conflict with general architecture or other integration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid reference architecture template with good visual structure and TypeScript examples, but falls short on actionability due to incomplete code implementations and vague setup instructions. The workflow lacks validation checkpoints that would help catch configuration errors during setup. The content could be more concise by removing obvious prerequisites and tightening the ASCII diagrams.
Suggestions
Complete the code examples - implement wrapExaError function body, define Cache/Monitor interfaces, and show actual ExaClient import/initialization
Add validation steps after each instruction phase (e.g., 'Verify: run `npx tsc --noEmit` to check types compile')
Replace vague instructions like 'Create the singleton client with caching' with specific file content or commands to execute
Remove the Prerequisites section - Claude already understands layered architecture and TypeScript setup
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the prerequisites section (Claude knows what layered architecture is) and verbose ASCII diagrams that could be simplified. The structure is good but could be tighter. | 2 / 3 |
Actionability | Provides concrete TypeScript code examples and a bash setup script, but many code snippets are incomplete (e.g., wrapExaError has no implementation, Cache/Monitor classes undefined). The 'Instructions' section is vague ('Create the singleton client with caching') rather than executable. | 2 / 3 |
Workflow Clarity | Steps are listed (Step 1-4) but lack validation checkpoints. No verification that the structure is correct, no testing guidance between steps, and no feedback loop for catching setup errors. For an architecture setup skill, validation of the created structure would be important. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, references to external docs and related skills (exa-multi-env-setup), and appropriate use of collapsible content areas. The project structure is well-organized and easy to navigate. | 3 / 3 |
Total | 9 / 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.