klaviyo

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

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

53%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.

The content is highly actionable with thorough executable code, but it is a monolithic ~800-line inline reference that ignores progressive disclosure and is padded with redundant variants and explanatory material Claude already knows. Batch operations lack validation checkpoints.

Suggestions

Move the bulk API reference (profiles, events, lists, flows, webhooks) into separate reference files under references/ and keep SKILL.md as a concise overview pointing to them.

Drop concept padding Claude already knows (e.g. the 'Why Klaviyo' benefits table, 'API Key Scopes') and collapse redundant TS/Python variants to one unless both are essential.

Add validation/verification checkpoints to batch operations (e.g. verify list-add counts, confirm pagination completeness) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The ~800-line body inlines large API reference blocks with redundant TS/Python variants and padded sections ('Why Klaviyo' benefits table, 'API Key Scopes') that Claude could fetch from the linked docs, matching anchor 2; not 3 because the volume of inline reference padding is substantial.	2 / 5
Actionability	Provides fully executable, copy-paste-ready code across profiles, events, lists, webhooks, rate-limit retry, pagination, and filtering that covers the common e-commerce cases, matching anchor 5.	5 / 5
Workflow Clarity	Integration patterns (Order Sync, Subscription Sync) are numbered and a Setup/Integration/Testing checklist exists, but batch operations (bulk list add, getAllProfiles) lack validation checkpoints and no validate->fix->retry feedback loop is present, capping at 3 per the batch-operation guideline; not 4 because checkpoints are missing rather than minor.	3 / 5
Progressive Disclosure	No bundle files exist and the entire API reference (profiles, events, lists, flows, webhooks) is inlined in SKILL.md, matching anchor 2 ('content that clearly belongs in separate files is inlined'); not 3 because there is no reference-file structure or signaling at all.	2 / 5
	Total	12 / 20 Passed

Description

62%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.

The description is product-specific and reasonably specific about capabilities but lacks an explicit 'Use when' trigger clause, capping its completeness. Trigger terms cover the core domain without synonyms or variations.

Suggestions

Add an explicit 'Use when' trigger clause, e.g. 'Use when integrating Klaviyo for email/SMS marketing, customer profiles, event tracking, or segmentation.'

Expand trigger-term coverage with synonyms users actually say (e.g. 'email campaigns', 'marketing automation', 'newsletters', 'abandoned cart').

Reframe capability nouns as concrete verbs (e.g. 'Track events, sync profiles, build flows, segment audiences') to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Klaviyo email/SMS marketing') and lists several concrete capability areas ('profiles, events, flows, segmentation'), matching anchor 4 with minor coverage gaps; not 5 because capabilities are nouns without action verbs.	4 / 5
Completeness	Provides a clear 'what' via the capability list but the description has no 'Use when...' trigger clause, so per the missing-trigger guideline completeness caps at 3; not 4 because 'when' is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	Includes relevant keywords a user might say ('Klaviyo', 'email/SMS marketing', 'profiles', 'events', 'flows', 'segmentation') but lacks synonyms and product-name variations, matching anchor 3; not 4 because natural-term coverage is incomplete.	3 / 5
Distinctiveness Conflict Risk	Names the specific product Klaviyo, giving it a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.	5 / 5
	Total	15 / 20 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: abc600e

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.