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.

3.16x

Quality

68%

Does it follow best practices?

Impact

95%

3.16x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/klaviyo-automation/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable reference for Klaviyo read operations with clear workflow sequencing and genuine pitfall knowledge (response nesting, compound statuses, strict tag rate limits). Its main cost is redundancy: several pitfall details are stated twice, inflating token usage without adding information.

Suggestions

Consolidate the duplicated rate-limit, pagination, and status-validation notes into the single 'Known Pitfalls' section and remove them from per-workflow Pitfalls blocks.

Move the exhaustive parameter lists and sparse-fieldset/filter-syntax reference into a references/ file, keeping SKILL.md as an overview with the Quick Reference table.

Add one example tool-call payload per workflow (e.g., a sample KLAVIYO_GET_CAMPAIGNS request/response snippet) to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient reference material, but rate limits, pagination, status-validation, and sparse-fieldset details are each repeated across the per-workflow Pitfalls and the Known Pitfalls/Common Patterns sections, and the 'Powered by Composio' footer is pure padding.	3 / 5
Actionability	Concrete tool slugs, real parameter names, example IDs ('01GDDKASAP8TKDDA2GRZDSVP4H'), executable filter syntax (equals(status,"draft")), and a quick-reference table give mostly executable guidance, with the minor gap of no example tool-call payloads.	4 / 5
Workflow Clarity	Each workflow has a 'When to use' cue and a numbered tool sequence, and setup includes an explicit checkpoint ('Confirm connection status shows ACTIVE before running any workflows'); operations are read-only so the destructive/batch cap does not apply, but error recovery beyond 'implement backoff on 429' is thin.	4 / 5
Progressive Disclosure	Well-organized sections with a Quick Reference table make the single-file skill navigable, and no bundle files exist; however, ~190 lines of API-reference detail (rate limits, fieldset syntax, status values) could arguably live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 strong, product-specific description with concrete action verbs and good natural keywords. Its main weaknesses are the missing explicit 'when to use' clause and the slightly generic 'manage campaigns' phrasing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Klaviyo, email/SMS campaign status, or marketing campaign metrics'.

Replace the generic 'manage email/SMS campaigns' with concrete read operations like 'list and filter campaigns' to match the actual toolset and avoid over-claiming.

Include common synonyms such as 'newsletter' or 'marketing automation' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('inspect campaign messages, track tags, and monitor send jobs') but 'manage email/SMS campaigns' is generic and slightly overstates the read-only toolset, leaving minor gaps in coverage.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Klaviyo', 'email/SMS campaigns', 'campaign messages', 'send jobs'), but misses common variations such as 'newsletter', 'marketing automation', or 'flows'.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Klaviyo' (plus 'Rube MCP'/'Composio') gives a clear niche with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/klaviyo-automation/SKILL.md
Commit: b90e2de

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.