SkillAgentSearch skills...

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.

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amr-methods

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of amr-methods

amr-methods scores 83/100 on our quality scale, 3189th of 4,702 Development & Engineering skills we index.

Its SKILL.md is 5.0 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so amr-methods is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

amr-methods compared with similar skills

All 4 of these similar skills score higher than amr-methods; compare them before choosing.

SkillScoreStarsUpdatedFormat
amr-methods (this skill)by brycewang-stanford831.2k2mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install amr-methods?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amr-methods. The install tabs above show the steps for each supported agent.
Which AI agents does amr-methods work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is amr-methods safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is amr-methods still maintained?
The repository was last updated about 2 months ago, so amr-methods is actively maintained.

name: amr-methods description: 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.

Theory-Construction Method (amr-methods)

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.

When to trigger

  • Constructs and propositions exist but the way they were built feels ad hoc
  • A reviewer would ask "where did this construct's domain come from?"
  • The theory needs a more disciplined construction approach than intuition
  • You need to choose among theory-building styles for your puzzle

Choosing a theory-construction approach

| 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 |

Building each component well

  • Constructs: a good construct is necessary (the theory cannot be stated without it), distinct (not a synonym), and has a clear domain and scope conditions (Suddaby's construct-clarity criteria, AMR 2010, DOI 10.5465/amr.2010.0419). Define what it excludes, not only what it includes. Construct domain is the conceptual analog of avoiding a contaminated sample — but done in argument, not data cleaning.
  • Relationships: derive, don't assert. Each link should follow from the constructs and an explicit mechanism. Specify form (causal / recursive / moderating / mediating / constitutive).
  • Mechanisms: name the engine — the why that makes theory explanatory rather than descriptive (Whetten, AMR 1989, DOI 10.5465/amr.1989.4308371). Prefer mechanisms with micro-foundations — actors doing things for stated reasons — over black-box "is associated with."
  • Boundary conditions: state the contextual, temporal, and level limits. Strong theory specifies its own scope; this is contribution, not hedging.
  • Falsifiability: design propositions to be refutable in principle (AMR's scope demands "testable knowledge-based claims"). This is the AMR analog of identification rigor at AMJ — credibility rests on tight, falsifiable logic, not on a clean estimate.

Checklist

  • [ ] A named construction approach (or explicit hybrid) is used, not intuition alone
  • [ ] Each construct is necessary, distinct, and domain-bounded
  • [ ] Each relationship is derived from constructs + mechanism, not asserted
  • [ ] Mechanisms are specified with micro-foundations where possible
  • [ ] Typologies (if used) are mutually exclusive and jointly exhaustive, derived from theory
  • [ ] Process theories specify stages, triggers, feedback, and timing
  • [ ] Boundary conditions are stated as part of the theory
  • [ ] No empirical apparatus has crept in (no samples, measures, tests)

Anti-patterns

  • Treating "method" as data collection — there is none at AMR
  • A typology whose dimensions came from convenience, not theory
  • A process "model" that is really a static box-and-arrow diagram with no engine
  • Borrowing a construct from another field without theorizing where the analogy fails
  • Cross-level claims that confuse the level of theory with the level of the mechanism
  • Asserting relationships and back-filling a mechanism afterward

Output format

【Construction approach】elaboration / analogy / typology / process / re-specification / cross-level
【Constructs built】[name + how its domain was derived]
【Mechanism basis】micro-foundations / structural / cognitive / ...
【Boundary conditions】contextual / temporal / level
【Empirical apparatus present?】must be: none
【Next step】amr-data-analysis (stress-test the logic)

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryDevelopment
Updated2mo ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions