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".
74
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/apollo-pack/skills/apollo-local-dev-loop/SKILL.mdQuality
Discovery
75%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 well-structured with clear 'what' and 'when' sections and explicit trigger phrases, making it functionally complete. Its main weakness is that the specific capabilities are somewhat vague—'configure local development workflow' doesn't tell Claude exactly what actions the skill can perform (e.g., setting up Docker, configuring environment variables, creating test fixtures). The trigger terms are reasonable but could cover more natural variations.
Suggestions
Add more concrete actions to the first line, e.g., 'Configure Apollo.io local development workflow including environment variable setup, API key configuration, Docker container management, and local API call testing.'
Expand trigger term coverage with more natural variations like 'run apollo locally', 'set up apollo', 'apollo API testing setup', 'apollo dev config'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Apollo.io local development) and mentions some actions like 'setting up development environment', 'testing API calls locally', and 'establishing team development practices', but these are fairly general and don't list concrete specific actions like 'configure Docker containers', 'set up API keys', or 'run local test suites'. | 2 / 3 |
Completeness | The description clearly answers both 'what' (configure Apollo.io local development workflow) and 'when' (setting up development environment, testing API calls locally, establishing team development practices) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes some relevant trigger phrases like 'apollo local dev', 'apollo development setup', 'apollo dev environment', and 'apollo testing locally'. However, these are somewhat narrow and miss common natural variations users might say like 'run apollo locally', 'apollo dev config', 'apollo API testing', or just 'set up apollo'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Apollo.io local development specifically, which is a distinct niche. The trigger terms all include 'apollo' combined with development-specific terms, making it unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with complete, executable code for every step of the Apollo local dev setup. Its main weaknesses are the length of inline code (especially mock handlers) that could benefit from being split into referenced files, and the absence of explicit validation checkpoints between steps to confirm each stage succeeded before proceeding.
Suggestions
Add explicit validation checkpoints after key steps, e.g., 'Run `npm run apollo:check` to verify auth before proceeding to Step 3' and 'Run `npm test` to confirm MSW is working before adding more scripts'.
Move the lengthy MSW mock handlers into a referenced bundle file (e.g., `apollo-handlers.ts`) and keep only a brief summary or one example handler inline to reduce body length.
Remove the Output section — it restates what the steps already produce and adds no new information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code blocks, but includes some unnecessary verbosity — the Overview paragraph explains what a sandbox token is (Claude knows this), inline comments like '# .env (gitignored — copy from example)' are slightly redundant, and the Output section largely restates what the steps already produced. The mock handlers are quite lengthy and could be trimmed. | 2 / 3 |
Actionability | Every step provides fully executable, copy-paste-ready code — TypeScript files, bash commands, JSON config, and test files. The code is complete with imports, exports, and proper configuration. The npm scripts provide concrete commands for every workflow need. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-5) and logically ordered from environment setup through testing. However, there are no explicit validation checkpoints between steps — no 'verify this works before proceeding' gates. For a setup workflow that could silently fail (e.g., missing env vars, wrong MSW config), the lack of feedback loops or verification steps is a gap. | 2 / 3 |
Progressive Disclosure | The skill references a prerequisite skill ('apollo-install-auth') and a next step ('apollo-sdk-patterns'), which is good navigation. However, the content is quite long with extensive inline code that could be split into referenced files (e.g., the MSW handlers, the test file). External resource links are provided but the body itself is monolithic. | 2 / 3 |
Total | 9 / 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 | |
- Commit
3a2d27d
- 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.