[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWP4PNBR879RTYBR7AX6G1":3,"skill-same:01M7BWP4PNBR879RTYBR7AX6G1":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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":48},"01M7BWP4PNBR879RTYBR7AX6G1","customer-360",null,"Build a comprehensive customer profile from Intercom data, including conversation history, account context, and interaction timeline. Use when the user asks to \"look up a customer\", \"customer profile\", \"customer 360\", \"tell me about this customer\", \"summarize a customer's history\", or provides a customer email or company name and wants a full picture.","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\u002Fintercom\u002Fskills\u002Fcustomer-360\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: customer-360\nlicense: MIT\ndescription: >\n  Build a comprehensive customer profile from Intercom data, including\n  conversation history, account context, and interaction timeline. Use when\n  the user asks to \"look up a customer\", \"customer profile\", \"customer 360\",\n  \"tell me about this customer\", \"summarize a customer's history\", or provides\n  a customer email or company name and wants a full picture.\ndisable-model-invocation: true\nargument-hint: \"[email or company name]\"\n---\n\n# Customer 360\n\nProduce a comprehensive customer profile by aggregating data from across the Intercom workspace.\n\n## Workflow\n\n### Step 1: Identify the Customer\n- Parse the user's input for an email, name, or company\n- Use `search_contacts` to find the contact (by email is most reliable)\n- If company name given, search contacts by email domain\n- Use `get_contact` to fetch the full profile (attributes, tags, segments, companies)\n\n### Step 2: Gather Conversation History\n- Use `search_conversations` filtered to this contact's conversations\n- Paginate to get all conversations (not just the first page)\n- For the most recent\u002Frelevant conversations, use `get_conversation` for full threads\n\n### Step 3: Build the Profile\nProduce a markdown profile with these sections:\n\n#### Contact Summary\n- Name, email, role (user\u002Flead), company\n- Location, timezone, last seen\n- Plan\u002Ftier (if available via custom attributes)\n- Tags and segments\n\n#### Conversation History\n- Total conversation count\n- Table: ID | Subject | State | Channel | Date\n- Highlight any currently open\u002Fsnoozed conversations\n\n#### Key Themes\n- Common topics across conversations\n- Recurring issues or feature requests\n- Sentiment signals (escalations, positive feedback)\n\n#### Timeline\n- Chronological list of significant interactions\n- First contact → most recent activity\n\n#### Open Items\n- Unresolved conversations\n- Pending questions or follow-ups\n\n### Step 4: Present and Offer Next Steps\n- Present the profile\n- Offer to dive deeper into any conversation\n- Offer to search for similar customers (same company, same issues)\n\n## Best Practices\n- Always cite conversation IDs so the user can find them in the Intercom inbox\n- Note data freshness — states may have changed since events occurred\n- If the contact has many conversations, summarize the most recent 10-15 and note the total count\n- Handle cases where the contact exists but has no conversations\n\n## Troubleshooting\n\n### Contact Not Found\nSymptom: No results for the provided email or name.\nSolution: Check for typos. Try searching by email domain to find related contacts. Ask the user to confirm the identifier.\n\n### Too Many Conversations\nSymptom: Contact has 50+ conversations, making full analysis impractical.\nSolution: Focus on the most recent 10-15 conversations. Summarize older ones by theme rather than individually. Note the total count.\n","# Customer 360\n\nProduce a comprehensive customer profile by aggregating data from across the Intercom workspace.\n\n## Workflow\n\n### Step 1: Identify the Customer\n- Parse the user's input for an email, name, or company\n- Use `search_contacts` to find the contact (by email is most reliable)\n- If company name given, search contacts by email domain\n- Use `get_contact` to fetch the full profile (attributes, tags, segments, companies)\n\n### Step 2: Gather Conversation History\n- Use `search_conversations` filtered to this contact's conversations\n- Paginate to get all conversations (not just the first page)\n- For the most recent\u002Frelevant conversations, use `get_conversation` for full threads\n\n### Step 3: Build the Profile\nProduce a markdown profile with these sections:\n\n#### Contact Summary\n- Name, email, role (user\u002Flead), company\n- Location, timezone, last seen\n- Plan\u002Ftier (if available via custom attributes)\n- Tags and segments\n\n#### Conversation History\n- Total conversation count\n- Table: ID | Subject | State | Channel | Date\n- Highlight any currently open\u002Fsnoozed conversations\n\n#### Key Themes\n- Common topics across conversations\n- Recurring issues or feature requests\n- Sentiment signals (escalations, positive feedback)\n\n#### Timeline\n- Chronological list of significant interactions\n- First contact → most recent activity\n\n#### Open Items\n- Unresolved conversations\n- Pending questions or follow-ups\n\n### Step 4: Present and Offer Next Steps\n- Present the profile\n- Offer to dive deeper into any conversation\n- Offer to search for similar customers (same company, same issues)\n\n## Best Practices\n- Always cite conversation IDs so the user can find them in the Intercom inbox\n- Note data freshness — states may have changed since events occurred\n- If the contact has many conversations, summarize the most recent 10-15 and note the total count\n- Handle cases where the contact exists but has no conversations\n\n## Troubleshooting\n\n### Contact Not Found\nSymptom: No results for the provided email or name.\nSolution: Check for typos. Try searching by email domain to find related contacts. Ask the user to confirm the identifier.\n\n### Too Many Conversations\nSymptom: Contact has 50+ conversations, making full analysis impractical.\nSolution: Focus on the most recent 10-15 conversations. Summarize older ones by theme rather than individually. Note the total count.\n",{"name":5,"license":15,"description":24,"argument-hint":25,"disable-model-invocation":26},"Build a comprehensive customer profile from Intercom data, including conversation history, account context, and interaction timeline. Use when the user asks to \"look up a customer\", \"customer profile\", \"customer 360\", \"tell me about this customer\", \"summarize a customer's history\", or provides a customer email or company name and wants a full picture.\n","[email or company name]",true,"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fintercom\u002Fskills\u002Fcustomer-360",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":37,"prompt":47,"zipAvailable":26},[38,41,44],{"tool":39,"command":40},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill customer-360",{"tool":42,"command":43},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill customer-360",{"tool":45,"command":46},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill customer-360","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fintercom\u002Fskills\u002Fcustomer-360\u002FSKILL.md",[],[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",[],[]]