apollo-security-basics

Apply Apollo.io API security best practices. Use when securing Apollo integrations, managing API keys, or implementing secure data handling. Trigger with phrases like "apollo security", "secure apollo api", "apollo api key security", "apollo data protection".

Quality

83%

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

Quality

Content

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

The body is highly actionable with executable code and well-sequenced workflows that include real validation checkpoints (rotation verifies before revoking). Its weaknesses are verbosity from duplicating the separate implementation guide inline and a progressive-disclosure failure where that reference file is never linked from the body.

Suggestions

Link references/implementation-guide.md from the body (e.g., a 'Full implementation details' pointer near the relevant steps) and move the full code listings there, keeping SKILL.md a lean overview.

Trim the inline code in Steps 1-5 to the essential patterns, leaving complete runnable examples to the implementation guide to reduce token duplication.

Add a short 'See also' navigation line so the existing reference bundle is discoverable instead of orphaned.

Dimension	Reasoning	Score
Conciseness	The body avoids over-explaining concepts Claude knows, but it carries ~200 lines of full inline implementations (getApiKey, redactPII, scoped clients, rotation, audit) that duplicate material in the 354-line implementation-guide.md, so it is mostly efficient but could be tightened — matching the level-2 anchor rather than the lean level-3 anchor.	2 / 3
Actionability	Quotes fully executable TypeScript blocks for getApiKey, redactPII, createReadOnlyClient/createFullAccessClient, rotateApiKey, and runSecurityAudit with specific imports and commands, all copy-paste ready — matching the level-3 anchor.	3 / 3
Workflow Clarity	The five steps are clearly sequenced, and the destructive key-rotation step verifies the new key via an auth-health check that aborts on failure before revoking the old key, while the audit step is a pass/fail checklist — matching the level-3 anchor's explicit validation and feedback loops.	3 / 3
Progressive Disclosure	A bundle file references/implementation-guide.md (354 lines) exists but is never linked or signaled anywhere in the body, and its content is largely duplicated inline — matching the level-2 anchor (reference present but not clearly signaled; content that should be separate is inline) rather than level 3's well-signaled one-level-deep references; it is not level 1 because the body itself is well-sectioned rather than a monolithic wall.	2 / 3
	Total	10 / 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.

The description clearly answers both what and when with explicit trigger phrases in third-person voice and a distinct Apollo.io niche, though the stated actions are somewhat abstract rather than concrete operations. Specificity is the only dimension capped at 2; the rest score full marks.

Dimension	Reasoning	Score
Specificity	Quotes 'Apply Apollo.io API security best practices' and 'securing Apollo integrations, managing API keys, or implementing secure data handling' name the domain and several actions, but the verbs (secure/manage/implement) are abstract rather than concrete operations like 'extract, fill, merge', so it stops short of level 3 and is well above level 1's vagueness.	2 / 3
Completeness	Quotes 'Apply Apollo.io API security best practices' (what) plus 'Use when securing Apollo integrations, managing API keys...' (when) and explicit 'Trigger with phrases like...' guidance clearly answer both what and when, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Quotes 'apollo security', 'secure apollo api', 'apollo api key security', and 'apollo data protection' give good coverage of natural phrasings a user would say when needing this skill, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The Apollo.io-specific niche and distinct triggers ('apollo security', 'secure apollo api') make it unlikely to fire for unrelated skills, matching the level-3 anchor.	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
Path: plugins/saas-packs/apollo-pack/skills/apollo-security-basics/SKILL.md
Commit: 4c47e33

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.