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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable code in two languages, a clear step sequence, and a useful error-recovery table. The main improvement opportunity is trimming the small amount of explanatory prose that does not earn its tokens.

Suggestions

Cut marketing-style detail such as 'Apollo's 275M+ database' and keep only operationally relevant facts (e.g. credit cost, free vs. paid).

Tighten the per-step prose intros so each step leads with the endpoint/action rather than a descriptive sentence.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and code-driven, but prose intros like 'finds contacts in Apollo's 275M+ database' and explanatory asides add context Claude does not need, so it could be tightened further rather than scoring a 3.	2 / 3
Actionability	It provides fully executable TypeScript and Python snippets with concrete endpoints, headers, and parameters, making the examples copy-paste ready.	3 / 3
Workflow Clarity	Steps 1-4 are clearly sequenced, and the Error Handling table maps failures to causes and recovery actions, providing an error-recovery feedback loop; the operations are non-destructive API calls so embedded validation checkpoints are not critical.	3 / 3
Progressive Disclosure	The body is a single well-organized file with clear sections (Overview, Prerequisites, Instructions, Output, Error Handling, Resources, Next Steps) and one-level-deep external doc links, with no nested or buried references.	3 / 3
	Total	11 / 12 Passed

Description

90%

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/when guidance and a strong set of natural trigger phrases. Its only weakness is specificity: it summarizes the skill as a single 'minimal example' rather than naming the concrete API operations it demonstrates.

Suggestions

Replace the single 'Create a minimal working Apollo.io example' action with the concrete operations the skill covers, e.g. 'Run Apollo.io people search, person enrichment, and organization enrichment'.

Drop or tighten the 'Trigger with phrases like' framing so the natural keywords read as triggers rather than meta-instructions.

Dimension	Reasoning	Score
Specificity	It names the domain ('Apollo.io') and a concrete action ('Create a minimal working Apollo.io example') but lists only a single high-level action rather than the multiple specific operations the skill actually covers (search, enrichment), so it is not comprehensive enough for a 3.	2 / 3
Completeness	It explicitly answers both what ('Create a minimal working Apollo.io example') and when ('Use when starting a new Apollo integration, testing your setup, or learning basic Apollo API patterns') with explicit triggers.	3 / 3
Trigger Term Quality	It provides good coverage of natural phrases a user would say ('apollo hello world', 'apollo example', 'apollo quick start', 'simple apollo code', 'test apollo api'), matching the anchor for natural term coverage.	3 / 3
Distinctiveness Conflict Risk	The Apollo.io niche is specific and the apollo-prefixed triggers are distinct, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.