klaviyo

Klaviyo email/SMS marketing - profiles, events, flows, segmentation

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/klaviyo/SKILL.md

Quality

Content

65%

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

The skill is highly actionable with executable multi-language code and good section organization, but it is overly long, mixes redundant boilerplate with reference material, and uses no progressive file splitting despite its size.

Suggestions

Split the large API reference and per-language installation/example code into references/ files (e.g. REFERENCE.md, EXAMPLES.md) and keep SKILL.md a concise overview that links to them, improving progressive disclosure and conciseness.

Trim boilerplate Claude already knows — the "Why Klaviyo" benefits table and basic scope/installation explanations — to tighten conciseness toward level 3.

Add explicit validate→fix→retry feedback loops for batch and destructive operations (rate-limited bulk sync, pagination, webhook signature verification) so workflow clarity can reach 3.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and full of useful executable code, but it is ~810 lines and padded with boilerplate Claude already knows (the "Why Klaviyo" benefits table, scope/installation tables, and code duplicated across languages), which is the level-2 "mostly efficient but could be tightened" anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript, Python, and HTML snippets with real endpoints, headers, and payloads — matching the level-3 "fully executable code, specific examples" anchor.	3 / 3
Workflow Clarity	Sequences integration patterns (order sync steps 1-3) and provides checklists, but batch/destructive operations like rate limiting, pagination, and webhook handling lack explicit validate→fix→retry feedback loops, which the rubric says caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Well-organized with clear sections, but it is a monolithic single file with no references/scripts/assets bundle — large API reference and per-language code that could be split out are inline rather than one-level-deep, matching the level-2 "structure present but content that should be separate is inline" anchor.	2 / 3
	Total	9 / 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.

The description is specific and clearly niched to Klaviyo, but it is terse and omits an explicit "Use when..." trigger clause, which caps completeness and weakens trigger guidance.

Suggestions

Add an explicit "Use when..." trigger clause to the description field (e.g. "Use when integrating Klaviyo for email/SMS marketing, event tracking, or customer segmentation") so completeness can reach 3.

Expand natural trigger terms to cover variations users would say — campaigns, lists, marketing automation, segments — rather than only "email/SMS marketing".

Consider folding the when-to-use frontmatter guidance into the description so the trigger is visible wherever the description is shown.

Dimension	Reasoning	Score
Specificity	Names the domain (Klaviyo email/SMS marketing) and multiple concrete capabilities — "profiles, events, flows, segmentation" — matching the rubric's level-3 example of listing several specific actions.	3 / 3
Completeness	It clearly answers "what" (profiles, events, flows, segmentation) but the description field has no explicit "Use when..." trigger clause — the trigger lives only in the separate when-to-use frontmatter — so completeness is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Contains relevant natural terms ("email/SMS marketing", "Klaviyo") but is terse and lacks common variations a user would say (e.g. campaigns, lists, segments, flows are present but "marketing automation" phrasing is thin), so it sits at the "some keywords, missing variations" level.	2 / 3
Distinctiveness Conflict Risk	Klaviyo-specific naming with email/SMS marketing context gives it a clear niche unlikely to trigger for unrelated skills, matching the level-3 "clear niche with distinct triggers" anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (810 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/klaviyo/SKILL.md
Commit: bb6195f

Reviewed: 6 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.