convertkit-automation
Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.
69
58%
Does it follow best practices?
Impact
83%
1.16xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/convertkit-automation/SKILL.mdQuality
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 is strong in specificity and distinctiveness, clearly naming the platform, integration method, and concrete entities it manages. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing common natural language trigger terms that users might use (e.g., 'email marketing', 'newsletter', 'email list').
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ConvertKit, Kit, email marketing subscribers, or newsletter management.'
Include broader natural trigger terms like 'email marketing', 'newsletter', 'email list', 'mailing list', or 'email campaigns' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: manage subscribers, tags, broadcasts, and broadcast stats. Also specifies the automation platform (ConvertKit/Kit) and the integration method (Rube MCP/Composio). | 3 / 3 |
Completeness | Clearly answers 'what' (automate ConvertKit tasks via Rube MCP), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the mention of ConvertKit-related entities, capping this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes good domain-specific terms like 'ConvertKit', 'Kit', 'subscribers', 'tags', 'broadcasts', and 'broadcast stats'. However, it misses common user variations like 'email marketing', 'email list', 'newsletter', 'email campaigns', or 'mailing list' that users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform (ConvertKit/Kit) and integration method (Rube MCP/Composio). Unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%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 coverage of ConvertKit/Kit operations with clear tool sequences and useful pitfall documentation. Its main weaknesses are redundancy across sections (pitfalls repeated in workflows and in the dedicated section), lack of executable examples, and missing explicit validation/confirmation steps for destructive operations like deletion and unsubscription. The content would benefit from deduplication and adding proper feedback loops for irreversible actions.
Suggestions
Add explicit confirmation/validation steps in destructive workflows (Delete Broadcast, Unsubscribe): e.g., 'Verify the broadcast details match what the user expects before calling DELETE' as a numbered step, not just a pitfall note.
Deduplicate pitfalls—consolidate all pitfalls into the 'Known Pitfalls' section and reference it from individual workflows instead of repeating the same information.
Replace pseudocode in 'Common Patterns' with actual MCP tool call examples showing the exact parameter format Claude should use.
Consider splitting the detailed workflow descriptions into a separate WORKFLOWS.md file, keeping SKILL.md as a concise overview with the quick reference table and links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but contains some redundancy—pitfalls are repeated across individual workflows and then again in the 'Known Pitfalls' section (e.g., ID formats, include_total_count being a string). Some information like 'ConvertKit (now known as Kit)' and the Composio branding line are unnecessary filler. The content could be tightened by ~30% without losing information. | 2 / 3 |
Actionability | The skill provides clear tool names, parameter lists, and step sequences, which is good. However, there are no executable code examples—the 'Common Patterns' section uses plain text pseudocode rather than actual MCP tool call syntax. The guidance is concrete enough to follow but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional), which is helpful. However, destructive operations like Delete Broadcast and Unsubscribe lack explicit validation/confirmation checkpoints—'Confirm the broadcast ID before deleting' is mentioned as a pitfall rather than an enforced workflow step with a feedback loop. This caps the score at 2 per the rubric's feedback loop requirement for destructive changes. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a quick reference table, but it's quite long (~180+ lines) and could benefit from splitting detailed workflow descriptions and pitfalls into separate reference files. The toolkit docs link is provided but all detailed content is inline rather than appropriately split. | 2 / 3 |
Total | 8 / 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 | |
- Repository
- Lingjie-chen/MT5
- Commit
3069d33
- 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.