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.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill klaviyo-automation71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 effectively communicates specific Klaviyo automation capabilities and is highly distinctive due to platform-specific terminology. However, it lacks an explicit 'Use when...' clause and could benefit from additional natural trigger terms that users might say when needing email marketing help.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Klaviyo', 'email marketing', 'SMS marketing', 'campaign automation', or 'marketing platform'.
Include common user variations such as 'newsletter', 'subscriber management', 'email automation', or 'marketing campaigns' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific capabilities, but lacks an explicit 'Use when...' clause. The when is only implied through the domain context (Klaviyo tasks). | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Klaviyo', 'email/SMS campaigns', 'tags', 'send jobs', but missing common user variations like 'marketing automation', 'email marketing', 'subscriber lists', or 'newsletter'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with 'Klaviyo' and 'Rube MCP (Composio)' as specific identifiers. Unlikely to conflict with other skills due to the platform-specific focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid workflow guidance for Klaviyo automation with clear tool sequences and comprehensive pitfall documentation. However, it lacks concrete executable examples (actual tool call syntax with parameters), contains some redundancy across sections, and could benefit from splitting detailed reference material into separate files for better progressive disclosure.
Suggestions
Add concrete tool invocation examples showing actual parameter values and expected response structures, not just pseudocode patterns
Consolidate redundant information (rate limits, pagination, status handling) into single authoritative sections to reduce token usage
Consider splitting the Common Patterns and Known Pitfalls sections into a separate REFERENCE.md file, keeping SKILL.md focused on core workflows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the pitfalls sections repeat information (e.g., rate limits mentioned multiple times, pagination explained in both workflow and common patterns sections). The quick reference table at the end duplicates information already covered in workflows. | 2 / 3 |
Actionability | Provides clear tool sequences and parameter lists, but lacks executable code examples. The 'Campaign Discovery Pattern' shows pseudocode-style steps rather than actual tool invocation syntax. No concrete examples of actual tool calls with real parameter values are provided. | 2 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps, prerequisite markers, and explicit tool sequences. The pagination workflow includes clear continuation criteria ('Continue until no more cursor is returned'). Validation guidance is present (e.g., 'always validate client-side'). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single file. The skill is ~150 lines and could benefit from splitting detailed patterns, pitfalls, or API reference into separate files. The external link to Composio docs is good, but internal progressive disclosure is lacking. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.