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

65

Quality

80%

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-known-pitfalls/SKILL.md
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 concise and highly actionable, with copy-paste code and a runnable audit script. Its main weaknesses are a lack of validation feedback loops around batch/destructive operations and failure to surface or link the existing reference bundle files for progressive disclosure.

Suggestions

Add an explicit validation/feedback step for batch and destructive operations (e.g., after the rate-limited import loop, verify a sample user landed via the activity-log curl before declaring success).

Link the existing references/implementation-guide.md and references/implementation.md from a 'Deeper reference' section so the one-level-deep bundle is discoverable from the body.

Tighten the grep audit script so its `grep -v` exclusions reliably surface the intended hits rather than masking them.

DimensionReasoningScore

Conciseness

Lean pitfall catalog with one WRONG/CORRECT pair and a one-line 'Why' per item; assumes Claude's competence and avoids explaining what Customer.io is or how the SDK works.

3 / 3

Actionability

Every pitfall gives fully executable TypeScript with specific correct snippets (e.g., Math.floor(Date.now() / 1000), singleton TrackClient, Bottleneck config), plus a runnable grep audit script and curl/jq troubleshooting commands.

3 / 3

Workflow Clarity

The catalog is a well-ordered checklist rather than a multi-step process, but the audit script and bulk operations (rate limiting, bounce handling) lack explicit validation/feedback checkpoints, which caps the score at 2 per the destructive/batch guideline.

2 / 3

Progressive Disclosure

The body is self-contained and useful, but it never signals the existing bundle files (references/implementation-guide.md and implementation.md) in the SKILL.md body; there is no navigation to those one-level-deep references, so structure is present but not clearly signaled.

2 / 3

Total

10

/

12

Passed

Description

82%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 states what the skill does and when to use it, with strong natural trigger terms and a distinct, low-conflict niche. It is slightly less strong on specificity because it lists contexts rather than multiple concrete technical actions.

Suggestions

Add a few concrete actions to the 'what' clause (e.g., 'detect wrong API keys, fix millisecond timestamps, suppress bounced users') to reach the multi-action specificity anchor.

Tighten the multi-line formatting so the description reads as a single concise sentence.

DimensionReasoningScore

Specificity

Names the domain ('Customer.io anti-patterns and gotchas') and a few actions ('reviewing integrations, onboarding developers, auditing'), but does not list multiple concrete technical actions; closer to anchor 2 than the multi-action anchor 3.

2 / 3

Completeness

Explicitly 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'), matching the 'what AND when' anchor.

3 / 3

Trigger Term Quality

Provides five natural phrases a user would actually 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

A narrow Customer.io-specific niche with distinct, brand-scoped triggers ('customer.io pitfalls', 'customer.io code review') makes it unlikely to conflict with other 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.