CtrlK
BlogDocsLog inGet started
Tessl Logo

customerio-known-pitfalls

Identify and avoid Customer.io anti-patterns and gotchas. Use when reviewing integrations, onboarding developers, or auditing existing Customer.io code. Trigger: "customer.io mistakes", "customer.io anti-patterns", "customer.io gotchas", "customer.io pitfalls", "customer.io code review".

64

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

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 pitfall catalog with concrete WRONG/CORRECT code and a runnable audit script, weakened by a redundant quick-reference table and bundle files that exist but are never referenced from the body. It reads as a monolithic reference rather than an overview that delegates detail to its references.

Suggestions

Link the existing references/ files from the body (e.g., 'For full setup details, see references/implementation-guide.md') so progressive disclosure is one level deep and signaled, rather than keeping everything inline.

Remove or shrink the Quick Reference table since it duplicates the 12 pitfalls already detailed above, reclaiming tokens without losing information.

Add a short validate→fix→retry loop after the audit script (e.g., re-run the audit until all checks report OK) to give the workflow explicit checkpoints.

DimensionReasoningScore

Conciseness

The body is mostly efficient and the per-pitfall 'Why' notes are Customer.io-specific (not concepts Claude already knows), but the Quick Reference table restates all 12 pitfalls already detailed above, which could be tightened.

2 / 3

Actionability

Every pitfall gives copy-paste-ready WRONG vs CORRECT TypeScript, and the Integration Audit Script provides concrete, runnable grep commands — fully executable guidance.

3 / 3

Workflow Clarity

The audit script is sequenced with per-check feedback ('|| echo OK'), but as a reference catalog it lacks an explicit validate→fix→retry workflow with checkpoints, so it sits at 'steps listed but checkpoints missing or implicit'.

2 / 3

Progressive Disclosure

Bundle files exist in references/ (implementation-guide.md, implementation.md) but are never linked or signaled from the body, and the full 12-pitfall catalog is kept inline rather than split out, matching 'references present but not clearly signaled; content that should be separate is inline'.

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 focused, well-structured description that clearly states purpose, usage context, and natural trigger terms for a distinct Customer.io niche. The only weakness is that the capability verbs are generic ('identify and avoid') rather than enumerating concrete actions.

DimensionReasoningScore

Specificity

The description names the domain ('Customer.io anti-patterns and gotchas') and two actions ('Identify and avoid'), but the verbs are generic rather than a list of concrete actions like the level-3 anchor, so it sits at 'names domain and some actions, not comprehensive'.

2 / 3

Completeness

It answers both 'what' ('Identify and avoid Customer.io anti-patterns and gotchas') and 'when' ('Use when reviewing integrations, onboarding developers, or auditing existing Customer.io code') with explicit triggers, matching the level-3 anchor.

3 / 3

Trigger Term Quality

An explicit Trigger block lists five natural phrases a developer would say ('customer.io mistakes', 'customer.io anti-patterns', 'customer.io gotchas', 'customer.io pitfalls', 'customer.io code review'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

It targets a clear niche (Customer.io-specific mistakes) with distinct, product-named 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.