Agent skill · Code Review & Quality

nbr-hypothesis-development

Use to develop hypotheses for 《南开管理评论》 (Nankai Business Review) so each is backed by an explicit theoretical mechanism, not intuition. Use when hypotheses read as "we expect a positive relationship", when mediation/moderation logic is asserted without a mechanism, or when the hypothesis set is not derived from the theory invoked in the introduction.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nbr-hypothesis-development --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Path: Nankai-Business-Review-Skills/skills/nbr-hypothesis-development/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 假设推演(nbr-hypothesis-development) ## 触发时机 - 假设写成"X 与 Y 正相关/负相关",没讲为什么 - 中介/调节只是"加变量",没有理论逻辑 - 假设与引言所用理论脱节,像事后补的 ## 核心原则:每条假设 = 一条机理链 合格的假设推演必须显化**机制链**: ``` X 通过 <理论机制M> 影响 Y(H1)。 因为 <理论T 主张……>,所以在 <条件> 下,X→M→Y。 ``` 机制必须来自**理论**(如社会交换、资源基础观、自我决定、制度理论、计划行为、调节焦点等),不是"常识上应该"。 ## 四类假设的机理要求 | 假设类型 | 必须讲清 | |----------|----------| | 主效应 H:X→Y | 一条可命名的理论机制,而非相关性观察 | | 中介 H:X→M→Y | M 为何被 X 激发、M 为何驱动 Y,两段都要机理 | | 调节 H:W 调节 X→Y | W 为何**改变机制强度/方向**,而非另一个主效应 | | 被调节的中介 | 指明 W 调节的是 X→M 还是 M→Y 哪一段,并说清理由 | ## 推演走查:包容性领导与员工建言 设想假设集:包容性领导→心理安全感→建言行为,员工传统性调节后半段。 - H1 机理:社会信息加工理论——领导的包容信号被员工加工为"试错无虞"的环境线索,故提升建言(不是"文献多为正相关") - H2 两段机理:包容信号→心理安全感(信息加工);心理安全感→建言(资源保存:安全感降低发声的预期资源损耗) - H3 调节机理:高传统性员工对权威线索敏感,"安全感→建言"的转化被等级观念抑制——讲清 W 改变的是后半段机制强度,且与 H2 的资源逻辑相容 - 一致性核对:三条假设同源于"包容如何转化为发声"这一个缺口,讨论部分将回扣同一条机制链 - 反例自测:若把"传统性"换成任意人口学变量后论证依然通顺,说明调节机理还没有写实,需回到理论重新推导 ## 假设规模与图模惯例(校准锚) - 本刊已刊实证文章假设多在 3–6 条量级,常用 H1、H2a/H2b 分层编号;一口气超过 8 条往往被批"机理摊薄" - 概念模型图(图 1)中每条箭头都应对应一条编号假设,反之亦然——审稿人会逐一比对 - 假设陈述句式直给:"员工传统性削弱心理安全感与建言行为之间的正向关系(H3)" - 以上为经验观察,具体以近期刊文与期刊最新投稿指南为准 ## 机理被追问时的三步修法 1. **命名**:把"我们认为"换成可引用的理论名(社会交换、调节焦点、资源保存……) 2. **链条**:写出"信号/资源/认知如何被激发→如何转化为结果"的两步式句子 3. **排他**:交代为何选此机制而非显而易见的竞争机制,必要时在分析中检验竞争中介 ## 自检清单 - [ ] 每

What's inside
Steps it walks through
  1. 触发时机
  2. 核心原则:每条假设 = 一条机理链
  3. 四类假设的机理要求
  4. 推演走查:包容性领导与员工建言
  5. 假设规模与图模惯例(校准锚)
  6. 机理被追问时的三步修法
  7. 自检清单
  8. 反模式
  9. 输出格式
More from Awesome-Journal-Skills
All skills →
About this skill
What does the nbr-hypothesis-development skill do?

Use to develop hypotheses for 《南开管理评论》 (Nankai Business Review) so each is backed by an explicit theoretical mechanism, not intuition. Use when hypotheses read as "we expect a positive relationship", when mediation/moderation logic is asserted without a mechanism, or when the hypothesis set is not derived from the theory invoked in the introduction.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nbr-hypothesis-development --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going