Name: apolloio
Rating: 64 (1 reviews)
Author: membranedev

apolloio

Apollo.io integration. Manage Persons, Organizations, Deals, Leads, Pipelines, Users and more. Use when the user wants to interact with Apollo.io data.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/apolloio/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

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

The body is highly actionable with executable commands throughout and a well-structured connection workflow with validation checkpoints. Its main weaknesses are minor: a slightly padded introductory paragraph and the absence of validation guidance for the batch/destructive actions it advertises.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and a tight actions table, but the opening paragraph ('Apollo.io is a sales intelligence and engagement platform...') explains context Claude largely already knows and could be trimmed, matching the 'efficient; minor over-explanation' anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready bash commands for install, login, connection ensure, action list/run, and proxy requests, plus a flag table and a popular-actions table — concrete guidance covering the common cases.	5 / 5
Workflow Clarity	The connection setup is a clear sequenced flow with polling/validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and an error-recovery loop, but there is no validation guidance for the listed batch/destructive actions (bulk-create/update), which is a minor gap keeping it below 5.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and an inlined overview table; no bundle files exist so there are no nested references, fitting 'good structure; most content appropriately placed' rather than 5 which requires signaled one-level-deep references.	4 / 5
	Total	17 / 20 Passed

Description

71%Weight 40%Scale 1-5

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 clearly identifies the Apollo.io niche and lists concrete entity types with an explicit use-when trigger, but the trigger phrasing is somewhat generic and lacks natural synonyms users would say. It is strong on distinctiveness and specificity but leaves room on trigger-term coverage.

Suggestions

Expand trigger terms with natural phrasings users actually say, e.g. 'search prospects, enrich contacts, manage deals and pipelines, or work with Apollo.io data'.

Replace the generic verb 'Manage' with concrete actions (create, search, update, enrich) to lift specificity toward comprehensive coverage.

Tighten the 'Use when' clause to reference concrete tasks (e.g. 'finding leads', 'enriching contact data', 'tracking deals') rather than the circular 'interact with Apollo.io data'.

Dimension	Reasoning	Score
Specificity	Names the Apollo.io domain and several concrete entity types ('Manage Persons, Organizations, Deals, Leads, Pipelines, Users'), but the verb 'Manage' is generic and 'and more' leaves coverage gaps, so it falls below the comprehensive 5 anchor.	4 / 5
Completeness	It has both a clear 'what' (manage listed entities) and an explicit 'Use when...' clause, but the 'when' trigger ('when the user wants to interact with Apollo.io data') is somewhat circular and could be more concrete, fitting the 4 anchor rather than 5.	4 / 5
Trigger Term Quality	It repeats 'Apollo.io' and offers 'interact with Apollo.io data', but lacks common synonyms or natural phrasings users would say (e.g. 'prospects', 'outreach', 'enrich contacts', 'sales intelligence'), matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	It explicitly names the Apollo.io application, carving a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/apolloio/SKILL.md
Commit: f484c82

Reviewed: 3 days 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.