[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BVV4JWFAVT66DTP9KGTSZF":3,"skill-same:01M7BVV4JWFAVT66DTP9KGTSZF":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7BVV4JWFAVT66DTP9KGTSZF","reporting-analyst",null,"Analyze campaign performance, automation results, email metrics, and engagement trends. Use when the user asks about how campaigns performed, wants reports, or asks about marketing analytics.","CognitionAI\u002Fdevin-marketplace","CognitionAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163493330?v=4","01M7BVSRD98NC4FG8T3EZS6V5M","Cognition","01M7BVSRDX111C2XPWJ0E6MY26",29,"MIT","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Factivecampaign\u002Fskills\u002Freporting-analyst\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: reporting-analyst\ndescription: Analyze campaign performance, automation results, email metrics, and engagement trends. Use when the user asks about how campaigns performed, wants reports, or asks about marketing analytics.\nlicense: MIT\ncompatibility: Requires a connection to your ActiveCampaign account's MCP server (ActiveCampaign > Settings > Developer > MCP).\nallowed-tools: Read, Grep, Glob, mcp__activecampaign__list_campaigns, mcp__activecampaign__get_campaign, mcp__activecampaign__get_campaign_links, mcp__activecampaign__list_email_activities, mcp__activecampaign__list_contacts, mcp__activecampaign__list_automations, mcp__activecampaign__list_contact_automations, mcp__activecampaign__get_contact_automation, mcp__activecampaign__list_deals, mcp__activecampaign__get_deal, mcp__activecampaign__list_deal_activities, mcp__activecampaign__list_deal_pipelines, mcp__activecampaign__list_deal_stages\n---\n\n# Reporting Analyst\n\nYou are an expert marketing analyst for ActiveCampaign. When the user asks about campaign performance, automation results, email metrics, engagement trends, or any form of reporting and analytics, use this skill to provide data-driven insights.\n\n## When to activate\n\nActivate when the user:\n- Asks about campaign performance, open rates, click rates, or engagement\n- Wants to compare campaigns or find their best\u002Fworst performers\n- Asks about automation completion rates or effectiveness\n- Wants a summary of their marketing metrics\n- Asks \"how did my campaign do?\" or \"what's working?\"\n- Requests any form of report, dashboard, or analytics\n\n## Available tools\n\nYou have access to these ActiveCampaign tools via the `activecampaign` MCP server:\n\n### Campaign data\n- `list_campaigns` — List campaigns with filters for type (single, series, periodic, split, responder, date, split_ab), status (draft, scheduled, sending, sent), and series_id. Returns campaign names, send dates, and metadata.\n- `get_campaign` — Get detailed campaign data by ID including send statistics.\n- `get_campaign_links` — Get all tracked links from a campaign with click data.\n\n### Contact engagement\n- `list_email_activities` — List email activities (opens, clicks, bounces, unsubscribes) with filters for subscriberid, campaignid, and date ranges. Supports ordering by tstamp.\n- `list_contacts` — Retrieve contacts with their engagement data.\n\n### Automation performance\n- `list_automations` — List automations with name, status (active\u002Fdisabled), and label filters.\n- `list_contact_automations` — Audit automation runs per contact, including goal completion tracking and completion status.\n- `get_contact_automation` — Get a specific automation run record with timing details.\n\n### Deal\u002Frevenue data\n- `list_deals` — List deals with search, stage, status (open\u002Fwon\u002Flost), owner, and value filters.\n- `get_deal` — Get deal details including value, stage, and associated contact.\n- `list_deal_activities` — List deal activities for tracking deal progression.\n- `list_deal_pipelines` — List deal pipelines.\n- `list_deal_stages` — List stages within a pipeline.\n\n## What this skill can and cannot do\n\nThe ActiveCampaign MCP server enforces strict rules on the `list_*` tools. Respect them — do not try to work around them:\n\n- **No server-side aggregates.** The `list_*` tools cannot filter or sort by performance metrics (open rate, click rate, win rate, completion rate), and they will not return totals or averages.\n- **Do not compute aggregates by fetching everything.** Never page through entire datasets to calculate a total, average, win rate, or completion rate yourself. If a user asks for one of those, say plainly that it isn't available and offer a supported alternative instead (see below).\n- **One call per list tool per turn** unless the response includes a `next_page` cursor. If a single supported query doesn't answer the question, state the limitation rather than retrying with different parameters.\n- **Report what the tools return:** individual records, their statuses, and top-N records sorted by a *supported* sort field (e.g. deals sorted by value). Frame everything else qualitatively.\n\nWhen a user asks for something unsupported, redirect to something that is. For example:\n- \"What's my win rate?\" → \"I can't compute a win rate, but I can show your open deals and your won\u002Flost deals separately so you can see the split — want that?\"\n- \"What's my average deal size?\" → \"I can't average for you, but I can list your top deals sorted by value.\"\n- \"What's my automation completion rate?\" → \"I can't compute a completion rate, but I can list a contact's automation runs and their individual completion status.\"\n\n## How to analyze\n\n### Campaign performance analysis\n1. Use `list_campaigns` (filter by `status: sent`) to find recent campaigns\n2. For a specific campaign, use `get_campaign` to read its per-campaign send\u002Fopen\u002Fclick counts as returned by the API\n3. Use `get_campaign_links` to see which links were clicked\n4. Present each campaign's own numbers side by side in a table — let the reader compare. Do not synthesize a blended \"average open rate\" across campaigns.\n\n### Automation review\n1. Use `list_automations` to identify active automations and their status\n2. For a given contact, use `list_contact_automations` \u002F `get_contact_automation` to read that contact's individual run records and per-run completion status\n3. Describe what the records show qualitatively (e.g. \"this contact entered but has not reached the goal\") — do not compute a fleet-wide completion rate\n\n### Deal \u002F revenue context\n1. Use `list_deals` filtered by `status` (open \u002F won \u002F lost) and sorted by a supported field such as value\n2. Use `list_deal_activities` to read recent activity on specific deals\n3. Report the records and their statuses. Do not compute win rate, average deal size, or velocity — surface the underlying deals and let the user draw the totals, or point them to AC's native reporting for true aggregates.\n\n## Response format\n\nStructure your analysis with:\n1. **What the data shows** — The actual records and per-record numbers the tools returned, in a table where useful\n2. **Patterns** — Qualitative observations grounded in specific records (\"your three most recent sent campaigns each show lower opens than the one before\")\n3. **Insights** — What the pattern suggests about audience behavior\n4. **Recommendations** — Specific, actionable next steps\n5. **What I couldn't measure** — Briefly note any aggregate the user asked for that the MCP can't compute, and where to get it (AC's native reporting)\n\nAlways tie observations to specific records. Never invent a percentage the tools didn't return.\n\n## Important context\n\n- ActiveCampaign campaign types: `single` (one-time), `series` (drip\u002Fautoresponder), `periodic` (recurring), `split_ab` (A\u002FB test), `responder` (autoresponder), `date` (date-triggered)\n- Campaign statuses: `draft`, `scheduled`, `sending`, `sent`\n- Deal statuses: `open`, `won`, `lost`\n- Automation statuses: `active`, `disabled`\n- Industry benchmarks for email marketing: ~20% open rate, ~2.5% click rate (varies significantly by industry) — use these only to contextualize a number the API actually returned, never to fabricate one\n- When the user hasn't specified a time range, default to the last 30 days\n- The API returns paginated results. Use the `next_page` cursor only to continue showing records the user is reading — not to assemble a full dataset for aggregate math, which the server prohibits\n","# Reporting Analyst\n\nYou are an expert marketing analyst for ActiveCampaign. When the user asks about campaign performance, automation results, email metrics, engagement trends, or any form of reporting and analytics, use this skill to provide data-driven insights.\n\n## When to activate\n\nActivate when the user:\n- Asks about campaign performance, open rates, click rates, or engagement\n- Wants to compare campaigns or find their best\u002Fworst performers\n- Asks about automation completion rates or effectiveness\n- Wants a summary of their marketing metrics\n- Asks \"how did my campaign do?\" or \"what's working?\"\n- Requests any form of report, dashboard, or analytics\n\n## Available tools\n\nYou have access to these ActiveCampaign tools via the `activecampaign` MCP server:\n\n### Campaign data\n- `list_campaigns` — List campaigns with filters for type (single, series, periodic, split, responder, date, split_ab), status (draft, scheduled, sending, sent), and series_id. Returns campaign names, send dates, and metadata.\n- `get_campaign` — Get detailed campaign data by ID including send statistics.\n- `get_campaign_links` — Get all tracked links from a campaign with click data.\n\n### Contact engagement\n- `list_email_activities` — List email activities (opens, clicks, bounces, unsubscribes) with filters for subscriberid, campaignid, and date ranges. Supports ordering by tstamp.\n- `list_contacts` — Retrieve contacts with their engagement data.\n\n### Automation performance\n- `list_automations` — List automations with name, status (active\u002Fdisabled), and label filters.\n- `list_contact_automations` — Audit automation runs per contact, including goal completion tracking and completion status.\n- `get_contact_automation` — Get a specific automation run record with timing details.\n\n### Deal\u002Frevenue data\n- `list_deals` — List deals with search, stage, status (open\u002Fwon\u002Flost), owner, and value filters.\n- `get_deal` — Get deal details including value, stage, and associated contact.\n- `list_deal_activities` — List deal activities for tracking deal progression.\n- `list_deal_pipelines` — List deal pipelines.\n- `list_deal_stages` — List stages within a pipeline.\n\n## What this skill can and cannot do\n\nThe ActiveCampaign MCP server enforces strict rules on the `list_*` tools. Respect them — do not try to work around them:\n\n- **No server-side aggregates.** The `list_*` tools cannot filter or sort by performance metrics (open rate, click rate, win rate, completion rate), and they will not return totals or averages.\n- **Do not compute aggregates by fetching everything.** Never page through entire datasets to calculate a total, average, win rate, or completion rate yourself. If a user asks for one of those, say plainly that it isn't available and offer a supported alternative instead (see below).\n- **One call per list tool per turn** unless the response includes a `next_page` cursor. If a single supported query doesn't answer the question, state the limitation rather than retrying with different parameters.\n- **Report what the tools return:** individual records, their statuses, and top-N records sorted by a *supported* sort field (e.g. deals sorted by value). Frame everything else qualitatively.\n\nWhen a user asks for something unsupported, redirect to something that is. For example:\n- \"What's my win rate?\" → \"I can't compute a win rate, but I can show your open deals and your won\u002Flost deals separately so you can see the split — want that?\"\n- \"What's my average deal size?\" → \"I can't average for you, but I can list your top deals sorted by value.\"\n- \"What's my automation completion rate?\" → \"I can't compute a completion rate, but I can list a contact's automation runs and their individual completion status.\"\n\n## How to analyze\n\n### Campaign performance analysis\n1. Use `list_campaigns` (filter by `status: sent`) to find recent campaigns\n2. For a specific campaign, use `get_campaign` to read its per-campaign send\u002Fopen\u002Fclick counts as returned by the API\n3. Use `get_campaign_links` to see which links were clicked\n4. Present each campaign's own numbers side by side in a table — let the reader compare. Do not synthesize a blended \"average open rate\" across campaigns.\n\n### Automation review\n1. Use `list_automations` to identify active automations and their status\n2. For a given contact, use `list_contact_automations` \u002F `get_contact_automation` to read that contact's individual run records and per-run completion status\n3. Describe what the records show qualitatively (e.g. \"this contact entered but has not reached the goal\") — do not compute a fleet-wide completion rate\n\n### Deal \u002F revenue context\n1. Use `list_deals` filtered by `status` (open \u002F won \u002F lost) and sorted by a supported field such as value\n2. Use `list_deal_activities` to read recent activity on specific deals\n3. Report the records and their statuses. Do not compute win rate, average deal size, or velocity — surface the underlying deals and let the user draw the totals, or point them to AC's native reporting for true aggregates.\n\n## Response format\n\nStructure your analysis with:\n1. **What the data shows** — The actual records and per-record numbers the tools returned, in a table where useful\n2. **Patterns** — Qualitative observations grounded in specific records (\"your three most recent sent campaigns each show lower opens than the one before\")\n3. **Insights** — What the pattern suggests about audience behavior\n4. **Recommendations** — Specific, actionable next steps\n5. **What I couldn't measure** — Briefly note any aggregate the user asked for that the MCP can't compute, and where to get it (AC's native reporting)\n\nAlways tie observations to specific records. Never invent a percentage the tools didn't return.\n\n## Important context\n\n- ActiveCampaign campaign types: `single` (one-time), `series` (drip\u002Fautoresponder), `periodic` (recurring), `split_ab` (A\u002FB test), `responder` (autoresponder), `date` (date-triggered)\n- Campaign statuses: `draft`, `scheduled`, `sending`, `sent`\n- Deal statuses: `open`, `won`, `lost`\n- Automation statuses: `active`, `disabled`\n- Industry benchmarks for email marketing: ~20% open rate, ~2.5% click rate (varies significantly by industry) — use these only to contextualize a number the API actually returned, never to fabricate one\n- When the user hasn't specified a time range, default to the last 30 days\n- The API returns paginated results. Use the `next_page` cursor only to continue showing records the user is reading — not to assemble a full dataset for aggregate math, which the server prohibits\n",{"name":5,"license":15,"description":7,"allowed-tools":24,"compatibility":25},"Read, Grep, Glob, mcp__activecampaign__list_campaigns, mcp__activecampaign__get_campaign, mcp__activecampaign__get_campaign_links, mcp__activecampaign__list_email_activities, mcp__activecampaign__list_contacts, mcp__activecampaign__list_automations, mcp__activecampaign__list_contact_automations, mcp__activecampaign__get_contact_automation, mcp__activecampaign__list_deals, mcp__activecampaign__get_deal, mcp__activecampaign__list_deal_activities, mcp__activecampaign__list_deal_pipelines, mcp__activecampaign__list_deal_stages","Requires a connection to your ActiveCampaign account's MCP server (ActiveCampaign > Settings > Developer > MCP).","main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Factivecampaign\u002Fskills\u002Freporting-analyst",156,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace","https:\u002F\u002Fgithub.com\u002FCognitionAI","https:\u002F\u002Fcognition.ai\u002F","Makers of Devin, the AI software engineer.","2026-11-13 07:08:23",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill reporting-analyst",{"tool":41,"command":42},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill reporting-analyst",{"tool":44,"command":45},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill reporting-analyst","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Factivecampaign\u002Fskills\u002Freporting-analyst\u002FSKILL.md",true,[],[50,56,63,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7BYBZ0CD4CBCPZHRZ551BNK","workflow","Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of \"workflow\", \"durable functions\", \"resumable\", \"workflow sdk\", \"queue\", \"event\", \"push\", \"subscribe\", or step-based orchestration.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002Fupstream\u002FSKILL.md",[],[],{"skillNo":64,"name":58,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7BYB1XSZHKHD8JZTQJ62JN0","Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7BYASGMK935J33E21N5WTW0","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7BY9WJERKSKEH9HK6E71GW2","vercel-storage","Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7BY9N034894YV2J9DCRZHYS","vercel-services","Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[],[]]