CtrlK
BlogDocsLog inGet started
Tessl Logo

customerio-primary-workflow

Implement Customer.io primary messaging workflow. Use when setting up campaign triggers, welcome sequences, onboarding flows, or event-driven email automation. Trigger: "customer.io campaign", "customer.io workflow", "customer.io email automation", "customer.io messaging", "customer.io onboarding".

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-primary-workflow/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.

Highly actionable with executable, copy-paste-ready code and clear sequencing, but it is verbose relative to its existing reference file and lacks validation feedback loops for the dashboard/batch steps. The bundled reference is real but never linked from the body, weakening progressive disclosure.

Suggestions

Link to references/implementation-guide.md from the body (e.g., a 'Full implementation guide' pointer) and trim the inlined MessagingService/event taxonomy so the SKILL.md stays a lean overview.

Add an explicit validate/retry checkpoint for event-name and Liquid-variable contracts before publishing campaigns (e.g., verify event names match the dashboard exactly and test Liquid rendering on a sample profile).

Replace the general Error Handling table's 'deduplication' advice with a concrete dedup/idempotency code pattern so the fix is executable rather than descriptive.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code and tight tables, but the inline full MessagingService and large event taxonomy repeat much of what the references/implementation-guide.md already covers, adding length that could be offloaded.

2 / 3

Actionability

Provides complete, executable TypeScript (event taxonomy, MessagingService, route integration) plus a concrete Liquid-variable table and dashboard campaign steps with specific waits and branches.

3 / 3

Workflow Clarity

A clear 4-step sequence and an ASCII diagram exist, and fire-and-forget error handling is shown, but there is no validate/verify checkpoint for the batch-like dashboard steps or event-name contract, and no retry/feedback loop, capping clarity at 2 per the destructive/batch guideline.

2 / 3

Progressive Disclosure

A references/implementation-guide.md exists and is one level deep, but the body never links to it and instead inlines near-duplicate content, so the reference is unsignaled and content that should be split is inline.

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.

A well-constructed description with an explicit Use-when clause, natural trigger keywords, and a clear customer.io niche. It is slightly general in its action list, but strong overall.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('campaign triggers, welcome sequences, onboarding flows, event-driven email automation'), but the actions overlap conceptually and are not maximally distinct/concrete as a list.

2 / 3

Completeness

Clearly answers both 'what' (implement Customer.io primary messaging workflow) and 'when' via an explicit 'Use when...' clause plus a Trigger keyword block, satisfying the full completeness anchor.

3 / 3

Trigger Term Quality

Explicit Trigger block offers good coverage of natural phrasings users would say ('customer.io campaign', 'customer.io workflow', 'customer.io email automation', 'customer.io messaging', 'customer.io onboarding').

3 / 3

Distinctiveness Conflict Risk

The 'customer.io' qualifier across all triggers carves a clear niche, 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.