convertkit-automation
Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill convertkit-automation73
Quality
65%
Does it follow best practices?
Impact
83%
1.16xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/convertkit-automation/SKILL.mdDiscovery
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 identifies specific capabilities and a clear domain (ConvertKit automation) with good distinctiveness. However, it lacks an explicit 'Use when...' clause and could benefit from additional natural trigger terms that users might say when needing email marketing automation help.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions ConvertKit, Kit, email subscribers, newsletter management, or email marketing automation'
Include additional natural trigger terms users might say: 'email marketing', 'newsletter', 'email list', 'mailing list', 'email campaigns'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'manage subscribers, tags, broadcasts, and broadcast stats' along with the instruction to 'search tools first for current schemas'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (automate ConvertKit tasks, manage subscribers/tags/broadcasts) but lacks an explicit 'Use when...' clause. The 'when' is only implied through the domain mention. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'ConvertKit', 'Kit', 'subscribers', 'tags', 'broadcasts', but missing common variations users might say like 'email marketing', 'newsletter', 'email list', or 'email campaigns'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting ConvertKit/Kit platform via Rube MCP (Composio). The combination of platform name and specific integration method makes it highly distinctive and unlikely to conflict with other skills. | 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 comprehensive coverage of ConvertKit/Kit operations with clear workflow sequences and good documentation of pitfalls. However, it lacks executable code examples (only pseudocode patterns), contains some redundancy in pitfall documentation, and could benefit from splitting detailed reference material into separate files.
Suggestions
Add executable code examples showing actual MCP tool calls with realistic parameters and expected response structures
Consolidate repeated pitfall information (ID formats, string vs boolean) into a single 'API Quirks' section to reduce redundancy
Move the detailed pitfalls and Quick Reference table to a separate REFERENCE.md file, keeping SKILL.md focused on core workflows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - pitfalls are repeated across sections (e.g., ID formats mentioned multiple times), and some explanations like 'Deletion is permanent and cannot be undone' state the obvious. The Quick Reference table duplicates information already covered. | 2 / 3 |
Actionability | Provides tool names and parameter lists but lacks executable code examples. The 'Common Patterns' section uses pseudocode-style numbered lists rather than actual API calls or code snippets. Key parameters are documented but without concrete request/response examples. | 2 / 3 |
Workflow Clarity | Clear tool sequences with explicit prerequisites marked as [Required], [Prerequisite], or [Optional]. Each workflow has a 'When to use' trigger and logical step ordering. The Setup section includes verification steps before proceeding. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file. The document is ~180 lines with detailed pitfalls and patterns that could be split into separate reference files. The Quick Reference table at the end is helpful but the overall structure is somewhat monolithic. | 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.