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 ./plugins/all-skills/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 (ConvertKit/Kit), the integration method (Rube MCP/Composio), and concrete entities (subscribers, tags, broadcasts). However, it lacks an explicit 'Use when...' clause and misses common user-facing trigger terms like 'email marketing' or 'newsletter' that would help Claude match this skill to natural user requests.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ConvertKit, Kit, email marketing automation, or managing email subscribers and campaigns.'
Include broader natural trigger terms like 'email marketing', 'newsletter', 'mailing list', 'email campaigns', and 'email automation' to improve matching against how users naturally phrase requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: manage subscribers, tags, broadcasts, and broadcast stats. Also specifies the integration method (Rube MCP / Composio) and includes a procedural instruction to search tools first. | 3 / 3 |
Completeness | Clearly answers 'what' (automate ConvertKit tasks via Rube MCP, manage subscribers/tags/broadcasts), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied by the domain. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'ConvertKit', 'Kit', 'subscribers', 'tags', 'broadcasts', and 'broadcast stats', but misses common user variations like 'email marketing', 'email list', 'newsletter', 'mailing list', or 'email campaigns' that users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: ConvertKit/Kit automation via a specific MCP integration (Rube/Composio). Unlikely to conflict with other skills given the specific platform and tooling mentioned. | 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 via Rube MCP with well-labeled tool sequences and useful pitfall documentation. Its main weaknesses are redundancy across sections (pitfalls repeated in workflows and summary), lack of executable examples showing actual MCP tool call syntax, and missing explicit validation/error-handling steps for destructive operations like deletion and unsubscription.
Suggestions
Add at least one fully executable MCP tool call example (showing exact JSON parameters and expected response structure) rather than pseudocode numbered lists in Common Patterns.
Add explicit validation checkpoints for destructive operations: e.g., after KIT_DELETE_BROADCAST, verify deletion by calling KIT_GET_BROADCAST and confirming a 404 response.
Consolidate pitfall information — remove duplicated notes from individual workflow sections and keep them only in the Known Pitfalls section, or vice versa, to reduce token usage.
Consider splitting the detailed parameter documentation and Known Pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but contains some redundancy — pitfalls are repeated across sections (e.g., ID format notes appear in individual workflows AND in the Known Pitfalls section), and some information like 'ConvertKit (now known as Kit)' is unnecessary context. The quick reference table at the end duplicates information already covered in the workflows. | 2 / 3 |
Actionability | Tool sequences are clearly named and parameters are well-documented, but there are no executable code examples — the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual tool invocation syntax. The guidance is concrete enough to follow but not copy-paste ready since the actual MCP tool call format/syntax is never shown. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with prerequisite/required/optional labels, which is good. However, for destructive operations (Delete Broadcast, Unsubscribe), there are no explicit validation checkpoints or feedback loops — just a note to 'confirm the broadcast ID before deleting' without specifying how to verify success or handle errors. The setup section has a good verification flow though. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a useful quick reference table, but it's a long monolithic document (~180 lines) with no references to supporting files. The Known Pitfalls section and some of the detailed parameter documentation could be split into separate reference files. The single external link to Composio toolkit docs is appropriate but insufficient for the volume of content. | 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
- davepoon/buildwithclaude
- Commit
d065ead
- 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.