exa-hello-world
Create a minimal working Exa example. Use when starting a new Exa integration, testing your setup, or learning basic Exa API patterns. Trigger with phrases like "exa hello world", "exa example", "exa quick start", "simple exa code".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exa-hello-world71
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 limited specificity about what concrete actions the skill performs beyond creating a 'minimal working example'. Adding details about what the example demonstrates (e.g., search queries, content retrieval) would strengthen it.
Suggestions
Add specific concrete actions the example demonstrates, such as 'performs a basic search query, retrieves results, and displays content' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Exa) and one action ('Create a minimal working Exa example'), but lacks comprehensive concrete actions like specific API operations, data handling, or output formats. | 2 / 3 |
Completeness | Clearly answers both what ('Create a minimal working Exa example') and when ('Use when starting a new Exa integration, testing your setup, or learning basic Exa API patterns') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'exa hello world', 'exa example', 'exa quick start', 'simple exa code'. Also includes contextual triggers like 'starting a new Exa integration' and 'testing your setup'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Exa' as a specific product/API name. The combination of 'Exa' with 'hello world', 'quick start', and 'example' creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structure and organization but fails at its core purpose - providing a working 'hello world' example. The code snippets are incomplete placeholders rather than executable examples, which defeats the purpose of a quick-start skill. The error handling table is useful but the main content needs actual API calls that demonstrate Exa functionality.
Suggestions
Replace placeholder comments with actual, complete API calls (e.g., a simple search query) that produce visible output
Remove the duplicate TypeScript code block - keep only one complete, executable example per language
Add a validation step after client initialization to confirm the connection works before proceeding
Show the expected API response structure, not just a generic 'Success!' message
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some redundancy - the TypeScript example appears twice (in Steps 2-3 and again in Examples section). The structure is reasonable but could be tightened by removing duplicate code blocks. | 2 / 3 |
Actionability | The code examples are incomplete placeholders with '// Your first API call here' comments instead of actual executable API calls. A 'hello world' skill should show a complete, working example that demonstrates the API actually doing something. | 1 / 3 |
Workflow Clarity | Steps are listed sequentially but lack validation checkpoints. There's no verification step to confirm the setup works before proceeding, and the 'Make Your First API Call' step doesn't actually show what call to make. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate external references to documentation and next steps. Content is well-organized with a logical flow from prerequisites through examples to resources. | 3 / 3 |
Total | 8 / 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 | |
- 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.