CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with complete, executable examples and a clear step sequence, but it is somewhat verbose in the mock block and keeps all material inline with only implicit validation checkpoints. Splitting the long test fixtures into reference files and trimming unused mocks would lift the weaker dimensions.

Suggestions

Trim the unit-test mock block to only the methods actually exercised (search, searchAndContents) and drop the unused findSimilar/getContents mocks to improve conciseness.

Add an explicit validation checkpoint after Step 2/Step 3, e.g. 'Run `npm test -- --run` and confirm unit tests pass before writing integration tests', to make the workflow's verify step explicit.

Move the full unit and integration test fixtures into a references/ file (e.g. references/test-templates.md) and keep only the key snippet inline, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body is largely lean with no conceptual padding Claude already knows, but the unit-test mock block defines unused mocks (findSimilar, getContents) and a verbose searchAndContents fixture, so not every token earns its place — mostly efficient but could be tightened.

2 / 3

Actionability

It provides a complete project tree, copy-paste package.json, executable TypeScript unit and integration tests, an env setup script, and a vitest config — fully executable and copy-paste ready.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced, but validation checkpoints are only implicit (running vitest) rather than explicitly framed as 'verify before proceeding'; the Error Handling table helps but is not a checkpoint in the flow.

2 / 3

Progressive Disclosure

Sections are well organized, but everything lives inline in a ~210-line body with no bundle/reference files splitting out the long code blocks; the only pointer is to a sibling skill and external docs, so content that could be separate stays inline.

2 / 3

Total

9

/

12

Passed

Description

100%

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 specific, complete, and distinctive: it states concrete capabilities, gives an explicit 'Use when' clause with natural trigger phrases, and occupies a clear Exa-local-dev niche. Voice is appropriately third person with no first/second-person phrasing.

DimensionReasoningScore

Specificity

"Configure Exa local development with hot reload, testing, and mock responses" lists multiple specific concrete actions (hot reload, testing, mock responses), matching the level-3 anchor rather than the level-2 single-domain example.

3 / 3

Completeness

It explicitly states both what ("Configure Exa local development with hot reload, testing, and mock responses") and when ("Use when setting up a development environment..." plus explicit trigger phrases), matching the level-3 what-and-when anchor.

3 / 3

Trigger Term Quality

Phrases like "exa dev setup", "exa local development", "exa test setup", "develop with exa", "mock exa" are natural terms a user would actually say, giving good coverage rather than just one or two relevant keywords.

3 / 3

Distinctiveness Conflict Risk

The Exa-specific niche and distinctive triggers ("exa dev setup", "mock exa") make it unlikely to fire for an unrelated skill, matching the clear-niche level-3 anchor rather than the generic level-2 example.

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.