apollo-reference-architecture
Implement Apollo.io reference architecture. Use when designing Apollo integrations, establishing patterns, or building production-grade sales intelligence systems. Trigger with phrases like "apollo architecture", "apollo system design", "apollo integration patterns", "apollo best practices architecture".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-reference-architecture77
Quality
70%
Does it follow best practices?
Impact
92%
1.91xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/apollo-pack/skills/apollo-reference-architecture/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. However, it lacks specificity about concrete architectural actions (e.g., webhook setup, API authentication, data sync patterns) and could benefit from more natural user language beyond technical jargon.
Suggestions
Add specific concrete actions like 'Configure webhooks, implement OAuth flows, design data sync pipelines, structure API rate limiting'
Include more natural trigger terms users might say such as 'Apollo API', 'sales data integration', 'connect Apollo to CRM', or 'Apollo webhook setup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io integrations) and mentions some actions like 'designing integrations', 'establishing patterns', and 'building production-grade sales intelligence systems', but lacks concrete specific actions like API endpoints, data flows, or specific architectural components. | 2 / 3 |
Completeness | Clearly answers both what ('Implement Apollo.io reference architecture') and when ('Use when designing Apollo integrations, establishing patterns, or building production-grade sales intelligence systems') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'apollo architecture', 'apollo system design', 'apollo integration patterns', but these are somewhat technical. Missing natural user phrases like 'connect to Apollo', 'Apollo API', 'sales data integration', or 'CRM integration'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to Apollo.io platform with distinct triggers mentioning 'apollo' explicitly. Unlikely to conflict with other integration or architecture skills due to the specific product name anchoring. | 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 reference architecture skill with excellent actionability through complete, executable code examples. However, it's overly verbose for a SKILL.md file - the detailed implementations would be better split into separate reference files. The workflow lacks explicit validation checkpoints for the multi-step enrichment and sync processes.
Suggestions
Add explicit validation checkpoints in the searchAndEnrich workflow (e.g., 'Validate API response before persisting', 'Check rate limit status before batch processing')
Split detailed implementations (models, integrations, events) into separate reference files and keep SKILL.md as a concise overview with links
Expand the error handling section with actual code showing retry logic and dead letter queue implementation rather than just a summary table
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose sections. The architecture diagram and project structure are useful, but the extensive code examples could be more condensed since Claude understands NestJS/TypeORM patterns. Some explanatory comments in code are unnecessary. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete implementations including service layers, job processors, data models, and API routes. Code is copy-paste ready with proper imports and decorators. | 3 / 3 |
Workflow Clarity | The searchAndEnrich method shows a clear 4-step workflow with comments, but lacks explicit validation checkpoints. No error recovery feedback loops are shown for the multi-step processes. The error handling table is too brief to guide actual implementation. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic with ~300 lines of inline code. The CRM integration and event patterns could be separate reference files. Only references external resources at the end rather than splitting detailed implementations. | 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 | |
- 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.