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".

64

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/customerio-pack/skills/customerio-debug-bundle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 complete, executable scripts and a clear step sequence, but it is verbose and duplicates the reference file while never pointing to it. Workflow clarity and progressive disclosure suffer from missing interleaved validation and an unlinked, redundant bundle file.

Suggestions

Link references/implementation-guide.md from the body (or move the full scripts there) so SKILL.md stays an overview and the reference is clearly signaled, removing the duplication.

Add interleaved validation checkpoints (e.g., verify API auth HTTP codes before proceeding to user investigation) and a validate-fix-retry loop for failed checks.

Trim the inline scripts to the essential snippets or reference the bundle files for the full versions to reduce token weight while preserving actionability.

DimensionReasoningScore

Conciseness

The body is mostly executable code with little concept explanation, but it runs ~250 lines with five full inline scripts and substantially duplicates references/implementation-guide.md, so it could be tightened.

2 / 3

Actionability

It provides fully executable bash/curl and TypeScript scripts (Steps 1–5) with specific commands and redaction logic, making the guidance copy-paste ready.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced with a Debug Checklist and Error Handling table, but there are no interleaved validation checkpoints or validate-fix-retry feedback loops within the workflow.

2 / 3

Progressive Disclosure

A bundle file (references/implementation-guide.md) exists but is never linked from the body, and detailed scripts that belong in the reference are inlined, so references are present but not clearly signaled.

2 / 3

Total

9

/

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 communicates a focused purpose, explicit use-when guidance, and natural trigger phrases, scoring well on completeness and distinctiveness. Specificity is slightly lower because the Use-when scenarios are framed as user tasks rather than distinct actions the skill performs.

DimensionReasoningScore

Specificity

It names the domain and one concrete action ("Collect Customer.io debug evidence for support tickets"), while "investigating delivery failures" and "documenting integration issues" are use-case scenarios rather than distinct skill actions, so it is not comprehensive.

2 / 3

Completeness

It clearly answers what ("Collect Customer.io debug evidence for support tickets") and when ("Use when creating support requests, investigating delivery failures, or documenting integration issues") with explicit triggers.

3 / 3

Trigger Term Quality

An explicit Trigger clause lists natural phrases users would say ("customer.io debug", "customer.io support ticket", "collect customer.io logs", "customer.io diagnostics"), giving good coverage.

3 / 3

Distinctiveness Conflict Risk

It targets a clear niche (Customer.io debug evidence for support tickets) with distinct, domain-specific triggers, making conflict with other skills unlikely.

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.