CtrlK
BlogDocsLog inGet started
Tessl Logo

apollo-performance-tuning

Optimize Apollo.io API performance. Use when improving API response times, reducing latency, or optimizing bulk operations. Trigger with phrases like "apollo performance", "optimize apollo", "apollo slow", "apollo latency", "speed up apollo".

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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 and concise, with complete executable TypeScript for six optimization techniques. Its weaknesses are the lack of explicit validation feedback loops in the batch workflows and an orphaned reference file that is never linked from SKILL.md.

Suggestions

Add explicit validation checkpoints to the batch and parallel workflows (e.g. verify bulk_match result count against the input batch and retry failed records before proceeding).

Link references/implementation-guide.md from the body (e.g. a '## Full implementation' section pointing to it) and move the duplicated code detail there so SKILL.md stays a concise overview.

Tighten or remove the Output recap section, which restates techniques already shown in the steps.

DimensionReasoningScore

Conciseness

The body is lean and code-heavy with brief justifications, assumes Claude's competence (no explaining what axios or an LRU cache is), and avoids padding with basic concepts; the only minor redundancy is the Output recap.

3 / 3

Actionability

Each step provides complete, executable TypeScript with imports and file paths (e.g. '// src/apollo/optimized-client.ts'), making the guidance copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

The six steps are clearly sequenced and a benchmark step plus error-handling table exist, but there are no explicit validate->fix->retry checkpoints within the batch enrichment and parallel search operations, which the rubric caps at 2 for batch operations.

2 / 3

Progressive Disclosure

Sections are well organized, but a bundle file (references/implementation-guide.md) exists and is never linked or signaled from the body, while ~230 lines of overlapping code remain inline rather than being split out.

2 / 3

Total

10

/

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 an explicit 'Use when' clause and natural Apollo-specific trigger phrases, giving it strong completeness and trigger quality. Its only weakness is specificity, since it frames tasks as goals rather than naming the concrete optimization techniques.

DimensionReasoningScore

Specificity

Names the Apollo.io API domain and some tasks ('improving API response times, reducing latency, or optimizing bulk operations'), but these are goals/outcomes rather than multiple concrete named actions like caching or connection pooling.

2 / 3

Completeness

Explicitly states what it does ('Optimize Apollo.io API performance') and when to use it via a 'Use when...' clause plus concrete trigger phrases, answering both what and when.

3 / 3

Trigger Term Quality

Lists natural phrases a user would actually say ('apollo performance', 'apollo slow', 'apollo latency', 'speed up apollo'), giving good coverage of likely trigger terms.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear Apollo.io performance niche with Apollo-specific triggers (4 of 5 unambiguously performance-related), making it unlikely to fire for an unrelated skill.

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.