CtrlK
BlogDocsLog inGet started
Tessl Logo

convertkit-automation

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/convertkit-automation/SKILL.md

The canonical home for this skill is convertkit-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body provides concrete, well-parameterized tool guidance with clear workflow sequencing and good internal navigation. Its weaknesses are duplicated pitfall content, a generic trailing section, and the absence of explicit validation checkpoints for destructive operations.

Suggestions

Add explicit validation checkpoints to destructive workflows (e.g., for delete-broadcast: verify the broadcast via KIT_GET_BROADCAST, confirm the ID/title with the user, then KIT_DELETE_BROADCAST, then re-list to confirm removal) to lift workflow_clarity above 3.

Remove the duplicated "Known Pitfalls" section or replace the per-workflow pitfalls with cross-references to it, and delete the generic final "When to Use" line, to tighten conciseness.

Add at least one complete copy-paste-ready example invocation per workflow (e.g., a full KIT_LIST_SUBSCRIBERS call with sample argument values and expected response shape) to move actionability toward 5.

DimensionReasoningScore

Conciseness

Mostly efficient parameter and pitfall lists, but pitfalls are duplicated across per-workflow sections and a consolidated "Known Pitfalls" block, and the trailing "When to Use" line ("applicable to execute the workflow or actions described in the overview") is generic filler that could be trimmed.

3 / 5

Actionability

Concrete tool names (KIT_LIST_SUBSCRIBERS, KIT_TAG_SUBSCRIBER, etc.), typed parameters with formats (e.g., "include_total_count is a string 'true', not a boolean"), and a Quick Reference table give mostly executable guidance, though no full copy-paste invocation block with argument values is provided.

4 / 5

Workflow Clarity

Each workflow is clearly sequenced with numbered tool calls and "When to use" headers, but destructive operations (KIT_DELETE_SUBSCRIBER, KIT_DELETE_BROADCAST, unsubscribe) lack explicit validate-then-confirm checkpoints, and the verify step in delete-broadcast is marked Optional rather than a required checkpoint, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist, so all content is inline in a single ~190-line file, but it is well-organized into clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) with easy navigation; the main organization gap is the duplicated pitfalls content.

4 / 5

Total

14

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 names a specific product and several concrete capability areas with good trigger terms and strong distinctiveness. Its main weakness is the missing explicit "Use when..." trigger guidance, which caps completeness at 3.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases (e.g., "Use when the user wants to manage ConvertKit/Kit subscribers, tags, or broadcasts, or asks about subscriber/broadcast statistics").

Enumerate a few more concrete actions (e.g., list/search subscribers, unsubscribe, delete broadcasts) to lift specificity from 4 toward 5.

Include common synonyms a user might say ("email list", "newsletter subscribers") to round out trigger term coverage.

DimensionReasoningScore

Specificity

"manage subscribers, tags, broadcasts, and broadcast stats" lists several concrete action areas within the ConvertKit domain, though each is stated at the domain level rather than fully enumerated, leaving minor gaps.

4 / 5

Completeness

The "what" is clear ("Automate ConvertKit (Kit) tasks... manage subscribers, tags, broadcasts, and broadcast stats") but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say (ConvertKit, Kit, subscribers, tags, broadcasts) are present, and the Kit/ConvertKit rename synonym is included, but a few common variants are missing.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to ConvertKit/Kit operations via Rube MCP (Composio), a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.