[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVFSYEACK701EBCV11DAJA":3,"skill-same:01M7EVFSYEACK701EBCV11DAJA":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},"01M7EVFSYEACK701EBCV11DAJA","gp-potential-reviewers",null,"Compile the list of people likely to review or sit on the panel for an NSF ANT (Algebra and Number Theory) proposal — the PI's suggested reviewers, recent ANT awardees from the nsf.gov award search (program element 1264, last two years), authors the proposal cites heavily, and senior people in the subfield — minus the proposal's COA conflicts, written to submission-docs\u002Fpotential-reviewers.md. Use for \"who will review this\", \"list potential reviewers\", \"who won ANT last year\", \"target the panel\", or before pd-review-as runs its perspective passes. Never guesses emails; never contacts anyone.","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\u002Fgp-potential-reviewers\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gp-potential-reviewers\ndescription: Compile the list of people likely to review or sit on the panel for an NSF ANT (Algebra and Number Theory) proposal — the PI's suggested reviewers, recent ANT awardees from the nsf.gov award search (program element 1264, last two years), authors the proposal cites heavily, and senior people in the subfield — minus the proposal's COA conflicts, written to submission-docs\u002Fpotential-reviewers.md. Use for \"who will review this\", \"list potential reviewers\", \"who won ANT last year\", \"target the panel\", or before pd-review-as runs its perspective passes. Never guesses emails; never contacts anyone.\n---\n\n# gp-potential-reviewers\n\nProduces the perspective list for `pd-review-as` and the fairness list for\nPD-POLICY P14 (every senior person whose work the draft uses is named and\ncited). It is a reading aid, not a submission document: NSF receives only\n`reviewers.txt`. No one on the list is contacted.\n\n## Inputs\n\n- The proposal folder: `proposal\u002Ftex\u002Fdescription.tex`, `references.bib`,\n  `submission-docs\u002Freviewers.txt`, `submission-docs\u002FCOA.xlsx`.\n- The program element (ANT is `1264`) and the two most recent fiscal years.\n\n## Procedure\n\n1. **PI's suggested reviewers.** Read `reviewers.txt`; every name goes in,\n   marked `suggested`.\n2. **Recent awardees.** Query the NSF award search (`nsf.gov\u002Fawardsearch`,\n   advanced search, program element code 1264, start date within the last\n   two fiscal years; the export is CSV). Record PI name, institution, title,\n   award number, year. Take all; mark `awardee`. Record the query date and\n   the count. If the site cannot be reached, say so and leave the section\n   marked `not run`; do not fill it from memory.\n3. **Heavily cited authors.** From `references.bib` and the `\\cite` counts\n   in `description.tex`, list authors cited twice or more or whose theorem\n   a project rests on; mark `cited`. Program officers for ANT (from the\n   program page, dated) go in marked `program officer`.\n4. **Senior people in the subfield.** From the cited authors' coauthor\n   networks and the PI's own knowledge of the field, the people whose\n   problems the proposal attacks or whose results it uses (for differential\n   algebra: the model theorists of differential fields, the Galois-theory\n   and D-module people, the computational differential algebra people).\n   Mark `senior`. For each, one line on which part of the draft touches\n   their work; this is the P14 fairness check input.\n5. **Exclude conflicts.** Open `COA.xlsx` read-only (`gp-coa` describes the\n   tables): remove anyone in Table 2 (collaborators) or Table 4 (advisors\n   and advisees), and anyone at the PI's institution; keep them in a\n   separate \"conflicted, excluded\" list so the exclusion is visible.\n6. **Write `submission-docs\u002Fpotential-reviewers.md`**, dated:\n\n   | name | institution | subfield | source | why they matter to this draft | likely panelist? |\n\n   `source` is one of `suggested`, `awardee \u003Cyear>`, `cited (n)`, `senior`,\n   `program officer`. \"Likely panelist\" is `yes` for suggested reviewers,\n   last year's awardees in the same subfield, and senior people the draft\n   leans on; `pd-review-as` runs one pass per `yes`. Then the conflicted\n   list, then the queries run with dates and counts.\n7. **Report** counts per source and the `yes` list. Do not edit\n   `reviewers.txt`; the PI chooses suggested reviewers.\n\n## Red flags\n\n| Thought | Reality |\n|---|---|\n| \"I remember who won ANT in 2025\" | Run the award search; record date and count. |\n| \"Their address is probably name at their institution\" | No emails; names and institutions only. |\n| \"Add them to reviewers.txt too\" | The PI chooses suggested reviewers (`gp-researchgov`). |\n| \"A collaborator would review it fairly\" | COA Table 2 and 4 names are excluded, always. |\n| \"Draft a note to ask if they would review\" | No contact of any kind. |\n","# gp-potential-reviewers\n\nProduces the perspective list for `pd-review-as` and the fairness list for\nPD-POLICY P14 (every senior person whose work the draft uses is named and\ncited). It is a reading aid, not a submission document: NSF receives only\n`reviewers.txt`. No one on the list is contacted.\n\n## Inputs\n\n- The proposal folder: `proposal\u002Ftex\u002Fdescription.tex`, `references.bib`,\n  `submission-docs\u002Freviewers.txt`, `submission-docs\u002FCOA.xlsx`.\n- The program element (ANT is `1264`) and the two most recent fiscal years.\n\n## Procedure\n\n1. **PI's suggested reviewers.** Read `reviewers.txt`; every name goes in,\n   marked `suggested`.\n2. **Recent awardees.** Query the NSF award search (`nsf.gov\u002Fawardsearch`,\n   advanced search, program element code 1264, start date within the last\n   two fiscal years; the export is CSV). Record PI name, institution, title,\n   award number, year. Take all; mark `awardee`. Record the query date and\n   the count. If the site cannot be reached, say so and leave the section\n   marked `not run`; do not fill it from memory.\n3. **Heavily cited authors.** From `references.bib` and the `\\cite` counts\n   in `description.tex`, list authors cited twice or more or whose theorem\n   a project rests on; mark `cited`. Program officers for ANT (from the\n   program page, dated) go in marked `program officer`.\n4. **Senior people in the subfield.** From the cited authors' coauthor\n   networks and the PI's own knowledge of the field, the people whose\n   problems the proposal attacks or whose results it uses (for differential\n   algebra: the model theorists of differential fields, the Galois-theory\n   and D-module people, the computational differential algebra people).\n   Mark `senior`. For each, one line on which part of the draft touches\n   their work; this is the P14 fairness check input.\n5. **Exclude conflicts.** Open `COA.xlsx` read-only (`gp-coa` describes the\n   tables): remove anyone in Table 2 (collaborators) or Table 4 (advisors\n   and advisees), and anyone at the PI's institution; keep them in a\n   separate \"conflicted, excluded\" list so the exclusion is visible.\n6. **Write `submission-docs\u002Fpotential-reviewers.md`**, dated:\n\n   | name | institution | subfield | source | why they matter to this draft | likely panelist? |\n\n   `source` is one of `suggested`, `awardee \u003Cyear>`, `cited (n)`, `senior`,\n   `program officer`. \"Likely panelist\" is `yes` for suggested reviewers,\n   last year's awardees in the same subfield, and senior people the draft\n   leans on; `pd-review-as` runs one pass per `yes`. Then the conflicted\n   list, then the queries run with dates and counts.\n7. **Report** counts per source and the `yes` list. Do not edit\n   `reviewers.txt`; the PI chooses suggested reviewers.\n\n## Red flags\n\n| Thought | Reality |\n|---|---|\n| \"I remember who won ANT in 2025\" | Run the award search; record date and count. |\n| \"Their address is probably name at their institution\" | No emails; names and institutions only. |\n| \"Add them to reviewers.txt too\" | The PI chooses suggested reviewers (`gp-researchgov`). |\n| \"A collaborator would review it fairly\" | COA Table 2 and 4 names are excluded, always. |\n| \"Draft a note to ask if they would review\" | No contact of any kind. |\n",{"name":5,"description":7},"main","8d13efb5e66306aeae6e3b948bc463e7e2db1b65","skills\u002Fgp-potential-reviewers","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 gp-potential-reviewers",{"tool":38,"command":39},"bunx","bunx skills add tdupu\u002Fagent-skills-public --skill gp-potential-reviewers",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tdupu\u002Fagent-skills-public --skill gp-potential-reviewers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Fgp-potential-reviewers\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",[],[]]