Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/amr-methods
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.
Passed 22 of 22 test cases with the skill, and 3 of 22 without it.
and 12 more in the full report
19 fixed3 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 19 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am drafting a theoretical manuscript for AMR where I take the concept of 'cognitive inertia' from cognitive psychology and apply it to executive team strategic pivots. I want to ensure my theoretical framing is structurally sound. Please evaluate my draft concept and organize your feedback using the structured format covering construction approach, constructs built, mechanism basis, boundary conditions, empirical apparatus present, and next step.
| Checked | Without skill | With skill |
|---|---|---|
| Uses the bracketed header tag 【Construction approach】 | Missed | Passed |
| Identifies analogy or metaphorical transfer as the construction approach | Missed | Passed |
| Specifies amr-data-analysis as the required next step | Missed | Passed |
The instructions your model reads when the skill loads.
AMR publishes NO empirical data. There are no samples, no measures, no estimation, and no results. "Method" here means the craft of building theory: how you construct constructs, derive relationships, ground mechanisms, and bound the theory. If your project needs data to make its point, it belongs at AMJ / ASQ / SMJ.
| Approach | When it fits | Core moves |
|---|---|---|
| Conceptual elaboration | Extending a known theory to a new domain | Carry over the core logic; re-specify constructs for the new setting; add boundary conditions |
| Analogical / metaphorical transfer | A construct from another field illuminates a management phenomenon | Map source → target carefully; theorize where the analogy holds and breaks |
| Typology construction | The phenomenon has distinct, theoretically meaningful types | Derive dimensions from theory (not data); ensure types are mutually exclusive and jointly exhaustive; theorize transitions (e.g., Oliver's strategic-responses typology, AMR 1991, DOI 10.5465/amr.1991.4279002) |
| Process theorizing | The phenomenon is a sequence/becoming, not a variance relationship | Specify stages, triggers, feedback loops, and timing; theorize the engine that drives movement |
| Construct re-specification | An existing construct conflates distinct phenomena | Split or merge; re-define the domain; re-derive downstream relationships |
| Cross-level theorizing | The action spans individual ↔ collective | Specify emergence (bottom-up) and top-down effects; avoid level confusion |
test cases passed, vs 3 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.