convertkit-automation

Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.

1.16x

Quality

58%

Does it follow best practices?

Impact

83%

1.16x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/convertkit-automation/SKILL.md

Quality

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 reasonably specific about what it does and names the exact platform and integration method, making it highly distinctive. However, it lacks an explicit 'Use when...' clause and misses common user-facing trigger terms like 'email marketing', 'newsletter', or 'email list' 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, managing email subscribers, or newsletter broadcasts.'

Include natural trigger terms users would say such as 'email marketing', 'newsletter', 'mailing list', 'email campaigns', and 'email subscribers' to improve discoverability.

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 behavioral instruction to search tools first.	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 by the domain context, which caps this at 2 per the rubric guidelines.	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', 'email campaigns', or 'mailing list' that users would naturally say.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific platform names 'ConvertKit' and 'Kit' combined with 'Rube MCP (Composio)'. This is 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 a solid structural overview of Kit/ConvertKit automation via Rube MCP with clear tool sequences and useful pitfall documentation. Its main weaknesses are redundancy across sections (pitfalls repeated in multiple places), lack of truly executable examples (pseudocode patterns instead of actual tool call syntax), and missing explicit validation checkpoints for destructive operations like broadcast deletion and subscriber unsubscription.

Suggestions

Add concrete, executable tool invocation examples showing exact parameter formats and response parsing (e.g., actual RUBE_SEARCH_TOOLS call syntax and how to extract a subscriber ID from the JSON response).

For destructive operations (Delete Broadcast, Unsubscribe), add mandatory verification steps with explicit feedback loops: e.g., 'Call KIT_GET_BROADCAST to confirm name/subject matches → display to user for confirmation → only then call KIT_DELETE_BROADCAST'.

Consolidate pitfalls into the single 'Known Pitfalls' section and remove duplicated pitfall notes from individual workflow sections to reduce token usage.

Replace the pseudocode Common Patterns with actual tool call examples showing parameters and expected response structure.

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)' and the Composio branding are unnecessary filler. The quick reference table at the end duplicates information already covered in the workflows.	2 / 3
Actionability	The skill provides clear tool names, parameter lists, and sequences, but lacks executable code examples—the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual tool invocation syntax. Key details like exact response structures and how to extract subscriber IDs from responses are described vaguely ('Extract subscriber ID from the response') rather than concretely.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with prerequisite/required/optional labels, which is good. However, the destructive operations (Delete Broadcast, 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. The delete broadcast workflow has an optional verify step but doesn't mandate it before a permanent destructive action.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and a useful quick reference table, but it's a monolithic document (~180 lines) with no references to external files for detailed content. The Known Pitfalls, Common Patterns, and per-workflow pitfalls could be split into separate reference files to keep the main skill leaner. However, with no bundle files provided, there's nothing to split into.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 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: 74c7031

Reviewed: 3 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.