Use when the user wants help developing theoretical ideas, checking assumptions, sketching proofs, identifying gaps in an argument, connecting theory notes across files, or turning rough theory notes into structured Markdown or LaTeX-ready outlines.
Use this skill when the user is doing theory-heavy research and wants Codex to help reason through a claim rather than just summarize or rewrite notes.
The goal is to make theoretical thinking explicit, structured, and reusable. A good output should separate formal claims from intuition, identify which assumptions matter, and make uncertainty visible instead of hiding it.
Inspect only the files needed for the task:
references/meeting-note.md if recent discussions matter for the theory ideadeliverable/paper/ if the theory idea is already being drafted thereTreat the most relevant LaTeX file in deliverable/paper/ as a high-value context source because it often contains the latest project progress and the most mature statement of the argument.
Default output is one of the following, depending on the user's request:
The skill cannot choose or activate a different model or engine. Instead, make the reasoning process more rigorous by being explicit about assumptions, logical dependencies, missing steps, and failure modes.
For proof-oriented work, prefer this sequence:
A good output should let a future reader quickly answer:
Default to medium detail: detailed enough to support serious theory work, short enough to remain usable as a working note.
Use this skill when the user asks things like: