[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVTESQAZ0SDJSYF1YZM9WD":3,"skill-same:01M7EVTESQAZ0SDJSYF1YZM9WD":46},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EVTESQAZ0SDJSYF1YZM9WD","referee-report",null,"Adversarial line-by-line referee-grade review of OUR OWN manuscript or notes, at prover level, delivered to ai\u002F — never edits the tex. A green build resolves nothing mathematical (mechanism 5). Use when the user says \"referee my section N\", \"referee-report on the draft\", \"adversarial review of the manuscript\". NOT for handling a RECEIVED referee report (triage-referee-report \u002F manual frontier-fable response per ADR 0005) and NOT for applying fixes (revise, after human adjudication).","tdupu\u002Fagent-skills-public","tdupu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3440403?v=4","01M7EV32X9J0EFE5T4P8TKQTCQ","Taylor Dupuy","01M7EV32XZ1Z4MDBYAFRCJD3BP",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Freferee-report\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: referee-report\ndescription: Adversarial line-by-line referee-grade review of OUR OWN manuscript or notes, at prover level, delivered to ai\u002F — never edits the tex. A green build resolves nothing mathematical (mechanism 5). Use when the user says \"referee my section N\", \"referee-report on the draft\", \"adversarial review of the manuscript\". NOT for handling a RECEIVED referee report (triage-referee-report \u002F manual frontier-fable response per ADR 0005) and NOT for applying fixes (revise, after human adjudication).\n---\n\n# referee-report\n\nRead-only toward the tex. This leaf's procedure:\n\n## Produce the report\n\n1. Resolve the repo docs (`subdomains\u002Frepo-docs\u002FRESOLUTION.md`); scope\n   = the named section(s) of the canonical file (WRITERS.md's Target\n   clause defines it).\n2. Dispatch the review at prover level per\n   `subdomains\u002Flean\u002FPROVERS.md`,\n   with the mandate: line-by-line; verify every proof step; attack every\n   statement (counterexample hunting per mechanism 6); check every\n   citation's plausibility (route suspicious ones to\n   track-down-reference); hypothesis\u002Fnotation drift; the mechanism-5\n   rule verbatim — compile success is not mathematical correctness.\n3. Report to `ai\u002F\u003Cdate>-referee-\u003Cslug>\u002Freport.md`: per-finding\n   severity (BLOCKING \u002F MAJOR \u002F MINOR), location, the objection, and\n   what evidence would resolve it. Every finding also has a stable ID,\n   an explicit disposition, an exact source\u002Freport locator, a closure\n   test, and a destination: `RESOLVED-IN-REPORT`, `OPEN-TODO`,\n   `IMPORTED-OBLIGATION`, `OUT-OF-SCOPE`, or `INVALIDATED`. Claims in\n   the report follow the five-way taxonomy; contradictions found route\n   through contradiction-check (its report + refusal semantics).\n4. Run a report-completeness pass before issuing a verdict. The report\n   must contain a coverage table listing every material objection found\n   during the review. Every row must use exactly one destination and the\n   corresponding evidence fields:\n   `RESOLVED-IN-REPORT` gives the exact resolving passage and closure test;\n   `OPEN-TODO` gives a named owner, evidence requirement, next source or\n   computation, and closure test; `IMPORTED-OBLIGATION` gives the precise\n   source, hypotheses, boundary of the import, and an explicit statement\n   that the fixed criterion permits it; `OUT-OF-SCOPE` gives the criterion\n   and the reason for exclusion; `INVALIDATED` gives the evidence that\n   defeats the objection. An objection may not remain only in worker\n   scratch, an ancillary calculation, or an unlinked note.\n   ACCEPT is forbidden while any material finding is `OPEN-TODO`, or while\n   an `IMPORTED-OBLIGATION` row lacks its source, hypotheses, boundary, or\n   criterion permission. A material row may support ACCEPT only after its\n   stated closure test passes or its permitted import\u002Fout-of-scope status is\n   explicit.\n5. Apply the example admissibility gate. An example used as evidence for\n   correctness, a gap, or a verdict must either be a source-native object\n   with its exact hypotheses and source interface, or an\n   interpretation-compatible object with an explicit typed interpretation\n   map preserving the operations under discussion. Do not use the labels\n   \"toy model\", \"toy example\", or \"naive calculation\" as mathematical\n   evidence. If an illustrative construction has no such interpretation,\n   omit it from the proof argument; at most record it as a rejected\n   diagnostic in the coverage table, explicitly excluded from the verdict.\n6. Return for adjudication under the caller's authorized route.\n\n## Red flags\n\n| Thought | Reality |\n|---|---|\n| \"It compiles and reads well\" | thm1p10: green builds, 5 blocking findings. Attack the math. |\n| \"Fixing it while reviewing saves a round\" | Reviewer edits nothing. Adjudication first. |\n\n## Negative results travel with the positive ones (LX11, LX12)\n\nThis skill renders previous work into a new artifact, so the negative-result\nfloor of `..\u002F..\u002FPOLICY.md` applies. Before finishing, enumerate the inputs'\nrefutations, counterexamples, ill-posed proposals, and failed expectations, and\ncarry each into the output as a numbered statement (or a labelled question when\nunproved), naming the expectation it corrects: \"it is natural to expect $X$; in\nfact $Y$\". Report the count carried and, for anything deliberately left out,\nthe scope reason. Dropping a refuted claim together with its refutation is a\nrevise-level violation: the refutation is the surviving result.\n","# referee-report\n\nRead-only toward the tex. This leaf's procedure:\n\n## Produce the report\n\n1. Resolve the repo docs (`subdomains\u002Frepo-docs\u002FRESOLUTION.md`); scope\n   = the named section(s) of the canonical file (WRITERS.md's Target\n   clause defines it).\n2. Dispatch the review at prover level per\n   `subdomains\u002Flean\u002FPROVERS.md`,\n   with the mandate: line-by-line; verify every proof step; attack every\n   statement (counterexample hunting per mechanism 6); check every\n   citation's plausibility (route suspicious ones to\n   track-down-reference); hypothesis\u002Fnotation drift; the mechanism-5\n   rule verbatim — compile success is not mathematical correctness.\n3. Report to `ai\u002F\u003Cdate>-referee-\u003Cslug>\u002Freport.md`: per-finding\n   severity (BLOCKING \u002F MAJOR \u002F MINOR), location, the objection, and\n   what evidence would resolve it. Every finding also has a stable ID,\n   an explicit disposition, an exact source\u002Freport locator, a closure\n   test, and a destination: `RESOLVED-IN-REPORT`, `OPEN-TODO`,\n   `IMPORTED-OBLIGATION`, `OUT-OF-SCOPE`, or `INVALIDATED`. Claims in\n   the report follow the five-way taxonomy; contradictions found route\n   through contradiction-check (its report + refusal semantics).\n4. Run a report-completeness pass before issuing a verdict. The report\n   must contain a coverage table listing every material objection found\n   during the review. Every row must use exactly one destination and the\n   corresponding evidence fields:\n   `RESOLVED-IN-REPORT` gives the exact resolving passage and closure test;\n   `OPEN-TODO` gives a named owner, evidence requirement, next source or\n   computation, and closure test; `IMPORTED-OBLIGATION` gives the precise\n   source, hypotheses, boundary of the import, and an explicit statement\n   that the fixed criterion permits it; `OUT-OF-SCOPE` gives the criterion\n   and the reason for exclusion; `INVALIDATED` gives the evidence that\n   defeats the objection. An objection may not remain only in worker\n   scratch, an ancillary calculation, or an unlinked note.\n   ACCEPT is forbidden while any material finding is `OPEN-TODO`, or while\n   an `IMPORTED-OBLIGATION` row lacks its source, hypotheses, boundary, or\n   criterion permission. A material row may support ACCEPT only after its\n   stated closure test passes or its permitted import\u002Fout-of-scope status is\n   explicit.\n5. Apply the example admissibility gate. An example used as evidence for\n   correctness, a gap, or a verdict must either be a source-native object\n   with its exact hypotheses and source interface, or an\n   interpretation-compatible object with an explicit typed interpretation\n   map preserving the operations under discussion. Do not use the labels\n   \"toy model\", \"toy example\", or \"naive calculation\" as mathematical\n   evidence. If an illustrative construction has no such interpretation,\n   omit it from the proof argument; at most record it as a rejected\n   diagnostic in the coverage table, explicitly excluded from the verdict.\n6. Return for adjudication under the caller's authorized route.\n\n## Red flags\n\n| Thought | Reality |\n|---|---|\n| \"It compiles and reads well\" | thm1p10: green builds, 5 blocking findings. Attack the math. |\n| \"Fixing it while reviewing saves a round\" | Reviewer edits nothing. Adjudication first. |\n\n## Negative results travel with the positive ones (LX11, LX12)\n\nThis skill renders previous work into a new artifact, so the negative-result\nfloor of `..\u002F..\u002FPOLICY.md` applies. Before finishing, enumerate the inputs'\nrefutations, counterexamples, ill-posed proposals, and failed expectations, and\ncarry each into the output as a numbered statement (or a labelled question when\nunproved), naming the expectation it corrects: \"it is natural to expect $X$; in\nfact $Y$\". Report the count carried and, for anything deliberately left out,\nthe scope reason. Dropping a refuted claim together with its refutation is a\nrevise-level violation: the refutation is the surviving result.\n",{"name":5,"description":7},"main","8d13efb5e66306aeae6e3b948bc463e7e2db1b65","skills\u002Freferee-report","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public","https:\u002F\u002Fgithub.com\u002Ftdupu","https:\u002F\u002Ftdupu.github.io\u002Findex.html","Associate Professor, Department of Mathematics and Statistics, University of Vermont --- last updated Fall 2019","2026-11-13 09:07:19",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tdupu\u002Fagent-skills-public --skill referee-report",{"tool":38,"command":39},"bunx","bunx skills add tdupu\u002Fagent-skills-public --skill referee-report",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tdupu\u002Fagent-skills-public --skill referee-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Freferee-report\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7EW4PT586KKE7VRCAD80Z9K","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"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":19},"01M7EW4HV5V74AF3PTV8N4T0PS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7EW4DNKGP5CR1RAJP2J9PHA","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7EW4BA2QP88VBFVXDVJM7XQ","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EW47F2JG5FBESDJNP3PKMV","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7EW44N8556Y556NX9HJT4KP","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[]]