apollo-hello-world
Create a minimal working Apollo.io example. Use when starting a new Apollo integration, testing your setup, or learning basic Apollo API patterns. Trigger with phrases like "apollo hello world", "apollo example", "apollo quick start", "simple apollo code", "test apollo api".
80
77%
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-hello-world/SKILL.mdQuality
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.
The description is well-structured with clear 'what' and 'when' clauses and excellent trigger term coverage for Apollo.io quick-start scenarios. Its main weakness is the lack of specificity about what concrete actions the skill performs beyond 'create a minimal working example' — listing specific capabilities like API authentication, contact search, or data enrichment would strengthen it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Scaffolds Apollo.io API authentication, performs a sample contact search, and demonstrates basic enrichment calls' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Apollo.io integration) and one action ('Create a minimal working example'), but doesn't list multiple specific concrete actions like 'authenticate with API key, search contacts, enrich leads'. | 2 / 3 |
Completeness | Clearly answers both 'what' (create a minimal working Apollo.io example) and 'when' (starting a new integration, testing setup, learning basic API patterns) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would actually say: 'apollo hello world', 'apollo example', 'apollo quick start', 'simple apollo code', 'test apollo api'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Apollo.io quick-start/hello-world scenarios, which is a distinct niche unlikely to conflict with other skills. The specific trigger terms further reduce conflict risk. | 3 / 3 |
Total | 11 / 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 hello-world skill with excellent actionability — the code examples are concrete, executable, and cover the three core API operations well. The main weaknesses are moderate verbosity (explanatory text and a full Python equivalent that could be a separate file) and missing validation checkpoints between credit-consuming steps. The error handling table is a nice touch that adds practical value.
Suggestions
Add a validation checkpoint after Step 1 (the free endpoint) to confirm the API key works before proceeding to credit-consuming Steps 2 and 3, e.g., 'Verify you see results before continuing — Steps 2-3 consume credits.'
Move the Python equivalent to a separate file (e.g., PYTHON_EXAMPLE.md) and reference it from the main skill to reduce token footprint.
Trim explanatory sentences like 'The People API Search endpoint finds contacts in Apollo's 275M+ database' — Claude doesn't need this context to execute the code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good executable examples, but includes some unnecessary explanations Claude already knows (e.g., 'The People API Search endpoint finds contacts in Apollo's 275M+ database', explaining what enrichment does). The Python equivalent section adds bulk that could be a separate reference file. Some inline comments are helpful but the overall content could be tightened. | 2 / 3 |
Actionability | Fully executable TypeScript and Python code with specific endpoints, request payloads, and response handling. The code is copy-paste ready with real API paths, correct headers, and concrete parameter examples. The error handling table provides specific solutions for each error code. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and labeled (Steps 1-4), with helpful notes about credit consumption. However, there are no validation checkpoints — no verification that the API key works before proceeding, no check that Step 1 succeeds before Step 2, and no explicit 'run and verify output' instructions between steps. For an API integration involving credit-consuming operations, validation steps would be important. | 2 / 3 |
Progressive Disclosure | The content has reasonable section structure and links to external Apollo docs, but the Python equivalent could be split into a separate file. For a 'hello world' skill, the inline content is borderline too long. The reference to 'apollo-install-auth' and 'apollo-local-dev-loop' skills provides good navigation, but no bundle files exist to support progressive disclosure. | 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.