[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVC90VSSYZJRMZDFD05YQP":3,"skill-same:01M7EVC90VSSYZJRMZDFD05YQP":52},{"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},"01M7EVC90VSSYZJRMZDFD05YQP","find-the-technique",null,"Search the literature for publications using a technique surfaced by an agent, return pinpoint citations, and optionally update a manuscript after the user confirms the target file.","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\u002Ffind-the-technique\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: find-the-technique\ndescription: Search the literature for publications using a technique surfaced by an agent, return pinpoint citations, and optionally update a manuscript after the user confirms the target file.\n---\n\n# Find The Technique\n\nUse this when the user wants to identify whether a proof technique, argument\npattern, citation trail, or manuscript move surfaced by an agent already appears\nin the literature.\n\n## Workflow\n\nStart by extracting the technique precisely. If the user names a manuscript,\nread the relevant local context first, including nearby comments, citation\nmarkers, and bibliography style. Reduce the technique to searchable mathematical\nphrases, theorem names, hypotheses, and proof-step orderings.\n\nSearch broadly enough to avoid confirmation bias:\n- Use local bibliography and repository search first when a manuscript is\n  provided.\n- Use scholarly search tools, arXiv, MathSciNet-style metadata, publisher\n  pages, Stacks Project, or ordinary web search as available.\n- Prefer primary sources: papers, books, preprints, or authoritative reference\n  projects. Treat secondary pages as leads, not citation evidence.\n- Try several formulations of the technique, including theorem names and the\n  sequence of proof moves.\n\nFor each plausible source, verify the actual text around the candidate result.\nReturn only references where the cited location genuinely supports the claimed\ntechnique or a clearly stated component of it. Give pinpoint citations with the\nmost specific stable locator available: theorem, proposition, lemma,\ndefinition, remark, section, tag, equation, and page number when the source has\npages. Say explicitly when a source is only analogous rather than the same\nargument.\n\n## Output\n\nReport the findings in a form the user can use directly in a manuscript:\n- a short description of the matched technique;\n- the strongest references first;\n- full pinpoint citations for each source;\n- any caveats about scope, hypotheses, or whether the source proves only part of\n  the technique;\n- BibTeX entries or bibliography text when the user asks for manuscript-ready\n  material or when a manuscript update is likely.\n\nDo not invent page numbers or proposition labels. If a source has no stable\npagination, use stable theorem numbers, section numbers, tags, or arXiv page\nnumbers from the PDF and label them accordingly.\n\nAfter presenting the references, ask the user whether they have a manuscript\nthey would like updated. If they confirm and identify the file, update the\nmanuscript hygienically:\n- preserve the document's citation style and bibliography mechanism;\n- replace relevant TODO or author-comment markers without disturbing unrelated\n  comments;\n- add or update BibTeX and inline bibliography entries consistently;\n- use pinpoint optional arguments in citations;\n- run the relevant LaTeX build or citation audit when available;\n- report any remaining unresolved citation markers or build warnings.\n","# Find The Technique\n\nUse this when the user wants to identify whether a proof technique, argument\npattern, citation trail, or manuscript move surfaced by an agent already appears\nin the literature.\n\n## Workflow\n\nStart by extracting the technique precisely. If the user names a manuscript,\nread the relevant local context first, including nearby comments, citation\nmarkers, and bibliography style. Reduce the technique to searchable mathematical\nphrases, theorem names, hypotheses, and proof-step orderings.\n\nSearch broadly enough to avoid confirmation bias:\n- Use local bibliography and repository search first when a manuscript is\n  provided.\n- Use scholarly search tools, arXiv, MathSciNet-style metadata, publisher\n  pages, Stacks Project, or ordinary web search as available.\n- Prefer primary sources: papers, books, preprints, or authoritative reference\n  projects. Treat secondary pages as leads, not citation evidence.\n- Try several formulations of the technique, including theorem names and the\n  sequence of proof moves.\n\nFor each plausible source, verify the actual text around the candidate result.\nReturn only references where the cited location genuinely supports the claimed\ntechnique or a clearly stated component of it. Give pinpoint citations with the\nmost specific stable locator available: theorem, proposition, lemma,\ndefinition, remark, section, tag, equation, and page number when the source has\npages. Say explicitly when a source is only analogous rather than the same\nargument.\n\n## Output\n\nReport the findings in a form the user can use directly in a manuscript:\n- a short description of the matched technique;\n- the strongest references first;\n- full pinpoint citations for each source;\n- any caveats about scope, hypotheses, or whether the source proves only part of\n  the technique;\n- BibTeX entries or bibliography text when the user asks for manuscript-ready\n  material or when a manuscript update is likely.\n\nDo not invent page numbers or proposition labels. If a source has no stable\npagination, use stable theorem numbers, section numbers, tags, or arXiv page\nnumbers from the PDF and label them accordingly.\n\nAfter presenting the references, ask the user whether they have a manuscript\nthey would like updated. If they confirm and identify the file, update the\nmanuscript hygienically:\n- preserve the document's citation style and bibliography mechanism;\n- replace relevant TODO or author-comment markers without disturbing unrelated\n  comments;\n- add or update BibTeX and inline bibliography entries consistently;\n- use pinpoint optional arguments in citations;\n- run the relevant LaTeX build or citation audit when available;\n- report any remaining unresolved citation markers or build warnings.\n",{"name":5,"description":7},"main","8d13efb5e66306aeae6e3b948bc463e7e2db1b65","skills\u002Ffind-the-technique","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 find-the-technique",{"tool":38,"command":39},"bunx","bunx skills add tdupu\u002Fagent-skills-public --skill find-the-technique",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tdupu\u002Fagent-skills-public --skill find-the-technique","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Ffind-the-technique\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",122,"https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Ffind-the-technique\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":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":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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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",[],[]]