[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718CS4VJNEW3SRN5S3MG35W":3,"skill-same:01M718CS4VJNEW3SRN5S3MG35W":71},{"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":28,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M718CS4VJNEW3SRN5S3MG35W","postmortem-report",null,"How the SRE team writes a postmortem PDF. Use this whenever asked for a postmortem, an incident report, a write-up to share, or a PDF of what happened.","anthropics\u002Fcwc-workshops","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M718C167JSRVRHKR28E40JYN",2309,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fship-your-first-managed-agent\u002Fskills\u002Fpostmortem-report\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"postmortem report","postmortem","report","sre","what happened","PDF","how","for","incident","write","up","incident report","use","team","share","2026-11-10 10:12:30",false,"---\nname: postmortem-report\ndescription: How the SRE team writes a postmortem PDF. Use this whenever asked for a postmortem, an incident report, a write-up to share, or a PDF of what happened.\n---\n\n# Postmortem report\n\nYou build the PDF yourself, in your sandbox. There is no template. Design it so a director understands the event in one minute and an engineer can check every claim.\n\n## What it must contain\n\n1. A headline and a summary of three or four sentences.\n2. A table of pages: page id, service, root cause. Pages that share a root cause are one incident; mark the others as symptoms.\n3. At least one chart drawn from real data. Compute it in your script from `\u002Fmnt\u002Fsession\u002Fuploads\u002Fapp.log` (for example p99 latency or error rate per minute for each paged service) and mark the deploys on it.\n4. For each root cause: a timeline in UTC, the evidence that proves it, what was ruled out, and the fix.\n5. Action items, each with an owner team and a priority.\n\n## How to build it\n\n- Python with matplotlib and pandas is installed. `matplotlib.backends.backend_pdf.PdfPages` writes multi-page PDFs. pandoc and LaTeX are there too. Use whichever you can do fastest.\n- The investigators' findings are in `\u002Fworkspace\u002Ffindings\u002F*.json`. Start from those instead of investigating again.\n- Save the result to `\u002Fmnt\u002Fsession\u002Foutputs\u002Fpostmortem.pdf`. Only files under `\u002Fmnt\u002Fsession\u002Foutputs\u002F` reach the user.\n- Be quick: write one script, run it, and fix it only if it errors. Two to four pages. Do not render the PDF to images to inspect it.\n- Keep everything inside the page margins: wrap the title and any long table cell instead of letting it run off the edge.\n- Follow any postmortem conventions you find in team memory.\n\nWhen it is built, tell the user the file name in one or two sentences. Do not paste the report into the chat.\n","# Postmortem report\n\nYou build the PDF yourself, in your sandbox. There is no template. Design it so a director understands the event in one minute and an engineer can check every claim.\n\n## What it must contain\n\n1. A headline and a summary of three or four sentences.\n2. A table of pages: page id, service, root cause. Pages that share a root cause are one incident; mark the others as symptoms.\n3. At least one chart drawn from real data. Compute it in your script from `\u002Fmnt\u002Fsession\u002Fuploads\u002Fapp.log` (for example p99 latency or error rate per minute for each paged service) and mark the deploys on it.\n4. For each root cause: a timeline in UTC, the evidence that proves it, what was ruled out, and the fix.\n5. Action items, each with an owner team and a priority.\n\n## How to build it\n\n- Python with matplotlib and pandas is installed. `matplotlib.backends.backend_pdf.PdfPages` writes multi-page PDFs. pandoc and LaTeX are there too. Use whichever you can do fastest.\n- The investigators' findings are in `\u002Fworkspace\u002Ffindings\u002F*.json`. Start from those instead of investigating again.\n- Save the result to `\u002Fmnt\u002Fsession\u002Foutputs\u002Fpostmortem.pdf`. Only files under `\u002Fmnt\u002Fsession\u002Foutputs\u002F` reach the user.\n- Be quick: write one script, run it, and fix it only if it errors. Two to four pages. Do not render the PDF to images to inspect it.\n- Keep everything inside the page margins: wrap the title and any long table cell instead of letting it run off the edge.\n- Follow any postmortem conventions you find in team memory.\n\nWhen it is built, tell the user the file name in one or two sentences. Do not paste the report into the chat.\n",{"name":5,"description":7},"main","2c65d16c6de16f8f24117d539a712ea706b5dee7","ship-your-first-managed-agent\u002Fskills\u002Fpostmortem-report",713,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-05 02:53:17",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add anthropics\u002Fcwc-workshops --skill postmortem-report",{"tool":63,"command":64},"bunx","bunx skills add anthropics\u002Fcwc-workshops --skill postmortem-report",{"tool":66,"command":67},"pnpm","pnpm dlx skills add anthropics\u002Fcwc-workshops --skill postmortem-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fship-your-first-managed-agent\u002Fskills\u002Fpostmortem-report\u002FSKILL.md",true,[],[72,92,103,131,150,168],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":44},"01M718CPE2QT7TQMYAG56R19JW","incident-triage-runbook","The SRE team's runbook for triaging production latency and error-rate incidents. Use this whenever investigating an incident, a latency spike, elevated error rates, or when asked \"what caused X\" about a production service.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fship-your-first-managed-agent\u002Fskills\u002Fincident-triage-runbook\u002FSKILL.md",[],[79,80,81,37,82,83,42,84,41,85,86,87,88,89,36,90,32,91],"runbook","triage","incident triage","incident triage runbook","about","when","service","spike","Production","rate","incidents","latency","error",{"skillNo":93,"name":94,"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":95,"categories":96,"keywords":97,"publishedAt":44},"01M718CMK6R22RHEBDN1VW1YB5","eval-audit-and-sweep","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Frightmodel\u002F.claude\u002Fskills\u002Feval-audit-and-sweep\u002FSKILL.md",[],[98,99,100,101,102],"sweep","audit","eval audit and sweep","eval audit","eval",{"skillNo":104,"name":105,"nameZh":6,"description":106,"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":112,"publishedAt":44},"01M718CJ7RTEG518SSEJMH3H8H","edgartools-sec-data","How to pull SEC EDGAR data with the edgartools Python package — company lookup, filings, XBRL financial statements, and filing sections like Item 1A risk factors. Use whenever a task involves SEC filings, 10-K\u002F10-Q data, or company financials.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fresearch-desk\u002Fskills\u002Fedgartools\u002FSKILL.md",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[113,114,115,116,117,118,35,119,120,41,121,122,123,124,125,126,127,128,129,130],"data","edgartools sec data","edgartools","lookup","company lookup","financial statements","with","task","package","company","how to","pull","financials","sec edgar","risk","filings","filing","python",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":44},"01M718CF9KPNBKPWFJN27XDN6A","workshop","Workshop coach for the Research Desk (SEC agents) workshop. Use when the user types \u002Fworkshop, asks for a workshop act or module (\"act 2\", \"next act\", \"where am I\"), wants a TODO(workshop-N) implemented or explained, or asks for help following WORKSHOP.md.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fresearch-desk\u002F.claude\u002Fskills\u002Fworkshop\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[133,41,141,36,142,143,84,144,145,146,147,148,149],"types","coach","module","todo","research","next","help","act","user",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":44},"01M718CD3EBG31CBH0KSPVX0YR","weekly-report","Structure and data sources for the weekly inventory report. Load this when the task is \"weekly report\", \"Monday report\", or \"summarize inventory status\".","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fagent-decomposition\u002F.claude\u002Fskills\u002Fweekly-report\u002FSKILL.md",[156],{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[31,158,159,160,161,36,162,163,113,164,84,120,165,166,167],"Weekly Report","weekly","monday","data sources","inventory","status","load","summarize","sources","structure",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":44},"01M718CBJPS1CFB1RBBY4HAA5F","supplier-selection","How to rank and pick a supplier for a SKU. Load this whenever a task involves choosing a supplier, comparing quotes, or creating a purchase order.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fcwc-workshops\u002Fblob\u002Fmain\u002Fagent-decomposition\u002F.claude\u002Fskills\u002Fsupplier-selection\u002FSKILL.md",[],[175,176,177,178,123,164,179,120,180,35,36],"supplier selection","selection","purchase","pick","quotes","purchase order"]