CtrlK
BlogDocsLog inGet started
Tessl Logo

klaviyo-automation

Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.

80

3.16x
Quality

Does it follow best practices?

Impact

95%

3.16x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

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.

A concrete, well-sequenced API-operation skill with actionable tool guidance and clear setup validation, weakened mainly by repeated pitfall content across sections and a monolithic single-file structure.

Suggestions

De-duplicate pitfalls: keep rate limits, status-value quirks, and response-nesting notes in one place (e.g., 'Known Pitfalls') and reference them from individual workflows rather than restating them.

Consider moving the Quick Reference table and/or detailed parameter reference into a reference file under ./references/ with a clearly signaled link from SKILL.md to improve progressive disclosure.

Add a brief 'Verify' note to read-heavy workflows (e.g., confirm pagination is exhausted, re-check status client-side) to make existing validation guidance more uniform across sections.

DimensionReasoningScore

Conciseness

The body is mostly efficient API guidance Claude would not already know, but pitfalls recur across sections (rate limits, case-sensitive compound statuses, response nesting appear both per-workflow and again under 'Known Pitfalls'), so it could be tightened.

2 / 3

Actionability

Provides exact tool slugs, concrete parameter names with example values ('equals(status,"draft")', sparse fieldset 'content.subject'), ID formats, and rate-limit numbers — specific, actionable guidance rather than pseudocode, which the rubric rewards for instruction-only skills.

3 / 3

Workflow Clarity

Setup is a numbered sequence with an explicit validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows'), and workflows use [Prerequisite]/[Required] ordering; operations are read-only so the destructive-feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

The skill is a single ~190-line file with no bundle/reference files and no split-out content; it exceeds the 'under 50 lines' simple-skill carve-out, and detailed reference material (Known Pitfalls, Quick Reference) is inline rather than in one-level-deep reference files.

2 / 3

Total

10

/

12

Passed

Description

67%

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 specific, well-scoped description with concrete capabilities and a clear niche, but it lacks an explicit 'Use when...' trigger clause and includes some technical jargon that weakens natural trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when the user asks to manage or inspect Klaviyo email/SMS campaigns, tags, or send jobs').

Move the operational instruction 'Always search tools first for current schemas' into the body, leaving the description focused on what the skill does and when to use it.

Soften technical phrasing like 'Rube MCP (Composio)' in favor of user-facing terms such as 'Klaviyo marketing automation'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs' — matching the level-3 anchor for several specific concrete actions, not just naming a domain.

3 / 3

Completeness

The 'what' is explicit, but there is no 'Use when...' or equivalent trigger clause; the closing sentence is an instruction rather than a usage trigger, so per the guidelines completeness caps at 2.

2 / 3

Trigger Term Quality

Relevant natural terms (Klaviyo, email/SMS campaigns, tags, send jobs) are present, but the phrase leans technical with 'Rube MCP (Composio)' and 'search tools first for current schemas', and omits common variations or a natural trigger clause.

2 / 3

Distinctiveness Conflict Risk

Klaviyo plus Rube MCP/Composio is a clear, branded niche with distinct triggers unlikely to collide with other skills, matching the level-3 anchor.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.