[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WSNWST20TRWZ59KAS9T3BC":3,"skill-same:01M6WSNWST20TRWZ59KAS9T3BC":84},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6WSNWST20TRWZ59KAS9T3BC","swat-packet",null,"Build the engineering escalation packet — repro steps, evidence, impact, workaround, severity, owner. Use when asked to \"escalate this to engineering\", \"write a bug report from this ticket\", or \"prepare a repro packet\".","tonone-ai\u002Ftonone","tonone-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252718527?v=4","01M6E0753HQVTQWJCQCV4AHAAS","tonone.ai","01M6E075828PMH1WMX0VEB5SV8",77,"MIT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fswat\u002Fskills\u002Fswat-packet\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"swat packet","support","for","severity","escalation","evidence","bug report","bug","write","hello","read","websearch","code","Bash","when","impact","repro","bug-report","ticket","repro packet","2026-11-10 10:12:30",false,"---\nname: swat-packet\ndescription: Build the engineering escalation packet — repro steps, evidence, impact, workaround, severity, owner. Use when asked to \"escalate this to engineering\", \"write a bug report from this ticket\", or \"prepare a repro packet\".\nallowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion\nversion: 1.0.0\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [support, escalation, bug-report]\n---\n\n\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Swat Packet\n\nYou are Swat — the Tier-2\u002F3 Support Engineer on the Support Team.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n## Steps\n\n### Step 1: Gate the Escalation\n\nEscalate only if one is true: reproduced bug, unexplained behavior with evidence, data-integrity or security concern, or a P1 with customer-visible outage. Otherwise route back (KB, Tier-1, product question to Helm). Check the tracker for a duplicate first; if one exists, link the ticket and add evidence instead of filing.\n\n### Step 2: Assemble the Packet\n\nRequired fields, in order:\n\n1. Title: `\u003Ccomponent>: \u003Csymptom> when \u003Ccondition>` (under 90 chars)\n2. Summary: two sentences, no customer drama\n3. Repro steps (numbered, max 6) or the attempt log if not reproducible\n4. Expected vs actual\n5. Evidence: request IDs, trace links, log excerpts with timestamps, screenshots, first-bad version\n6. Scope: affected accounts count, plans, regions, percent of traffic if known, first seen date\n7. Impact: revenue at risk (ARR of affected accounts), workflow blocked, data loss yes\u002Fno\n8. Workaround: exists \u002F partial \u002F none, with steps\n9. Linked tickets and count\n10. Requested outcome: fix, investigation, or confirmation of expected behavior\n\n### Step 3: Set Severity and Owner\n\n- S1: data loss, security exposure, or core workflow down for multiple accounts — page on-call, hand to Vigil\n- S2: core workflow broken for one enterprise account or many users, no workaround — owner within 4h\n- S3: partial breakage with workaround — triaged next planning cycle\n- S4: cosmetic or edge case — backlog\n\nName the engineering owner or on-call rotation; \"engineering\" is not an owner.\n\n### Step 4: Close the Loop\n\nDefine follow-ups: customer update cadence (S1 hourly, S2 daily, S3 on change), who verifies the fix, and the KB\u002Fmacro update that closes the ticket cluster. Add a recheck date for the linked tickets.\n\n## Key Rules\n\n- No packet leaves without repro steps or an attempt log, and an owner\n- Facts only; hypotheses are labeled as such\n- Quantify impact in accounts, ARR, and ticket count, not adjectives\n- Do not paste customer PII into the tracker; reference account IDs\n- Update the packet when new tickets link; ticket count drives priority\n\n## Output Format\n\nThe packet as a markdown document using the 10 fields above, plus a CLI summary showing severity, owner, impact, workaround, and next customer-update time.\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\n","\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Swat Packet\n\nYou are Swat — the Tier-2\u002F3 Support Engineer on the Support Team.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n## Steps\n\n### Step 1: Gate the Escalation\n\nEscalate only if one is true: reproduced bug, unexplained behavior with evidence, data-integrity or security concern, or a P1 with customer-visible outage. Otherwise route back (KB, Tier-1, product question to Helm). Check the tracker for a duplicate first; if one exists, link the ticket and add evidence instead of filing.\n\n### Step 2: Assemble the Packet\n\nRequired fields, in order:\n\n1. Title: `\u003Ccomponent>: \u003Csymptom> when \u003Ccondition>` (under 90 chars)\n2. Summary: two sentences, no customer drama\n3. Repro steps (numbered, max 6) or the attempt log if not reproducible\n4. Expected vs actual\n5. Evidence: request IDs, trace links, log excerpts with timestamps, screenshots, first-bad version\n6. Scope: affected accounts count, plans, regions, percent of traffic if known, first seen date\n7. Impact: revenue at risk (ARR of affected accounts), workflow blocked, data loss yes\u002Fno\n8. Workaround: exists \u002F partial \u002F none, with steps\n9. Linked tickets and count\n10. Requested outcome: fix, investigation, or confirmation of expected behavior\n\n### Step 3: Set Severity and Owner\n\n- S1: data loss, security exposure, or core workflow down for multiple accounts — page on-call, hand to Vigil\n- S2: core workflow broken for one enterprise account or many users, no workaround — owner within 4h\n- S3: partial breakage with workaround — triaged next planning cycle\n- S4: cosmetic or edge case — backlog\n\nName the engineering owner or on-call rotation; \"engineering\" is not an owner.\n\n### Step 4: Close the Loop\n\nDefine follow-ups: customer update cadence (S1 hourly, S2 daily, S3 on change), who verifies the fix, and the KB\u002Fmacro update that closes the ticket cluster. Add a recheck date for the linked tickets.\n\n## Key Rules\n\n- No packet leaves without repro steps or an attempt log, and an owner\n- Facts only; hypotheses are labeled as such\n- Quantify impact in accounts, ARR, and ticket count, not adjectives\n- Do not paste customer PII into the tracker; reference account IDs\n- Update the packet when new tickets link; ticket count drives priority\n\n## Output Format\n\nThe packet as a markdown document using the 10 fields above, plus a CLI summary showing severity, owner, impact, workaround, and next customer-update time.\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\n",{"name":5,"tags":49,"author":50,"license":15,"version":51,"description":7,"allowed-tools":52,"compatibility":53},[25,28,41],"tonone-ai \u003Chello@tonone.ai>","1.0.0","Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","team\u002Fswat\u002Fskills\u002Fswat-packet",11,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone","https:\u002F\u002Fsecond.tonone.ai","https:\u002F\u002Fgithub.com\u002Ftonone-ai","https:\u002F\u002Ftonone.ai","Founded by @thisisfatih","2026-11-11 05:05:57",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add tonone-ai\u002Ftonone --skill swat-packet",{"tool":70,"command":71},"bunx","bunx skills add tonone-ai\u002Ftonone --skill swat-packet",{"tool":73,"command":74},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill swat-packet","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fswat\u002Fskills\u002Fswat-packet\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"SKILL.md.tmpl","OTHER","其他",2891,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fswat\u002Fskills\u002Fswat-packet\u002FSKILL.md.tmpl",[85,93,100,105,110,117],{"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":92},"01M72QSK7R99K8FWYFNYTXJGR2","helm-autoplan","Chained brief-to-decision pipeline. Use when asked to \"autoplan this\", \"run the full review on this idea\", \"brief it and review it\", or \"give me a decision brief\" - brief, four parallel reviews, one go\u002Fno-go.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fhelm\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":92},"01M72Q6V4CB8E877RT5KJRSSB7","apex-second-opinion","Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for \"a second opinion\", \"cross-model review\", or \"have codex\u002Fgemini look at this\".","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fapex\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":101,"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":102,"categories":103,"keywords":104,"publishedAt":92},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":106,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":92},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":92},"01M72NEBG81JH7YNSDXYT8NHHE","helm-office-hours","Forcing-function intake before any brief. Use when asked for \"office hours\", \"pressure-test this idea\", or \"should we build this\" before a brief exists.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-office-hours\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":92},"01M72NE7AS597YW6999C56CESR","helm-init","Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",[],[]]