Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when choosing and applying a theory-construction method for an Academy of Management Review (AMR) manuscript — building constructs, defining their domain, specifying relationships, articulating the underlying logic/mechanisms, and setting boundary conditions. This is the THEORY-CONSTRUCTION craft, NOT empirical method; AMR publishes no datasets, no measures, and no statistical tests.
Use when writing the response document for an Academy of Management Review (AMR) Revise & Resubmit — structuring point-by-point replies that show the theory was genuinely strengthened, not just defended. Drafts the response; revise the manuscript's theory FIRST (amr-theory-development / amr-data-analysis) before writing the letter.
Use when building the actual theory for an Academy of Management Review (AMR) manuscript — turning a positioned puzzle into defined constructs, explicit relationships, propositions, and boundary conditions. Constructs the theory; it does NOT stress-test the argument's logic (that is amr-data-analysis) or design any data collection (AMR has none).
Use when the theoretical puzzle is the bottleneck for an Academy of Management Review (AMR) manuscript — deciding whether an idea is theory-worthy and AMR-fit before any theorizing begins. Frames the puzzle; it does NOT build constructs (that is amr-theory-development) or design any empirical study (AMR has none).
Use when polishing the prose and structure of an Academy of Management Review (AMR) manuscript to AOM house style and an argument-driven voice. Late-stage polish; it does NOT build theory or check logic — do those first with amr-theory-development and amr-data-analysis.
Use when organizing the exposition and structure of a pure-mathematics manuscript for Annals of Mathematics — sectioning, notation, statements-before-proofs, commutative diagrams, and readability for an expert non-specialist. Figures are optional and rare; this skill is about exposition first. Does not assess the proof's correctness.
Use when controlling the length of a pure-mathematics manuscript for Annals of Mathematics — math papers may be long, but every section must be necessary; this skill cuts bloat and padding while keeping the proof complete and gap-free. Late-stage; run after the proof and architecture are fixed.
Use when laying out the proof strategy of a pure-mathematics manuscript for Annals of Mathematics — the architecture of the argument, the key lemmas and propositions, the novel technique, and where the difficulty lies. Designs and exposes the proof plan; does not check final correctness line-by-line (see anmath-referee-strategy).
Use when stating the main theorem(s) of a pure-mathematics manuscript precisely, establishing their significance, and positioning them against prior work for an Annals of Mathematics submission. Crafts statements and positioning; does not write the proof (see anmath-methods).
Use when responding to an Annals of Mathematics referee report — revising the manuscript to close gaps or strengthen results and writing a point-by-point reply. Drafts the revision and response after the text is fixed; does not invent significance the result lacks (see anmath-scope-fit).