Name: klaviyo
Rating: 63.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

klaviyo

Klaviyo integration. Manage Persons, Campaigns, Flows, Events. Use when the user wants to interact with Klaviyo data.

Quality

75%

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

71%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 executable CLI commands and a well-branched connection workflow including feedback loops. It loses points for some redundant/padded explanation, a dangling "Step 2" reference, and a monolithic single-file structure that could split detail into references.

Suggestions

Remove the introductory paragraph explaining what Klaviyo is and trim the redundant "Popular actions" section that re-states the action-list command already shown in "Searching for actions".

Label the post-connection workflow step explicitly as "Step 2" (or reword the "Skip to Step 2" references) so navigation targets are unambiguous.

Move the detailed clientAction field breakdown and the proxy flag table into separate reference files (e.g. CONNECTION_STATES.md, PROXY.md) and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Klaviyo is ("email and SMS marketing automation platform... e-commerce businesses") which Claude already knows, and the "Popular actions" section duplicates the earlier search command, so the body is mostly efficient but could be tightened.	3 / 5
Actionability	Concrete, copy-paste-ready commands are provided throughout (membrane connection ensure, action list/run, request) with a complete flag table for the proxy, covering the common cases fully.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and explicit poll-again feedback loops, but the "Skip to Step 2" reference points at a step that is not clearly labeled, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	The 146-line body is organized into sections but is a single monolithic file with no external references; the detailed clientAction breakdown and proxy flag table could live in separate reference files, and the "Popular actions" section is a thin stub.	3 / 5
	Total	15 / 20 Passed

Description

78%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 well-targeted: it identifies Klaviyo by name, lists concrete managed entities, and includes an explicit "Use when" trigger in third-person voice. It is slightly generic in its trigger clause and lists entities rather than granular actions, capping a couple of dimensions just below the top anchor.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Campaigns, Flows, Events" names the Klaviyo domain and lists several concrete capabilities, though these are entities/resources rather than fully spelled-out actions, leaving minor coverage gaps.	4 / 5
Completeness	It states both a clear "what" ("Klaviyo integration. Manage Persons, Campaigns, Flows, Events.") and an explicit "when" ("Use when the user wants to interact with Klaviyo data."), but the trigger clause is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	Natural terms like "Klaviyo", "Campaigns", "Flows", "Events", and "interact with Klaviyo data" are present and would be said by users, but common synonyms or file/extension variants are missing.	4 / 5
Distinctiveness Conflict Risk	The named product "Klaviyo" with Klaviyo-specific resource types (Persons, Campaigns, Flows, Events) carves a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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: membranedev/application-skills
Path: skills/klaviyo/SKILL.md
Commit: f484c82

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.