apollo-sdk-patterns
Apply production-ready Apollo.io SDK patterns. Use when implementing Apollo integrations, refactoring API usage, or establishing team coding standards. Trigger with phrases like "apollo sdk patterns", "apollo best practices", "apollo code patterns", "idiomatic apollo", "apollo client wrapper".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-sdk-patterns86
Quality
81%
Does it follow best practices?
Impact
100%
1.75xAverage score across 3 eval scenarios
Discovery
89%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 is a well-structured skill description with strong completeness and excellent trigger term coverage. The main weakness is the somewhat abstract capability description - 'production-ready patterns' and 'best practices' are somewhat vague compared to listing specific concrete actions the skill enables. The explicit trigger phrase list is a notable strength.
Suggestions
Add 2-3 specific concrete actions the skill enables, such as 'create typed client wrappers', 'implement rate limiting', 'handle pagination patterns', or 'structure error handling'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io SDK) and mentions some actions ('implementing integrations', 'refactoring API usage', 'establishing team coding standards'), but lacks concrete specific actions like 'create client wrappers', 'handle pagination', or 'implement error handling'. | 2 / 3 |
Completeness | Clearly answers both what ('Apply production-ready Apollo.io SDK patterns') and when ('Use when implementing Apollo integrations, refactoring API usage, or establishing team coding standards') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'apollo sdk patterns', 'apollo best practices', 'apollo code patterns', 'idiomatic apollo', 'apollo client wrapper'. Good coverage of variations users might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Apollo.io SDK with distinct triggers. Unlikely to conflict with other skills due to the specific product name and explicit trigger phrases listed. | 3 / 3 |
Total | 11 / 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 strong, actionable skill with excellent code examples that are production-ready and copy-paste executable. The main weaknesses are minor verbosity in introductory sections and lack of explicit workflow guidance for integrating the patterns together or validating setup before use. The progressive disclosure and organization are well-executed.
Suggestions
Add a brief 'Integration Order' section showing how patterns build on each other (e.g., 'Set up errors.ts first, then client.ts imports those errors')
Include a validation step after singleton setup, such as a health check call to verify API key works before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial code examples but includes some unnecessary explanations (e.g., 'Production-ready patterns for Apollo.io API integration with type safety, error handling, and retry logic' restates what the title implies). The prerequisites section explaining familiarity with async/await and TypeScript generics is somewhat redundant for Claude. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all patterns are copy-paste ready with complete TypeScript implementations including imports, type definitions, and usage examples. The code is production-quality with proper error handling and real API endpoints. | 3 / 3 |
Workflow Clarity | While individual patterns are well-documented, there's no clear sequence for when to apply which pattern or how they integrate together. The 'When to Use' table helps but lacks validation checkpoints - for example, no guidance on verifying the singleton is properly configured before making API calls. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections for each pattern, a summary table for quick reference, and appropriate external references (Zod docs, Axios docs). The 'Next Steps' section provides clear navigation to related skills. Content is appropriately organized without excessive nesting. | 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.