[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72WDR8CPVYH4A5NS4HGD3ZT":3,"skill-same:01M72WDR8CPVYH4A5NS4HGD3ZT":53},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M72WDR8CPVYH4A5NS4HGD3ZT","research-report",null,"Research a technical question with probes on the local system, a web fan-out through deep-research, a grounding pass on every load-bearing claim, and a report rendered as one HTML page. Use when the user asks for a research report, a design study or an evidence-backed recommendation about their own system.","raisedadead\u002Fclaude-code-plugins","raisedadead","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1884376?v=4","01M72WC4WYRJGZ2CXMCSF7B6VG","Mrugesh Mohapatra","01M72WC4XJTNHQ0D89QPG2H0W4",3,"ISC","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fresearch-report\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: research-report\ndescription: Research a technical question with probes on the local system, a web fan-out through deep-research, a grounding pass on every load-bearing claim, and a report rendered as one HTML page. Use when the user asks for a research report, a design study or an evidence-backed recommendation about their own system.\n---\n\n# research-report — local probes, web evidence, grounded claims, one readable page\n\n`anthropic-skills:deep-research` runs the web fan-out and writes notes. This skill adds what it lacks: probes on the operator's own system, advisor checkpoints, a grounding pass, a fixed report shape and the HTML render.\n\n## Before you start\n\nThe user invoked this skill by name: go on. Claude routed it: ask once, because the run spawns several agents and a workflow, then go on after a yes.\n\nWork in `.scratchpad\u002Fresearch\u002F\u003CYYYY-MM-DD>-\u003Cslug>\u002F`, the research directory. Every file this skill names goes there.\n\n## Steps\n\n1. **Probe the real system first.** Read the installed source, the schema, the config, the data volumes. Save each probe as `probes\u002F\u003Cn>-\u003Cname>.md`: the exact command, its output, the date. Probes are read-only; confirm isolation before a probe that writes. Cap a long run at 5 minutes and record the cap. Done when every fact the question depends on locally has a probe file.\n1. **Plan with the advisor.** Call `advisor` when the session has it. Write `plan.md`: the question in one sentence, the facets (3 to 6, no overlap), the deliverable shape and the stop rule (every facet reported, at most one gap round).\n1. **Fan out to the web.** Run `anthropic-skills:deep-research` on the question and the facets from `plan.md`. It writes `research_notes\u002F\u003Ctitle>\u002F` and `reports\u002F\u003Ctitle>.md` in the directory it used for research earlier in the conversation, else in the current working directory; when it is done, move both into the research directory. Its narrative report is an input to `report.md`, not the deliverable. Without deep-research, spawn one `whetstone:whetstone-scout` per facet, all in one message, and save each claim table to `notes\u002F\u003Cfacet>.md`.\n1. **Check the stop rule with the advisor.** Deep-research's own gap round is the one round; here, only check that each facet has claims and record the uncovered ones as open items. Without deep-research, a facet with no claims gets one gap round.\n1. **Ground every load-bearing claim.** List each claim the answer or a decision rests on, with its source (URL, `path:line` or command), about 20 to 40 claims. Run the `whetstone:verify-claims` workflow with `args: { question, claims, batch: 5 }`. For each claim that is not `CONFIRMED`, correct it from the source or mark it `UNVERIFIED:` in the report. Save the result as `grounding.md`.\n1. **Write `report.md`** to the shape in [report-core.md](reference\u002Freport-core.md). Every number cites a probe, a `[key]` source or `UNVERIFIED:`.\n1. **Render.** Run the `whetstone:html-report` skill on `report.md` to `report.html`, then read every figure it lists. Re-render after the last edit to `report.md`.\n1. **Check with the advisor**, then account for every agent you spawned: arrived or pending.\n\nHand over: the HTML path, the answer in 3 to 5 bullets, and the count of `UNVERIFIED:` claims.\n\n## Honesty labels\n\n| claim                                                   | enforced by                                                            |\n| ------------------------------------------------------- | ---------------------------------------------------------------------- |\n| each claim gets a verdict                               | code — verify-claims marks a claim with no ruling `UNRULED`            |\n| a verdict is correct                                    | model-judgment — a grounder reads the source                           |\n| a broken diagram stops the render                       | code — `html-report` exit 1                                            |\n| probes are read-only                                    | model-judgment — this prompt; no hook checks a probe                   |\n| deep-research output ends in the research directory | model-judgment — deep-research writes to the conversation's research directory or the cwd; step 3 moves it |\n| the advisor runs at steps 2, 4 and 8                    | model-judgment — no hook checks the calls                              |\n","# research-report — local probes, web evidence, grounded claims, one readable page\n\n`anthropic-skills:deep-research` runs the web fan-out and writes notes. This skill adds what it lacks: probes on the operator's own system, advisor checkpoints, a grounding pass, a fixed report shape and the HTML render.\n\n## Before you start\n\nThe user invoked this skill by name: go on. Claude routed it: ask once, because the run spawns several agents and a workflow, then go on after a yes.\n\nWork in `.scratchpad\u002Fresearch\u002F\u003CYYYY-MM-DD>-\u003Cslug>\u002F`, the research directory. Every file this skill names goes there.\n\n## Steps\n\n1. **Probe the real system first.** Read the installed source, the schema, the config, the data volumes. Save each probe as `probes\u002F\u003Cn>-\u003Cname>.md`: the exact command, its output, the date. Probes are read-only; confirm isolation before a probe that writes. Cap a long run at 5 minutes and record the cap. Done when every fact the question depends on locally has a probe file.\n1. **Plan with the advisor.** Call `advisor` when the session has it. Write `plan.md`: the question in one sentence, the facets (3 to 6, no overlap), the deliverable shape and the stop rule (every facet reported, at most one gap round).\n1. **Fan out to the web.** Run `anthropic-skills:deep-research` on the question and the facets from `plan.md`. It writes `research_notes\u002F\u003Ctitle>\u002F` and `reports\u002F\u003Ctitle>.md` in the directory it used for research earlier in the conversation, else in the current working directory; when it is done, move both into the research directory. Its narrative report is an input to `report.md`, not the deliverable. Without deep-research, spawn one `whetstone:whetstone-scout` per facet, all in one message, and save each claim table to `notes\u002F\u003Cfacet>.md`.\n1. **Check the stop rule with the advisor.** Deep-research's own gap round is the one round; here, only check that each facet has claims and record the uncovered ones as open items. Without deep-research, a facet with no claims gets one gap round.\n1. **Ground every load-bearing claim.** List each claim the answer or a decision rests on, with its source (URL, `path:line` or command), about 20 to 40 claims. Run the `whetstone:verify-claims` workflow with `args: { question, claims, batch: 5 }`. For each claim that is not `CONFIRMED`, correct it from the source or mark it `UNVERIFIED:` in the report. Save the result as `grounding.md`.\n1. **Write `report.md`** to the shape in [report-core.md](reference\u002Freport-core.md). Every number cites a probe, a `[key]` source or `UNVERIFIED:`.\n1. **Render.** Run the `whetstone:html-report` skill on `report.md` to `report.html`, then read every figure it lists. Re-render after the last edit to `report.md`.\n1. **Check with the advisor**, then account for every agent you spawned: arrived or pending.\n\nHand over: the HTML path, the answer in 3 to 5 bullets, and the count of `UNVERIFIED:` claims.\n\n## Honesty labels\n\n| claim                                                   | enforced by                                                            |\n| ------------------------------------------------------- | ---------------------------------------------------------------------- |\n| each claim gets a verdict                               | code — verify-claims marks a claim with no ruling `UNRULED`            |\n| a verdict is correct                                    | model-judgment — a grounder reads the source                           |\n| a broken diagram stops the render                       | code — `html-report` exit 1                                            |\n| probes are read-only                                    | model-judgment — this prompt; no hook checks a probe                   |\n| deep-research output ends in the research directory | model-judgment — deep-research writes to the conversation's research directory or the cwd; step 3 moves it |\n| the advisor runs at steps 2, 4 and 8                    | model-judgment — no hook checks the calls                              |\n",{"name":5,"description":7},"main","f4f41887b78189cefcac4468f545fc33c434ce37","plugins\u002Fwhetstone\u002Fskills\u002Fresearch-report",0,"https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins","https:\u002F\u002Fgithub.com\u002Fraisedadead","https:\u002F\u002Fmrugesh.dev","dad • dev\u002F\u002Fops • open-source","2026-11-15 01:50:10",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add raisedadead\u002Fclaude-code-plugins --skill research-report",{"tool":39,"command":40},"bunx","bunx skills add raisedadead\u002Fclaude-code-plugins --skill research-report",{"tool":42,"command":43},"pnpm","pnpm dlx skills add raisedadead\u002Fclaude-code-plugins --skill research-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fresearch-report\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"reference\u002Freport-core.md","REFERENCE","参考文档",1627,"https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fresearch-report\u002Freference\u002Freport-core.md",[54,62,69,77,84,91],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":61},"01M7DX0HNM8XP58PP7E4XB8E98","ship","Review the dossier branch once, fold the fixup commits into the planned commits, hand the push and PR to the operator, then watch CI. Invoke when the user says \"ds:ship\", \"ship the dossier\", or when ds next exits 4.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdossier\u002Fskills\u002Fship\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":61},"01M7DX0ECWW3SANP6C6BYRVRRB","plan","Open a dossier and write its plan with the operator, then get it checked by a fresh agent before any build. Invoke when the user says \"ds:plan\", \"start a dossier\", \"plan this\", \"grill me\" in a repo with `.scratchpad\u002Fdossier\u002F`, or when work needs more than one commit.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdossier\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":76},"01M76ACYEV4AABQFW2E5F0JGDK","suite-review","Run the monthly evidence review of this repo's plugin skills. Count each skill's opportunities and uses with the census, read what happened where a skill was not used, put each skill in one bucket, act, and write the actions as predictions with a check date. Use when the operator says \"suite review\" or \"monthly review\", or when the suite-review line on LATER.md is due.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsuite-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M72WDH4ZX9QEMCPY2KSFHDDR","html-report","Render a markdown report as one self-contained HTML page for a human reader, in plain English, with the answer first, a table of contents and Mermaid diagrams drawn as images. Use when the user asks for an HTML report, or for a readable page made from a markdown document.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fhtml-report\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M72WD53HERXZ6HTZGN27SWD5","domain-modeling","Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"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":19},"01M72WD0D1DKJ4A7G59Z7SY9QG","codebase-design","Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.","https:\u002F\u002Fgithub.com\u002Fraisedadead\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fwhetstone\u002Fskills\u002Fcodebase-design\u002FSKILL.md",[],[]]