CtrlK
BlogDocsLog inGet started
Tessl Logo

apollo-sdk-patterns

Apply production-ready Apollo.io SDK patterns. Use when implementing Apollo integrations, refactoring API usage, or establishing team coding standards. Trigger with phrases like "apollo sdk patterns", "apollo best practices", "apollo code patterns", "idiomatic apollo", "apollo client wrapper".

64

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

65%

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

A highly actionable, well-structured patterns skill with complete executable code, but it is held back by duplicated content (an unreferenced implementation guide), a missing validation checkpoint on the batch enrichment path, and modest recap redundancy.

Suggestions

Add an explicit verification checkpoint to the bulk-enrichment workflow (e.g. validate batch input, check data.matches per batch, and handle/report partial failures before proceeding) so the batch operation has a feedback loop.

Link to references/implementation-guide.md from the body (e.g. a '## Full implementation' section) and de-duplicate the overlapping client/retry/pagination/error code between the two files so the reference is discoverable and the body is leaner.

Trim the Output recap and fold the full-pipeline Example into the relevant steps, keeping only the cross-pattern composition that is not already shown inline.

DimensionReasoningScore

Conciseness

The body is mostly lean code with brief, Apollo-specific intros, but the Output section restates what each code block already shows and the Examples section re-demonstrates patterns already presented; a near-duplicate implementation-guide.md reference further inflates the effective token footprint.

2 / 3

Actionability

Every step ships complete, executable TypeScript with file paths, imports, and real endpoints (e.g. /people/bulk_match, x-api-key header); the code is copy-paste ready and specific.

3 / 3

Workflow Clarity

Steps 1-5 form a clear build-up (client, errors, retry, pagination, bulk), but the batch bulk-enrichment operation has no validation or verification checkpoint, capping workflow clarity at 2 per the batch-operations guideline.

2 / 3

Progressive Disclosure

The body is well sectioned, but the bundled references/implementation-guide.md is never linked or signaled from the body and largely duplicates inline content, so material that should be split out remains inline and the reference is undiscoverable.

2 / 3

Total

9

/

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.

A strong description with explicit what/when structure and a rich set of natural trigger phrases. The only weakness is a somewhat abstract capability statement that leans on "production-ready patterns" rather than naming the concrete techniques the skill provides.

DimensionReasoningScore

Specificity

Names the Apollo.io domain and a broad action ("Apply production-ready Apollo.io SDK patterns") but the capability statement is abstract; the concrete capabilities (retry, pagination, bulk enrichment) are not surfaced in the description itself, only in the body.

2 / 3

Completeness

Clearly answers both what ("Apply production-ready Apollo.io SDK patterns") and when ("Use when implementing Apollo integrations, refactoring API usage, or establishing team coding standards") with explicit trigger guidance.

3 / 3

Trigger Term Quality

Explicitly lists natural trigger phrases a user would say ("apollo sdk patterns", "apollo best practices", "apollo code patterns", "idiomatic apollo", "apollo client wrapper"), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a specific, well-scoped niche (Apollo.io SDK patterns) with distinct Apollo-branded 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.