exa-local-dev-loop

Configure Exa local development with hot reload, testing, and mock responses. Use when setting up a development environment, writing tests against Exa, or establishing a fast iteration cycle. Trigger with phrases like "exa dev setup", "exa local development", "exa test setup", "develop with exa", "mock exa".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

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

A highly actionable, well-structured dev-loop skill with executable code for every step and a useful error-handling table. The main improvements are adding an explicit verification checkpoint between steps and resolving the dangling exa-sdk-patterns reference.

Suggestions

Add an explicit validation checkpoint between steps (e.g., after Step 3/4: 'Run `npm run test:unit` and confirm mocks resolve before proceeding to integration tests') to strengthen workflow feedback loops.

Resolve the 'See exa-sdk-patterns' reference in Next Steps — either bundle that file under references/ or remove the dangling pointer so navigation targets are real.

Trim the unit-test mock to the methods actually asserted (search, searchAndContents), or add assertions for findSimilar/getContents, to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no padding about what Exa/vitest/mocking are), but the unit-test mock scaffolds four methods (search, searchAndContents, findSimilar, getContents) while only two are asserted, a minor instance of over-supply that could be trimmed, fitting the score-4 anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready code across project structure, package.json scripts, a vitest unit mock, integration tests, env config, and a vitest config, covering the common Exa cases (search, searchAndContents, findSimilar), matching the score-5 anchor.	5 / 5
Workflow Clarity	Steps 1–5 are clearly sequenced and the error-handling table supplies recovery guidance, but there are no explicit validate-then-proceed checkpoints between steps (e.g., a 'run npm test to confirm setup' gate), placing it at score 4 rather than 5; this is a dev-setup skill, so the destructive/batch cap does not apply.	4 / 5
Progressive Disclosure	Content is organized into clear, navigable sections (Overview, Prerequisites, Instructions, Error Handling, Examples, Resources, Next Steps) with one-level-deep external links, fitting the score-4 'good structure; minor organization gaps' anchor; the gap is the 'See exa-sdk-patterns' pointer in Next Steps, which references no bundled file.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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

A strong, well-formed description that concretely states capabilities, gives explicit 'Use when' guidance with natural trigger phrases, and carves out a distinct Exa-dev niche. Minor room to expand trigger synonyms and enumerate a couple more actions.

Suggestions

Add a few more natural trigger synonyms (e.g., 'exa testing', 'exa mock setup', 'exa integration tests') to push trigger-term coverage toward comprehensive.

Consider explicitly naming one or two more concrete actions in the 'what' clause (e.g., integration tests, environment configuration) for fuller capability coverage.

Dimension	Reasoning	Score
Specificity	The description names several concrete actions ('hot reload, testing, and mock responses') within the Exa dev domain, matching the 'several specific actions; minor gaps' anchor; it stops short of score 5 because coverage is not exhaustive (e.g., integration tests, env config are implied rather than enumerated).	4 / 5
Completeness	It clearly answers 'what' ('Configure Exa local development with hot reload, testing, and mock responses') and 'when' ('Use when setting up a development environment...') plus explicit concrete trigger phrases, matching the score-5 anchor that requires both what and when with concrete triggers.	5 / 5
Trigger Term Quality	It lists five natural trigger phrases ('exa dev setup', 'exa local development', 'exa test setup', 'develop with exa', 'mock exa') giving good keyword coverage, but a few natural variations/synonyms are missing, so it fits the score-4 anchor rather than the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	The Exa-local-dev niche with Exa-scoped triggers ('exa dev setup', 'mock exa') is clearly distinct from sibling skills and unlikely to fire for the wrong skill, fitting the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/exa-pack/skills/exa-local-dev-loop/SKILL.md
Commit: 8585d6d

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.