CtrlK
BlogDocsLog inGet started
Tessl Logo

apollo-debug-bundle

Collect Apollo.io debug evidence for support. Use when preparing support tickets, documenting issues, or gathering diagnostic information for Apollo problems. Trigger with phrases like "apollo debug", "apollo support bundle", "collect apollo diagnostics", "apollo troubleshooting info".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 a clear sequenced workflow, but it is token-heavy because the full implementation is inlined instead of deferred to the existing reference file, which is left unlinked.

Suggestions

Replace the four inline TypeScript code blocks with a concise overview plus a link to references/implementation-guide.md, keeping only a minimal quick-start snippet in SKILL.md.

Add an explicit, clearly signaled reference to the existing implementation-guide.md (e.g., a 'Full implementation: See [implementation-guide.md](references/implementation-guide.md)' link) so the bundle file is no longer orphaned.

Consolidate the inline step code into a single contiguous script or trim redundant sections to reduce token cost while preserving actionability.

DimensionReasoningScore

Conciseness

The body is mostly efficient (executable code, no conceptual padding about what Apollo is), but it inlines ~170 lines of TypeScript across four steps that largely duplicate the bundled references/implementation-guide.md, so it could be tightened by deferring detail to that file.

2 / 3

Actionability

It provides complete, copy-paste-ready TypeScript plus concrete curl one-liners, specific endpoints, and an error-handling table — fully executable guidance rather than vague direction.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced (collect bundle → test connectivity/key type → test endpoints → generate/output) with an error-handling table that gives recovery feedback; this non-destructive diagnostic task does not require destructive/batch validation checkpoints.

3 / 3

Progressive Disclosure

A references/implementation-guide.md bundle file exists but is never linked from the body, while near-duplicate full implementation code is inlined in SKILL.md — content that should be separate is inline and the reference is orphaned, matching the 'references present but not clearly signaled' anchor.

2 / 3

Total

10

/

12

Passed

Description

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

A strong, third-person description that clearly states the skill's purpose, when to use it, and supplies natural trigger phrases. It is concise without padding and carries no over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Collect Apollo.io debug evidence', 'preparing support tickets', 'documenting issues', 'gathering diagnostic information' — rather than vague language, matching the anchor that enumerates specific capabilities.

3 / 3

Completeness

It explicitly states both what ('Collect Apollo.io debug evidence for support') and when ('Use when preparing support tickets, documenting issues, or gathering diagnostic information for Apollo problems') with explicit triggers, satisfying the highest anchor.

3 / 3

Trigger Term Quality

It includes natural trigger phrases a user would actually say ('apollo debug', 'apollo support bundle', 'collect apollo diagnostics', 'apollo troubleshooting info'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Apollo.io debug-bundle niche is specific and the triggers are Apollo-scoped, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.