CtrlK
BlogDocsLog inGet started
Tessl Logo

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

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%Weight 40%Scale 1-3

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

Strong, actionable content with executable code in two languages and a useful error table. It loses points on workflow clarity for credit-consuming steps that lack validation checkpoints, and slightly on conciseness due to dual-language duplication.

Suggestions

Add a validation checkpoint before the credit-consuming Steps 2 and 3 (e.g., confirm the search returned a person before enriching, or warn the user that the next call costs a credit).

Tighten the Python Step 4 to only the operations not already shown, or move it to a reference file, to reduce duplication with the TypeScript steps.

DimensionReasoningScore

Conciseness

The body is lean with no concept-explanation padding and executable code throughout, but it duplicates the same three operations in both TypeScript (Steps 1-3) and Python (Step 4), adding tokens that could be tightened for a hello-world skill.

2.5 / 3

Actionability

Provides fully executable TypeScript and Python code with real endpoints, headers, and parameters, plus a concrete error-handling table — copy-paste ready.

3 / 3

Workflow Clarity

The four steps are clearly sequenced, but Steps 2 and 3 consume paid credits and there are no validation checkpoints or feedback loops (e.g., verify the response before proceeding), which caps credit-incurring workflows at 2.

2 / 3

Progressive Disclosure

A single, well-organized SKILL.md with clearly signaled one-level-deep external doc links in the Resources section and no nested references; appropriate for a simple skill needing no bundle files.

3 / 3

Total

10.5

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, well-triggered description that answers both what and when with natural keywords and a distinct Apollo.io niche. Its only weakness is that the capability statement stays somewhat abstract rather than naming the concrete API operations the skill performs.

Suggestions

Replace the abstract 'Create a minimal working Apollo.io example' with the concrete operations, e.g. 'Run people search, person enrichment, and organization enrichment against the Apollo.io API'.

DimensionReasoningScore

Specificity

Names the Apollo.io domain and a few actions ('Create a minimal working Apollo.io example', 'testing your setup', 'learning basic Apollo API patterns') but stays abstract rather than listing the concrete operations (people search, enrichment) shown in the body, so it is not comprehensive.

2 / 3

Completeness

Explicitly answers what it does and when to use it via 'Use when starting a new Apollo integration, testing your setup, or learning basic Apollo API patterns' plus an explicit 'Trigger with phrases like' clause.

3 / 3

Trigger Term Quality

Provides several natural trigger phrases ('apollo hello world', 'apollo example', 'apollo quick start', 'simple apollo code', 'test apollo api') that a user would plausibly say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped to the Apollo.io niche with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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