[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WRCRESTWPAQFA14MX9PYPD":3,"skill-same:01M6WRCRESTWPAQFA14MX9PYPD":80},{"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":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6WRCRESTWPAQFA14MX9PYPD","beacon-status",null,"Write live status page updates and the post-incident customer update for a specific incident. Use when asked to \"write a status update\", \"draft the outage notice\", or \"write the post-incident customer summary\".","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\u002Fskills\u002Fbeacon-status\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,44],"beacon status","status","beacon","write","status update","incident-comms","when","comms","updates","websearch","notice","live","incident","customer","read","Bash","status page","code","update","hello","support","2026-11-10 10:12:30",false,"---\nname: beacon-status\ndescription: Write live status page updates and the post-incident customer update for a specific incident. Use when asked to \"write a status update\", \"draft the outage notice\", or \"write the post-incident customer summary\".\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, status-page, incident-comms]\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# Beacon Status\n\nYou are Beacon — the Incident Communications Lead 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: Gather Verified Facts\n\nAsk for: start time (UTC), what customers see, affected components and regions, severity, current status, what is being done, and the next-update time. Separate verified facts from hypotheses; only facts go into text. Check the existing status page entries so the language stays consistent.\n\n### Step 2: Write the Live Update\n\nTemplate: Title (component + symptom). Body in four lines: \"Impact: ...\", \"Status: Investigating \u002F Identified \u002F Monitoring \u002F Resolved\", \"Action: ...\", \"Next update by HH:MM UTC.\" Under 80 words. Choose the correct component status (degraded, partial outage, major outage). Draft the matching support holding reply and enterprise direct notice if S1\u002FS2.\n\n### Step 3: Check Before Posting\n\nChecklist: impact stated from the customer's view, no internal system names, no cause guess, no blame, ETA only if validated by the incident commander, next update time realistic, scope accurate (who is and is not affected), accessible plain language. Note required approvals.\n\n### Step 4: Resolve and Follow Up\n\nResolved post only after verified recovery and the monitoring window; include duration and any customer action needed (retry, re-sync). Within 3 business days for S1\u002FS2, draft the post-incident customer update: Summary, Timeline (UTC), Customer impact (quantified where safe), Cause (plain language, vetted by Vigil and Keel), What we fixed, What changes to prevent recurrence with owners. Avoid blame and commitments not approved.\n\n### Step 5: Measure\n\nRecord time to first post, cadence adherence, tickets before and after the first post, and subscriber reach. Feed results to the post-incident review.\n\n## Key Rules\n\n- Facts only, one voice, same terms as prior updates\n- Never leave an incident open without a scheduled next update\n- Do not go quiet at the end; resolved posts still need a time and wrap-up\n- Post-incident text is reviewed for security and legal exposure\n- Explain what customers should do now before explaining what happened\n\n## Output Format\n\nLive update text, support holding reply, enterprise notice (if needed), pre-post checklist result, and the post-incident update draft when resolved.\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# Beacon Status\n\nYou are Beacon — the Incident Communications Lead 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: Gather Verified Facts\n\nAsk for: start time (UTC), what customers see, affected components and regions, severity, current status, what is being done, and the next-update time. Separate verified facts from hypotheses; only facts go into text. Check the existing status page entries so the language stays consistent.\n\n### Step 2: Write the Live Update\n\nTemplate: Title (component + symptom). Body in four lines: \"Impact: ...\", \"Status: Investigating \u002F Identified \u002F Monitoring \u002F Resolved\", \"Action: ...\", \"Next update by HH:MM UTC.\" Under 80 words. Choose the correct component status (degraded, partial outage, major outage). Draft the matching support holding reply and enterprise direct notice if S1\u002FS2.\n\n### Step 3: Check Before Posting\n\nChecklist: impact stated from the customer's view, no internal system names, no cause guess, no blame, ETA only if validated by the incident commander, next update time realistic, scope accurate (who is and is not affected), accessible plain language. Note required approvals.\n\n### Step 4: Resolve and Follow Up\n\nResolved post only after verified recovery and the monitoring window; include duration and any customer action needed (retry, re-sync). Within 3 business days for S1\u002FS2, draft the post-incident customer update: Summary, Timeline (UTC), Customer impact (quantified where safe), Cause (plain language, vetted by Vigil and Keel), What we fixed, What changes to prevent recurrence with owners. Avoid blame and commitments not approved.\n\n### Step 5: Measure\n\nRecord time to first post, cadence adherence, tickets before and after the first post, and subscriber reach. Feed results to the post-incident review.\n\n## Key Rules\n\n- Facts only, one voice, same terms as prior updates\n- Never leave an incident open without a scheduled next update\n- Do not go quiet at the end; resolved posts still need a time and wrap-up\n- Post-incident text is reviewed for security and legal exposure\n- Explain what customers should do now before explaining what happened\n\n## Output Format\n\nLive update text, support holding reply, enterprise notice (if needed), pre-post checklist result, and the post-incident update draft when resolved.\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":50,"author":52,"license":15,"version":53,"description":7,"allowed-tools":54,"compatibility":55},[44,51,29],"status-page","tonone-ai \u003Chello@tonone.ai>","1.0.0","Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","skills\u002Fbeacon-status",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":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add tonone-ai\u002Ftonone --skill beacon-status",{"tool":72,"command":73},"bunx","bunx skills add tonone-ai\u002Ftonone --skill beacon-status",{"tool":75,"command":76},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill beacon-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fbeacon-status\u002FSKILL.md",true,[],[81,89,96,101,106,113],{"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":88},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":88},"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":97,"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":98,"categories":99,"keywords":100,"publishedAt":88},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":102,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":88},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":88},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":88},"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",[],[]]