[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BXPXFSZ93TSEKF43TD78DA":3,"skill-same:01M7BXPXFSZ93TSEKF43TD78DA":51},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M7BXPXFSZ93TSEKF43TD78DA","ask",null,"Ask natural language questions about incidents, on-call, services, and reliability data. Translates your question into Rootly API calls and returns structured answers.","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\u002Frootly\u002Fskills\u002Fask\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ask\ndescription: Ask natural language questions about incidents, on-call, services, and reliability data. Translates your question into Rootly API calls and returns structured answers.\nargument-hint: [your question]\ndisable-model-invocation: true\nallowed-tools:\n  - mcp__rootly__*\n---\n\n# Natural Language Query\n\nYou are answering a natural language question about the user's incident, on-call, or reliability data using Rootly's MCP tools.\n\n## Workflow\n\n### 1. Understand the Question\n\nParse the user's question from `$ARGUMENTS`. Identify what data they need.\n\n### 2. Discover Available Tools\n\nCall `mcp__rootly__list_endpoints` to see the full list of available Rootly MCP tools and their capabilities. This helps you select the right tools for the query.\n\n### 3. Execute Queries\n\nSelect the most appropriate tools for the question. You may need multiple calls to fully answer the question. Common patterns:\n\n- \"How many incidents last week?\" -> `mcp__rootly__search_incidents` with date filters\n- \"Who's on call?\" -> `mcp__rootly__get_oncall_handoff_summary`\n- \"What happened with [service]?\" -> `mcp__rootly__search_incidents` filtered by service\n- \"Show me critical incidents\" -> `mcp__rootly__search_incidents` filtered by severity\n- \"Any patterns in auth service failures?\" -> `mcp__rootly__search_incidents` + `mcp__rootly__find_related_incidents`\n\n### 4. Present Answer\n\nProvide a clear, structured answer with supporting data. Include:\n- Direct answer to the question\n- Supporting data in tables or lists where helpful\n- Source attribution (which tools\u002Fqueries produced the data)\n\n### 5. Limitations\n\nBe explicit about what you can't answer. If the question requires data that isn't available through the Rootly MCP tools, say so clearly rather than guessing or hallucinating. For example:\n\n- \"I can't answer questions about infrastructure metrics -- Rootly tracks incidents, not system metrics.\"\n- \"This question requires data from [other system]. I can only query Rootly incident and on-call data.\"\n","# Natural Language Query\n\nYou are answering a natural language question about the user's incident, on-call, or reliability data using Rootly's MCP tools.\n\n## Workflow\n\n### 1. Understand the Question\n\nParse the user's question from `$ARGUMENTS`. Identify what data they need.\n\n### 2. Discover Available Tools\n\nCall `mcp__rootly__list_endpoints` to see the full list of available Rootly MCP tools and their capabilities. This helps you select the right tools for the query.\n\n### 3. Execute Queries\n\nSelect the most appropriate tools for the question. You may need multiple calls to fully answer the question. Common patterns:\n\n- \"How many incidents last week?\" -> `mcp__rootly__search_incidents` with date filters\n- \"Who's on call?\" -> `mcp__rootly__get_oncall_handoff_summary`\n- \"What happened with [service]?\" -> `mcp__rootly__search_incidents` filtered by service\n- \"Show me critical incidents\" -> `mcp__rootly__search_incidents` filtered by severity\n- \"Any patterns in auth service failures?\" -> `mcp__rootly__search_incidents` + `mcp__rootly__find_related_incidents`\n\n### 4. Present Answer\n\nProvide a clear, structured answer with supporting data. Include:\n- Direct answer to the question\n- Supporting data in tables or lists where helpful\n- Source attribution (which tools\u002Fqueries produced the data)\n\n### 5. Limitations\n\nBe explicit about what you can't answer. If the question requires data that isn't available through the Rootly MCP tools, say so clearly rather than guessing or hallucinating. For example:\n\n- \"I can't answer questions about infrastructure metrics -- Rootly tracks incidents, not system metrics.\"\n- \"This question requires data from [other system]. I can only query Rootly incident and on-call data.\"\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":26,"disable-model-invocation":28},[25],"mcp__rootly__*",[27],"your question",true,"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Frootly\u002Fskills\u002Fask",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":39,"prompt":49,"zipAvailable":28},[40,43,46],{"tool":41,"command":42},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill ask",{"tool":44,"command":45},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill ask",{"tool":47,"command":48},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill ask","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Frootly\u002Fskills\u002Fask\u002FSKILL.md",[],[52,58,65,71,78,85],{"skillNo":53,"name":54,"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":55,"categories":56,"keywords":57,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":60,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]