CtrlK
BlogDocsLog inGet started
Tessl Logo

customerio-debug-bundle

Collect Customer.io debug evidence for support tickets. Use when creating support requests, investigating delivery failures, or documenting integration issues. Trigger: "customer.io debug", "customer.io support ticket", "collect customer.io logs", "customer.io diagnostics".

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 presents a well-sequenced, validated diagnostic workflow with error-recovery guidance. Its weaknesses are token length from inlining all scripts and an orphaned reference file that is never linked, which hurt conciseness and progressive disclosure.

Suggestions

Move the five inline scripts into references/implementation-guide.md and link to it from the body, keeping only a concise overview and quick-start inline — this improves both progressive disclosure and conciseness.

Add a navigation pointer (e.g., a '## Full implementation guide' section linking to references/implementation-guide.md) so the bundled reference is discoverable rather than orphaned.

Trim the Step 4 report template and the 'Current State' command blocks or relocate them to the reference to tighten the token budget while preserving the actionable core.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and the code earns its place, but at ~256 lines with five full scripts inlined it is not lean; it could be tightened by moving scripts into the existing reference file, so it sits at the 'mostly efficient but could be tightened' anchor rather than score 3.

2 / 3

Actionability

It provides fully executable bash (set -euo pipefail, real curl calls) and complete TypeScript with invocations, plus concrete grep/docker log commands — copy-paste ready and free of pseudocode, matching the score-3 anchor.

3 / 3

Workflow Clarity

Five steps are clearly sequenced with explicit validation (HTTP-code checks and a checklist requiring 'HTTP 200'), an Error Handling table for recovery feedback, and a debug checklist, matching the score-3 anchor; the workflow is read-only diagnostics, so the destructive/batch cap does not apply.

3 / 3

Progressive Disclosure

Section organization is reasonable (Overview, Prerequisites, Steps, Checklist, Error Handling, Resources), but roughly 200 lines of scripts that belong in a separate file are inlined, and the provided references/implementation-guide.md is never linked from the body — 'references present but not clearly signaled' with content that should be separate kept inline, which is the score-2 anchor rather than the orphaned-reference score-1 or the well-split score-3.

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 strong: it states a concrete capability, provides an explicit 'Use when' clause, and lists natural trigger terms in a clear niche. Its only weakness is that it states a single primary action rather than enumerating multiple distinct capabilities.

DimensionReasoningScore

Specificity

It names the domain and one core concrete action ("Collect Customer.io debug evidence for support tickets") but does not list multiple specific capabilities the way a score-3 example does; the 'Use when' clauses describe use-cases, not distinct capabilities.

2 / 3

Completeness

It clearly answers both what ("Collect Customer.io debug evidence for support tickets") and when (an explicit "Use when..." clause plus explicit Trigger terms), matching the score-3 anchor; it is not missing the trigger guidance that would cap this at 2.

3 / 3

Trigger Term Quality

The explicit Trigger list ("customer.io debug", "customer.io support ticket", "collect customer.io logs", "customer.io diagnostics") gives good coverage of natural terms a user would actually say, matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

It carves a clear Customer.io debugging niche with distinct, product-specific triggers that are unlikely to fire for unrelated skills, matching the score-3 anchor.

3 / 3

Total

11

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 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

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

13

/

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.