[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BVX828F8EWRZTYVH5ND7HS":3,"skill-same:01M7BVX828F8EWRZTYVH5ND7HS":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BVX828F8EWRZTYVH5ND7HS","create-dashboard",null,"Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.","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\u002Famplitude\u002Fskills\u002Fcreate-dashboard\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-dashboard\ndescription: Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.\n---\n\n# Create Dashboard\n\nCreate new team or initiative dashboards, organize scattered charts, build executive reporting, or set up review cadence dashboards.\n\n## Instructions\n\n### Step 0: Discovery (if unfamiliar with the feature)\n\nBefore building, understand what you're tracking:\n- Search for existing dashboards\u002Fcharts related to the topic\n- Search for relevant events with `Amplitude:search_amp_data_taxonomy`\n- Use `get_properties` to understand available properties for segmentation\n- Ask user for clarification on primary goals, key segments, or time horizons\n\n### Step 1: Define Dashboard Purpose\n\nClarify:\n\n- Who is the audience?\n- What decisions will it inform?\n- How frequently will it be reviewed?\n- What's the narrative structure?\n\n### Step 2: Gather or Create Charts\n\n**If existing charts found (>5 relevant):**\n- Use `Amplitude:search_amp_entities` to find relevant existing charts\n- Use `Amplitude:get_amplitude_charts` with `include: \"definition\"` to retrieve their definitions\n- Identify gaps that need new charts\n\n**If few\u002Fno charts exist (\u003C5 relevant):**\n- Switch to \"greenfield build\" mode\n- Use `Amplitude:query_amplitude_data` to create needed charts\n- Keep the returned chart edit IDs; `use_amp_dashboards` promotes them when creating the dashboard\n- Consider searching for relevant events first with entityTypes: [\"EVENT\", \"CUSTOM_EVENT\"]\n\n**Creating new charts:**\n- Prototype with `query_amplitude_data` to verify data\n- Collect the returned chart edit IDs before creating the dashboard\n\n### Step 3: Plan the Layout\n\nOrganize into logical sections:\n\n1. **Summary Row**: Key metrics at a glance (headline view)\n2. **Trend Section**: How things are changing\n3. **Breakdown Section**: Segments and dimensions\n4. **Detail Section**: Supporting analyses\n\n### Step 4: Create the Dashboard\n\nUse `Amplitude:use_amp_dashboards` with `action: \"create\"` and:\n\n- Clear, descriptive name\n- Rows with appropriate heights (375, 500, 625, or 750px)\n- Charts sized appropriately (3-12 columns)\n- Rich text headers for sections\n- Chart display configurations in chartMetas:\n  - `metric_only`: Headline KPIs (single number)\n  - `series`: Trend lines (default view)\n  - `converted`: Funnels (conversion view)\n  - `table`: Data tables\n\n### Step 5: Add Context\n\nInclude rich text blocks for:\n\n- Dashboard purpose and audience\n- How to interpret key metrics\n- Links to related resources\n- Last updated or review schedule\n\n## Layout Guidelines\n\n| Content Type     | Suggested Width | Suggested Height |\n|------------------|-----------------|------------------|\n| Headline metric  | 3-4 columns     | 375px            |\n| Trend chart      | 6-12 columns    | 500px            |\n| Comparison chart | 6 columns       | 500px            |\n| Detailed table   | 12 columns      | 625px            |\n| Section header   | 12 columns      | 375px            |\n\n## Best Practices\n\n- Put most important metrics above the fold\n- Use consistent chart sizing within rows\n- Group related metrics together\n- Add explanatory text for complex metrics\n- Ask user about focus areas if multiple valid approaches exist\n- Create charts in batches to minimize tool calls\n\n## Common Issues\n\n**Query errors (500\u002F400):**\n- Simplify: remove complex groupBy, reduce date ranges, avoid nested properties\n- Verify events\u002Fproperties exist using search first\n- Use eventsSegmentation with groupBy instead of dataTableV2 for top N lists\n\n**No data returned:**\n- Check event names are exact matches (case-sensitive)\n- Verify date range covers when events were tracked\n- Confirm user segments aren't too restrictive\n\n\n\n","# Create Dashboard\n\nCreate new team or initiative dashboards, organize scattered charts, build executive reporting, or set up review cadence dashboards.\n\n## Instructions\n\n### Step 0: Discovery (if unfamiliar with the feature)\n\nBefore building, understand what you're tracking:\n- Search for existing dashboards\u002Fcharts related to the topic\n- Search for relevant events with `Amplitude:search_amp_data_taxonomy`\n- Use `get_properties` to understand available properties for segmentation\n- Ask user for clarification on primary goals, key segments, or time horizons\n\n### Step 1: Define Dashboard Purpose\n\nClarify:\n\n- Who is the audience?\n- What decisions will it inform?\n- How frequently will it be reviewed?\n- What's the narrative structure?\n\n### Step 2: Gather or Create Charts\n\n**If existing charts found (>5 relevant):**\n- Use `Amplitude:search_amp_entities` to find relevant existing charts\n- Use `Amplitude:get_amplitude_charts` with `include: \"definition\"` to retrieve their definitions\n- Identify gaps that need new charts\n\n**If few\u002Fno charts exist (\u003C5 relevant):**\n- Switch to \"greenfield build\" mode\n- Use `Amplitude:query_amplitude_data` to create needed charts\n- Keep the returned chart edit IDs; `use_amp_dashboards` promotes them when creating the dashboard\n- Consider searching for relevant events first with entityTypes: [\"EVENT\", \"CUSTOM_EVENT\"]\n\n**Creating new charts:**\n- Prototype with `query_amplitude_data` to verify data\n- Collect the returned chart edit IDs before creating the dashboard\n\n### Step 3: Plan the Layout\n\nOrganize into logical sections:\n\n1. **Summary Row**: Key metrics at a glance (headline view)\n2. **Trend Section**: How things are changing\n3. **Breakdown Section**: Segments and dimensions\n4. **Detail Section**: Supporting analyses\n\n### Step 4: Create the Dashboard\n\nUse `Amplitude:use_amp_dashboards` with `action: \"create\"` and:\n\n- Clear, descriptive name\n- Rows with appropriate heights (375, 500, 625, or 750px)\n- Charts sized appropriately (3-12 columns)\n- Rich text headers for sections\n- Chart display configurations in chartMetas:\n  - `metric_only`: Headline KPIs (single number)\n  - `series`: Trend lines (default view)\n  - `converted`: Funnels (conversion view)\n  - `table`: Data tables\n\n### Step 5: Add Context\n\nInclude rich text blocks for:\n\n- Dashboard purpose and audience\n- How to interpret key metrics\n- Links to related resources\n- Last updated or review schedule\n\n## Layout Guidelines\n\n| Content Type     | Suggested Width | Suggested Height |\n|------------------|-----------------|------------------|\n| Headline metric  | 3-4 columns     | 375px            |\n| Trend chart      | 6-12 columns    | 500px            |\n| Comparison chart | 6 columns       | 500px            |\n| Detailed table   | 12 columns      | 625px            |\n| Section header   | 12 columns      | 375px            |\n\n## Best Practices\n\n- Put most important metrics above the fold\n- Use consistent chart sizing within rows\n- Group related metrics together\n- Add explanatory text for complex metrics\n- Ask user about focus areas if multiple valid approaches exist\n- Create charts in batches to minimize tool calls\n\n## Common Issues\n\n**Query errors (500\u002F400):**\n- Simplify: remove complex groupBy, reduce date ranges, avoid nested properties\n- Verify events\u002Fproperties exist using search first\n- Use eventsSegmentation with groupBy instead of dataTableV2 for top N lists\n\n**No data returned:**\n- Check event names are exact matches (case-sensitive)\n- Verify date range covers when events were tracked\n- Confirm user segments aren't too restrictive\n\n\n\n",{"name":5,"description":7},"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Famplitude\u002Fskills\u002Fcreate-dashboard",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill create-dashboard",{"tool":39,"command":40},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill create-dashboard",{"tool":42,"command":43},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill create-dashboard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Famplitude\u002Fskills\u002Fcreate-dashboard\u002FSKILL.md",true,[],[48,54,61,67,74,81],{"skillNo":49,"name":50,"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":51,"categories":52,"keywords":53,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":56,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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",[],[]]