[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BXPR8BQJZTPYGW4WASZXTZ":3,"skill-same:01M7BXPR8BQJZTPYGW4WASZXTZ":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},"01M7BXPR8BQJZTPYGW4WASZXTZ","alert",null,"Triage a Rootly alert by short ID. Pulls the alert record, its event timeline, related alerts in the same group, and any incident the alert is attached to. Use when a page comes in and you want context before opening Rootly.","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\u002Falert\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: alert\ndescription: Triage a Rootly alert by short ID. Pulls the alert record, its event timeline, related alerts in the same group, and any incident the alert is attached to. Use when a page comes in and you want context before opening Rootly.\nargument-hint: [short-id]\ndisable-model-invocation: true\nallowed-tools:\n  - mcp__rootly__*\n---\n\n# Alert Triage\n\nYou are helping the user triage a Rootly alert. Alerts are the upstream signal that may or may not become incidents. The goal is to give the user enough context in one place that they can decide: ignore, acknowledge, escalate, or open an incident.\n\n## Workflow\n\n### 1. Resolve the alert\n\n`$ARGUMENTS` should contain a short alert ID (e.g. `A-1234` or `1234`).\n\n- If `$ARGUMENTS` is empty: report \"No alert ID provided. Pass a short ID like `A-1234` or `1234`.\" and stop.\n- Otherwise call `mcp__rootly__get_alert_by_short_id` with the value as given.\n- If that fails, fall back to `mcp__rootly__getAlert` with the same value (the MCP layer often accepts both forms).\n- If both fail, surface the error and stop.\n\n### 2. Gather context\n\nOnce you have the alert UUID:\n\n1. Call `mcp__rootly__listAlertEvents` (or filter by alert) to get the event timeline.\n2. If the alert response includes an `alert_group_id` or `group` reference, call `mcp__rootly__getAlertGroup` for sibling alerts.\n3. If the alert is attached to an incident, the response usually carries an `incident_id`. Call `mcp__rootly__getIncident` for incident context.\n4. Optional: call `mcp__rootly__listAlerts` filtered to the same source\u002Fservice in the last 24h to surface \"is this alert flapping?\"\n\nStop fetching once you have enough to render the brief — do not keep walking endpoints.\n\n### 3. Present the alert brief\n\n```\n## Alert Brief: [alert title]\n\n**Short ID**: [short-id] | **Source**: [source] | **Urgency**: [urgency]\n**Started**: [time] ([duration] ago) | **State**: [state]\n**Service**: [service or \"unmapped\"]\n\n### Summary\n[Alert summary or first event message]\n\n### Event Timeline\n- [time] [event-type]: [message]\n- [time] [event-type]: [message]\n[at most 8 events, oldest first]\n\n### Group Context\n[If part of a group:]\nThis alert is one of [N] in group [group-name]. Other open alerts in the group:\n- [short-id] [title] ([state])\n\n[If flapping detected:]\n**Flapping**: this source has fired [N] alerts in the last 24h on the same service.\n\n### Incident Linkage\n[If attached to an incident:]\nAlready attached to **[INC-XXXX]** [title] ([severity], [status]).\n\n[If not attached:]\nNot attached to an incident.\n\n### Suggested Next Step\n[Pick one based on the data:]\n- \"Acknowledge — looks like a known transient pattern\"\n- \"Open an incident — first occurrence, customer-facing surface\"\n- \"Escalate — already linked to a critical incident with no responder yet\"\n- \"Ignore — historical noise from this source on this service\"\n```\n\n### 4. Read-only\n\nThis skill never mutates Rootly state. If the user wants to acknowledge, escalate, or convert the alert into an incident, point them to the Rootly UI or to `\u002Frootly:respond` for the linked incident.\n\n### 5. Error handling\n\n- **Alert not found**: report the short ID and suggest checking the format (e.g. `A-1234`).\n- **MCP tool errors**: report the specific error and continue with whatever data you have.\n- **No event timeline available**: note it and skip that section rather than failing entirely.\n","# Alert Triage\n\nYou are helping the user triage a Rootly alert. Alerts are the upstream signal that may or may not become incidents. The goal is to give the user enough context in one place that they can decide: ignore, acknowledge, escalate, or open an incident.\n\n## Workflow\n\n### 1. Resolve the alert\n\n`$ARGUMENTS` should contain a short alert ID (e.g. `A-1234` or `1234`).\n\n- If `$ARGUMENTS` is empty: report \"No alert ID provided. Pass a short ID like `A-1234` or `1234`.\" and stop.\n- Otherwise call `mcp__rootly__get_alert_by_short_id` with the value as given.\n- If that fails, fall back to `mcp__rootly__getAlert` with the same value (the MCP layer often accepts both forms).\n- If both fail, surface the error and stop.\n\n### 2. Gather context\n\nOnce you have the alert UUID:\n\n1. Call `mcp__rootly__listAlertEvents` (or filter by alert) to get the event timeline.\n2. If the alert response includes an `alert_group_id` or `group` reference, call `mcp__rootly__getAlertGroup` for sibling alerts.\n3. If the alert is attached to an incident, the response usually carries an `incident_id`. Call `mcp__rootly__getIncident` for incident context.\n4. Optional: call `mcp__rootly__listAlerts` filtered to the same source\u002Fservice in the last 24h to surface \"is this alert flapping?\"\n\nStop fetching once you have enough to render the brief — do not keep walking endpoints.\n\n### 3. Present the alert brief\n\n```\n## Alert Brief: [alert title]\n\n**Short ID**: [short-id] | **Source**: [source] | **Urgency**: [urgency]\n**Started**: [time] ([duration] ago) | **State**: [state]\n**Service**: [service or \"unmapped\"]\n\n### Summary\n[Alert summary or first event message]\n\n### Event Timeline\n- [time] [event-type]: [message]\n- [time] [event-type]: [message]\n[at most 8 events, oldest first]\n\n### Group Context\n[If part of a group:]\nThis alert is one of [N] in group [group-name]. Other open alerts in the group:\n- [short-id] [title] ([state])\n\n[If flapping detected:]\n**Flapping**: this source has fired [N] alerts in the last 24h on the same service.\n\n### Incident Linkage\n[If attached to an incident:]\nAlready attached to **[INC-XXXX]** [title] ([severity], [status]).\n\n[If not attached:]\nNot attached to an incident.\n\n### Suggested Next Step\n[Pick one based on the data:]\n- \"Acknowledge — looks like a known transient pattern\"\n- \"Open an incident — first occurrence, customer-facing surface\"\n- \"Escalate — already linked to a critical incident with no responder yet\"\n- \"Ignore — historical noise from this source on this service\"\n```\n\n### 4. Read-only\n\nThis skill never mutates Rootly state. If the user wants to acknowledge, escalate, or convert the alert into an incident, point them to the Rootly UI or to `\u002Frootly:respond` for the linked incident.\n\n### 5. Error handling\n\n- **Alert not found**: report the short ID and suggest checking the format (e.g. `A-1234`).\n- **MCP tool errors**: report the specific error and continue with whatever data you have.\n- **No event timeline available**: note it and skip that section rather than failing entirely.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":26,"disable-model-invocation":28},[25],"mcp__rootly__*",[27],"short-id",true,"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Frootly\u002Fskills\u002Falert",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 alert",{"tool":44,"command":45},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill alert",{"tool":47,"command":48},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill alert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Frootly\u002Fskills\u002Falert\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",[],[]]