Name: apollo
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

apollo

Apollo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Apollo data.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/apollo/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 a strong, executable guide: concrete CLI commands, a clear connection state machine with feedback loops, and tidy sectioning. Its main gaps are a broken 'Step 2' cross-reference and a thin Apollo-Overview section that adds little value.

Suggestions

Fix the dangling cross-reference: either label the next phase 'Step 2' or rewrite 'skip to Step 2' to point to the actual section ('Searching for actions').

Remove or replace the vague 'Apollo Overview' bullets ('Query — Represents a data request') with Apollo-specific objects (leads, contacts, sequences) Claude cannot infer.

Consider moving the proxy flag reference table into a separate REFERENCE.md so the core workflow stays lean and supports progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, with only minor over-explanation (e.g. the weak 'Apollo Overview' bullets and framing prose about auth plumbing), fitting the 4 anchor better than 3.	4 / 5
Actionability	It provides copy-paste-ready membrane commands with concrete flags and JSON examples covering connect, poll, search, run, and proxy cases, matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	The connect-to-run sequence has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but cross-references like 'skip to Step 2' point to no labeled Step 2 and the '1b' header has no '1a', so it falls just short of 5.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with headers and no nested references, but everything is inlined with no file-based split, so it sits at the well-structured 4 anchor rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

62%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 correctly pairs a what-statement with an explicit when-trigger and anchors on the distinct Apollo brand, but its action verbs and trigger keywords stay generic. Tightening 'manage data, records' into concrete Apollo-specific actions and adding natural synonyms would lift it.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Apollo capabilities such as 'search leads, enrich contact data, and sequence outreach'.

Add natural user phrasing and synonyms to the when-clause, e.g. 'Use when the user wants to find leads, look up contacts, or automate Apollo outreach.'

Mention recognizable Apollo objects (leads, contacts, sequences, accounts) to improve both specificity and trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names the Apollo domain plus a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic and coverage is not comprehensive, matching the 3 anchor.	3 / 5
Completeness	It gives a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Apollo data'), but the when-clause is generic rather than concrete trigger phrases, so it sits at 4 not 5.	4 / 5
Trigger Term Quality	'Apollo' is a natural term users would say, but the supporting keywords ('data', 'records', 'workflows') are generic with missing common variations, fitting the 3 anchor better than 4.	3 / 5
Distinctiveness Conflict Risk	The 'Apollo integration' framing names a specific platform, making it mostly distinct with only minor overlap risk against other data-tool skills, matching the 4 anchor.	4 / 5
	Total	14 / 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/apollo/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.