Source profileQuality 93/100

davepoon/buildwithclaude/plugins/all-skills/skills/convertkit-automation/SKILL.md

convertkit-automation

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

Source repository stars
3,359
Declared platforms
0
Static risk flags
0
Last source update
2026-08-24
Source checked
2026-08-26

Decision brief

What it does: where it fits

Automate ConvertKit (now known as Kit) email marketing operations through Composio's Kit toolkit via Rube MCP.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/davepoon/buildwithclaude --skill "plugins/all-skills/skills/convertkit-automation"
    Safe inspection promptEditorial

    Inspect the Agent Skill "convertkit-automation" from https://github.com/davepoon/buildwithclaude/blob/ebd20fe1d82fa74e9a2f94abfeff88090f6c758c/plugins/all-skills/skills/convertkit-automation/SKILL.md at commit ebd20fe1d82fa74e9a2f94abfeff88090f6c758c. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Setup

      Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

      Verify Rube MCP is available by confirming RUBESEARCHTOOLS respondsCall RUBEMANAGECONNECTIONS with toolkit kitIf connection is not ACTIVE, follow the returned auth link to complete Kit authentication
    2. 02

      Prerequisites

      Rube MCP must be connected (RUBESEARCHTOOLS available)

      Rube MCP must be connected (RUBESEARCHTOOLS available)Active Kit connection via RUBEMANAGECONNECTIONS with toolkit kitAlways call RUBESEARCHTOOLS first to get current tool schemas
    3. 03

      Core Workflows

      When to use: User wants to browse, search, or filter email subscribers

      KITLISTSUBSCRIBERS - List subscribers with filters and pagination [Required]status: Filter by status ('active' or 'inactive')emailaddress: Exact email to search for
    4. 04

      1. List and Search Subscribers

      When to use: User wants to browse, search, or filter email subscribers

      KITLISTSUBSCRIBERS - List subscribers with filters and pagination [Required]status: Filter by status ('active' or 'inactive')emailaddress: Exact email to search for
    5. 05

      2. Manage Subscriber Tags

      When to use: User wants to tag subscribers for segmentation

      KITLISTSUBSCRIBERS - Find subscriber ID by email [Prerequisite]KITTAGSUBSCRIBER - Associate a subscriber with a tag [Required]KITLISTTAGSUBSCRIBERS - List subscribers for a specific tag [Optional]

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score93/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars3,359SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    davepoon/buildwithclaude
    Skill path
    plugins/all-skills/skills/convertkit-automation/SKILL.md
    Commit
    ebd20fe1d82fa74e9a2f94abfeff88090f6c758c
    License
    MIT
    Collected
    2026-08-26
    Default branch
    main
    View the original SKILL.md

    ConvertKit (Kit) Automation via Rube MCP

    Automate ConvertKit (now known as Kit) email marketing operations through Composio's Kit toolkit via Rube MCP.

    Toolkit docs: composio.dev/toolkits/kit

    Prerequisites

    • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
    • Active Kit connection via RUBE_MANAGE_CONNECTIONS with toolkit kit
    • Always call RUBE_SEARCH_TOOLS first to get current tool schemas

    Setup

    Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

    1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
    2. Call RUBE_MANAGE_CONNECTIONS with toolkit kit
    3. If connection is not ACTIVE, follow the returned auth link to complete Kit authentication
    4. Confirm connection status shows ACTIVE before running any workflows

    Core Workflows

    1. List and Search Subscribers

    When to use: User wants to browse, search, or filter email subscribers

    Tool sequence:

    1. KIT_LIST_SUBSCRIBERS - List subscribers with filters and pagination [Required]

    Key parameters:

    • status: Filter by status ('active' or 'inactive')
    • email_address: Exact email to search for
    • created_after/created_before: Date range filter (YYYY-MM-DD)
    • updated_after/updated_before: Date range filter (YYYY-MM-DD)
    • sort_field: Sort by 'id', 'cancelled_at', or 'updated_at'
    • sort_order: 'asc' or 'desc'
    • per_page: Results per page (min 1)
    • after/before: Cursor strings for pagination
    • include_total_count: Set to 'true' to get total subscriber count

    Pitfalls:

    • If sort_field is 'cancelled_at', the status must be set to 'cancelled'
    • Date filters use YYYY-MM-DD format (no time component)
    • email_address is an exact match; partial email search is not supported
    • Pagination uses cursor-based approach with after/before cursor strings
    • include_total_count is a string 'true', not a boolean

    2. Manage Subscriber Tags

    When to use: User wants to tag subscribers for segmentation

    Tool sequence:

    1. KIT_LIST_SUBSCRIBERS - Find subscriber ID by email [Prerequisite]
    2. KIT_TAG_SUBSCRIBER - Associate a subscriber with a tag [Required]
    3. KIT_LIST_TAG_SUBSCRIBERS - List subscribers for a specific tag [Optional]

    Key parameters for tagging:

    • tag_id: Numeric tag ID (required)
    • subscriber_id: Numeric subscriber ID (required)

    Pitfalls:

    • Both tag_id and subscriber_id must be positive integers
    • Tag IDs must reference existing tags; tags are created via the Kit web UI
    • Tagging an already-tagged subscriber is idempotent (no error)
    • Subscriber IDs are returned from LIST_SUBSCRIBERS; use email_address filter to find specific subscribers

    3. Unsubscribe a Subscriber

    When to use: User wants to unsubscribe a subscriber from all communications

    Tool sequence:

    1. KIT_LIST_SUBSCRIBERS - Find subscriber ID [Prerequisite]
    2. KIT_DELETE_SUBSCRIBER - Unsubscribe the subscriber [Required]

    Key parameters:

    • id: Subscriber ID (required, positive integer)

    Pitfalls:

    • This permanently unsubscribes the subscriber from ALL email communications
    • The subscriber's historical data is retained but they will no longer receive emails
    • Operation is idempotent; unsubscribing an already-unsubscribed subscriber succeeds without error
    • Returns empty response (HTTP 204 No Content) on success
    • Subscriber ID must exist; non-existent IDs return 404

    4. List and View Broadcasts

    When to use: User wants to browse email broadcasts or get details of a specific one

    Tool sequence:

    1. KIT_LIST_BROADCASTS - List all broadcasts with pagination [Required]
    2. KIT_GET_BROADCAST - Get detailed information for a specific broadcast [Optional]
    3. KIT_GET_BROADCAST_STATS - Get performance statistics for a broadcast [Optional]

    Key parameters for listing:

    • per_page: Results per page (1-500)
    • after/before: Cursor strings for pagination
    • include_total_count: Set to 'true' for total count

    Key parameters for details:

    • id: Broadcast ID (required, positive integer)

    Pitfalls:

    • per_page max is 500 for broadcasts
    • Broadcast stats are only available for sent broadcasts
    • Draft broadcasts will not have stats
    • Broadcast IDs are numeric integers

    5. Delete a Broadcast

    When to use: User wants to permanently remove a broadcast

    Tool sequence:

    1. KIT_LIST_BROADCASTS - Find the broadcast to delete [Prerequisite]
    2. KIT_GET_BROADCAST - Verify it is the correct broadcast [Optional]
    3. KIT_DELETE_BROADCAST - Permanently delete the broadcast [Required]

    Key parameters:

    • id: Broadcast ID (required)

    Pitfalls:

    • Deletion is permanent and cannot be undone
    • Deleting a sent broadcast removes it but does not unsend the emails
    • Confirm the broadcast ID before deleting

    Common Patterns

    Subscriber Lookup by Email

    1. Call KIT_LIST_SUBSCRIBERS with email_address='[email protected]'
    2. Extract subscriber ID from the response
    3. Use ID for tagging, unsubscribing, or other operations
    

    Pagination

    Kit uses cursor-based pagination:

    • Check response for after cursor value
    • Pass cursor as after parameter in next request
    • Continue until no more cursor is returned
    • Use include_total_count: 'true' to track progress

    Tag-Based Segmentation

    1. Create tags in Kit web UI
    2. Use KIT_TAG_SUBSCRIBER to assign tags to subscribers
    3. Use KIT_LIST_TAG_SUBSCRIBERS to view subscribers per tag
    

    Known Pitfalls

    ID Formats:

    • Subscriber IDs: positive integers (e.g., 3887204736)
    • Tag IDs: positive integers
    • Broadcast IDs: positive integers
    • All IDs are numeric, not strings

    Status Values:

    • Subscriber statuses: 'active', 'inactive', 'cancelled'
    • Some operations are restricted by status (e.g., sorting by cancelled_at requires status='cancelled')

    String vs Boolean Parameters:

    • include_total_count is a string 'true', not a boolean true
    • sort_order is a string enum: 'asc' or 'desc'

    Rate Limits:

    • Kit API has per-account rate limits
    • Implement backoff on 429 responses
    • Bulk operations should be paced appropriately

    Response Parsing:

    • Response data may be nested under data or data.data
    • Parse defensively with fallback patterns
    • Cursor values are opaque strings; use exactly as returned

    Quick Reference

    TaskTool SlugKey Params
    List subscribersKIT_LIST_SUBSCRIBERSstatus, email_address, per_page
    Tag subscriberKIT_TAG_SUBSCRIBERtag_id, subscriber_id
    List tag subscribersKIT_LIST_TAG_SUBSCRIBERStag_id
    UnsubscribeKIT_DELETE_SUBSCRIBERid
    List broadcastsKIT_LIST_BROADCASTSper_page, after
    Get broadcastKIT_GET_BROADCASTid
    Get broadcast statsKIT_GET_BROADCAST_STATSid
    Delete broadcastKIT_DELETE_BROADCASTid

    Powered by Composio

    Frequently asked questions

    What to verify before installation and use

    What does the convertkit-automation source document cover?

    Automate ConvertKit (now known as Kit) email marketing operations through Composio's Kit toolkit via Rube MCP.

    How do I install convertkit-automation?

    The source record exposes this install command: npx skills add https://github.com/davepoon/buildwithclaude --skill "plugins/all-skills/skills/convertkit-automation". Inspect the command and pinned source before running it.

    Alternatives

    Compare before choosing

    Computed 10029,095

    garrytan/gbrain

    bulk-ingestion

    End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

    Computed 10024,975

    alirezarezvani/claude-skills

    app-store-optimization

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

    Computed 10015,246

    wanshuiyin/Auto-claude-code-research-in-sleep

    citation-audit

    Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

    Computed 10014,678

    prowler-cloud/prowler

    postgresql-indexing

    PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance