find-the-technique
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.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- find-the-technique
- description
- 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.
02 资源文件 1
- 参考文档agents/openai.yaml122 B
03 SKILL.md 正文
Find The Technique
Use this when the user wants to identify whether a proof technique, argument pattern, citation trail, or manuscript move surfaced by an agent already appears in the literature.
Workflow
Start by extracting the technique precisely. If the user names a manuscript, read the relevant local context first, including nearby comments, citation markers, and bibliography style. Reduce the technique to searchable mathematical phrases, theorem names, hypotheses, and proof-step orderings.
Search broadly enough to avoid confirmation bias:
- Use local bibliography and repository search first when a manuscript is provided.
- Use scholarly search tools, arXiv, MathSciNet-style metadata, publisher pages, Stacks Project, or ordinary web search as available.
- Prefer primary sources: papers, books, preprints, or authoritative reference projects. Treat secondary pages as leads, not citation evidence.
- Try several formulations of the technique, including theorem names and the sequence of proof moves.
For each plausible source, verify the actual text around the candidate result. Return only references where the cited location genuinely supports the claimed technique or a clearly stated component of it. Give pinpoint citations with the most specific stable locator available: theorem, proposition, lemma, definition, remark, section, tag, equation, and page number when the source has pages. Say explicitly when a source is only analogous rather than the same argument.
Output
Report the findings in a form the user can use directly in a manuscript:
- a short description of the matched technique;
- the strongest references first;
- full pinpoint citations for each source;
- any caveats about scope, hypotheses, or whether the source proves only part of the technique;
- BibTeX entries or bibliography text when the user asks for manuscript-ready material or when a manuscript update is likely.
Do not invent page numbers or proposition labels. If a source has no stable pagination, use stable theorem numbers, section numbers, tags, or arXiv page numbers from the PDF and label them accordingly.
After presenting the references, ask the user whether they have a manuscript they would like updated. If they confirm and identify the file, update the manuscript hygienically:
- preserve the document's citation style and bibliography mechanism;
- replace relevant TODO or author-comment markers without disturbing unrelated comments;
- add or update BibTeX and inline bibliography entries consistently;
- use pinpoint optional arguments in citations;
- run the relevant LaTeX build or citation audit when available;
- report any remaining unresolved citation markers or build warnings.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
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
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
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
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code