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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-local-dev-loop81
Quality
73%
Does it follow best practices?
Impact
98%
2.39xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/apollo-pack/skills/apollo-local-dev-loop/SKILL.mdDiscovery
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.
This description has good structure with explicit 'Use when' and 'Trigger with' clauses, making it complete and distinctive for Apollo.io workflows. However, it lacks concrete specific actions beyond general setup concepts, and the trigger phrases feel somewhat manufactured rather than reflecting natural user language patterns.
Suggestions
Add specific concrete actions like 'configure environment variables', 'set up API mocking', 'initialize local Apollo server', or 'configure authentication for local testing'.
Include more natural trigger variations users might actually say, such as 'run apollo locally', 'test apollo integration', 'apollo sandbox setup', or 'debug apollo API calls'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io local development) and mentions some actions (setting up environment, testing API calls, establishing practices), but lacks concrete specific actions like 'configure environment variables', 'mock API responses', or 'set up local server'. | 2 / 3 |
Completeness | Clearly answers both what (configure Apollo.io local development workflow) and when (setting up dev environment, testing API calls locally, establishing team practices) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'apollo local dev' and 'apollo development setup', but these feel somewhat artificial rather than natural user language. Missing common variations like 'run apollo locally', 'apollo dev server', or 'apollo sandbox'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to Apollo.io local development workflow with distinct triggers. The 'apollo' prefix throughout makes it unlikely to conflict with generic development setup skills or other API-related skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%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, actionable skill with excellent executable code examples covering the full local development workflow. The main weaknesses are missing validation checkpoints between setup steps and some unnecessary content like basic tool documentation links. The structure and progressive disclosure are well-executed.
Suggestions
Add validation checkpoints after Step 1 (verify .env loads correctly) and Step 2 (verify client can authenticate) before proceeding
Remove the Resources section - Claude knows these common tools and can reference them without explicit links
Add a quick verification command after environment setup, e.g., 'node -e "console.log(process.env.APOLLO_API_KEY ? 'OK' : 'Missing')"'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary elements like the Resources section with basic tool links Claude already knows, and the Prerequisites section restates obvious requirements. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for every step including TypeScript clients, mock servers, test files, and bash commands. All examples are complete and runnable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints between steps. No feedback loops for verifying environment setup worked correctly before proceeding to client creation. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections (Overview, Instructions, Output, Error Handling, Examples). References to related skills (apollo-install-auth, apollo-sdk-patterns) are one level deep and clearly signaled. | 3 / 3 |
Total | 10 / 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.