CtrlK
BlogDocsLog inGet started
Tessl Logo

apollo-local-dev-loop

Configure Apollo.io local development workflow. Use when setting up development environment, testing API calls locally, or establishing team development practices. Trigger with phrases like "apollo local dev", "apollo development setup", "apollo dev environment", "apollo testing locally".

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

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 body is highly actionable with complete executable code and a clear step sequence, but it is over-inlined: a 198-line reference file sits unused while the same material is duplicated inline, and the workflow lacks explicit validation checkpoints between steps.

Suggestions

Link and signal references/implementation-guide.md from the body (e.g., a '## Full implementation' section pointing to it) and move the verbose MSW handler array and complete test file into that reference, keeping SKILL.md as a concise overview.

Add explicit validation checkpoints between steps — e.g., after Step 1 run `npm run apollo:check`, and after Step 4 run `npm test` — so the workflow enforces verify-before-proceed rather than relying on a post-hoc error table.

Trim duplication between SKILL.md and the reference so each piece of guidance lives in exactly one place, reducing token cost while preserving copy-paste actionability.

DimensionReasoningScore

Conciseness

Prose is lean and assumes Claude's competence, but roughly 200 lines of full code (the MSW handler array, server, vitest config, and a complete test file) are inlined in SKILL.md and substantially duplicated in references/implementation-guide.md, so the body could be tightened by offloading detail to the reference.

2 / 3

Actionability

Every step ships complete, copy-paste-ready, executable code or commands — dev-client.ts, MSW handlers, vitest config, a working test, and concrete npm scripts — with specific examples throughout.

3 / 3

Workflow Clarity

The five numbered steps give a clear sequence, but there are no explicit mid-flow validation checkpoints (only an end-state Error Handling table and post-hoc scripts), so checkpoints are implicit rather than enforced.

2 / 3

Progressive Disclosure

A reference file exists (references/implementation-guide.md, 198 lines) but is never linked or signaled from the body, and content that belongs in the reference is inlined instead — structure is present but the reference is orphaned.

2 / 3

Total

9

/

12

Passed

Description

90%

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 description that clearly states purpose, use cases, and natural trigger phrases within a distinct Apollo.io niche. It is only held back from full marks by a slightly generic headline action that under-specifies the concrete operations.

DimensionReasoningScore

Specificity

It names the domain and several activities ('setting up development environment, testing API calls locally, or establishing team development practices'), but the headline verb 'Configure Apollo.io local development workflow' is generic and the actions are broad workflow descriptions rather than a list of multiple concrete operations.

2 / 3

Completeness

It explicitly answers both 'what' ('Configure Apollo.io local development workflow') and 'when' ('Use when setting up development environment, testing API calls locally... Trigger with phrases like...'), with explicit trigger guidance.

3 / 3

Trigger Term Quality

It provides good coverage of natural trigger phrases a user would say — 'apollo local dev', 'apollo development setup', 'apollo dev environment', 'apollo testing locally' — across the main intent variations.

3 / 3

Distinctiveness Conflict Risk

The Apollo.io local-development niche and its distinct trigger phrases make it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.