Exploratory Data Analysis
spacering-net/codeg
Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.
A skill your agent uses when the theoretical argument is the bottleneck for a Journal of Management Studies (JMS) manuscript — building a mechanism and deriving hypotheses a priori, OR abstracting…
Install Jms Theory Development
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-theory-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-theory-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Journal-of-Management-Studies-Skills/skills/jms-theory-development .claude/skills/jms-theory-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jms-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-theory-development into .claude/skills/jms-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-theory-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-theory-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-theory-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-theory-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Journal-of-Management-Studies-Skills/skills/jms-theory-development .agents/skills/jms-theory-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jms-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-theory-development into .agents/skills/jms-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-theory-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-theory-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-theory-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Journal-of-Management-Studies-Skills/skills/jms-theory-development .cursor/skills/jms-theory-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jms-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-theory-development into .cursor/skills/jms-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-theory-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Journal-of-Management-Studies-Skills/skills/jms-theory-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-theory-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-theory-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Journal-of-Management-Studies-Skills/skills/jms-theory-development .gemini/skills/jms-theory-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jms-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-theory-development into .gemini/skills/jms-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-theory-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-theory-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-theory-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Journal-of-Management-Studies-Skills/skills/jms-theory-development .github/skills/jms-theory-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jms-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-theory-development into .github/skills/jms-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-theory-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-theory-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-theory-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Journal-of-Management-Studies-Skills/skills/jms-theory-development .opencode/skills/jms-theory-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jms-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-theory-development into .opencode/skills/jms-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-theory-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
jms-theory-development- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 652 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the theoretical argument is the bottleneck for a Journal of Management Studies (JMS) manuscript — building a mechanism and deriving hypotheses a priori, OR abstracting…
- Works in 5 steps: Antecedent — the predictor and why it… → Mechanism — the theoretical process… → Outcome — the dependent construct,… → …
- Abstracting grounded constructs and propositions from qualitative data
- SKILL.md covers When to trigger, The JMS theory bar, Path A — Deductive: build a… and Path B — Inductive: abstract…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jms Theory Development is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when the theoretical argument is the bottleneck for a Journal of Management Studies (JMS) manuscript — building a mechanism and deriving hypotheses a priori, OR abstracting grounded constructs and propositions from qualitative data. Constructs the theory both deductively and inductively; it does not run the analysis (jms-data-analysis) or write the final contribution paragraph (jms-contribution-framing).
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Data & Analytics, covering Data analysis. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Abstracting grounded constructs and propositions from qualitative data
- Tasks that involve Data analysis
Example prompts
- “/jms-theory-development”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Antecedent — the predictor and why it matters in this organizational context.
- Mechanism — the theoretical process linking antecedent to outcome (e.g., institutional logics, attention allocation, identity work…
- Outcome — the dependent construct, defined at a stated level of analysis (individual / team / firm / field).
- Direction & form — sign, and whether linear, curvilinear, or threshold (justify a turning point with two opposing forces, not a…
- Boundary — the moderator(s) and the theoretical reason the mechanism strengthens or reverses. "It depends" is not a theory until you say…
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Jms Theory Development loads about 1.4k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 652 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 652 words, ~1,416 tokens.
Download SKILL.mdSave it as
.claude/skills/jms-theory-development/SKILL.md (or your agent's skills folder).- name
- jms-theory-development
- description
- Use when the theoretical argument is the bottleneck for a Journal of Management Studies (JMS) manuscript — building a mechanism and deriving hypotheses a priori, OR abstracting grounded constructs and propositions from qualitative data. Constructs the theory both deductively and inductively; it does not run the analysis (jms-data-analysis) or write the final contribution paragraph (jms-contribution-framing).
Theory Development (jms-theory-development)
When to trigger
- Hypotheses read as bald predictions ("A is positively related to B") with no mechanism
- An inductive study produces rich description but no abstracted theoretical model
- The argument leans on one borrowed citation rather than a developed logic
- A reviewer says "the theory is thin," "this is description, not theory," or "what is the contribution to theory?"
- You are unsure whether to write a priori hypotheses or emergent propositions
The JMS theory bar
JMS exists to advance management and organization theory, and — unlike a US empirical journal — it treats the deductive and inductive paths as equally legitimate. The bar is the same for both: a reader must finish understanding why the relationship or pattern holds and under what conditions it changes. Pick the path the design demands; do not force a qualitative study into a hypothetico-deductive template or write post-hoc hypotheses around quantitative results.
Path A — Deductive: build a hypothesis as a mechanism chain
For each hypothesis, write the explicit chain and skip no step:
- Antecedent — the predictor and why it matters in this organizational context.
- Mechanism — the theoretical process linking antecedent to outcome (e.g., institutional logics, attention allocation, identity work, resource dependence, signalling). Name the theory and the process verb (legitimates, depletes, redirects attention, signals).
- Outcome — the dependent construct, defined at a stated level of analysis (individual / team / firm / field).
- Direction & form — sign, and whether linear, curvilinear, or threshold (justify a turning point with two opposing forces, not a significant squared term).
- Boundary — the moderator(s) and the theoretical reason the mechanism strengthens or reverses. "It depends" is not a theory until you say why.
Keep hypotheses to a defensible set (a focal effect plus a mechanism and one or two boundaries); a "kitchen sink" of ten thin predictions signals weak theory. A boxes-and-arrows model figure must map one-to-one to the hypotheses.
Path B — Inductive: abstract data into a grounded theoretical model
For qualitative theory-building, JMS does not want a priori hypotheses — it wants a credible journey from data to a model. The Gioia-style discipline is the field reference:
- First-order codes — informant-centric terms, staying close to the data.
- Second-order themes — researcher-centric theoretical concepts that aggregate the codes.
- Aggregate dimensions — the small set of constructs that organise the themes.
- Process / theoretical model — a figure showing how the dimensions relate dynamically, with propositions (not hypotheses) abstracting the relationships.
Make the data-to-theory chain visible (a data-structure figure plus representative quotes table is the convention) so a reviewer can audit how a quote became a construct. For process/longitudinal work, use temporal bracketing or a visual-mapping strategy and theorise the mechanism of change over time, not just a stage sequence.
Show full SKILL.md (203 more words)Show less
Engage rival explanations
Whichever path you take, name at least one alternative theoretical account and show why yours explains the phenomenon better or differently. JMS reviewers reward a paper that takes the strongest counter-theory seriously, not one that ignores it.
Checklist
- Path chosen (deductive mechanism / inductive grounded model) and consistent with the design
- Deductive: every hypothesis has an explicit mechanism, not just a predicted sign; level of analysis stated
- Inductive: first-order → second-order → aggregate-dimensions chain is explicit and auditable; propositions (not hypotheses)
- A theoretical/process model figure maps one-to-one to hypotheses or propositions
- Boundaries/moderators (or scope conditions) are theorised with substantive reasons
- At least one rival theoretical explanation is named and engaged
- No HARKing: deductive hypotheses fixed before analysis; inductive constructs traceable to data
Anti-patterns
- Description masquerading as theory: a vivid case with no abstracted constructs or model
- Bald predictions: "we hypothesise A relates to B" with no why
- Borrowed theory by name only: invoking dynamic capabilities or institutional logics without using its logic
- HARKing: hypothesising after results are known; every hypothesis supported, none surprising
- Stage models without mechanism: a phase sequence that never explains what drives the transitions
- Boundary without reason: a moderator with no theoretical account of why the effect differs
Output format
【Path】deductive (hypotheses) / inductive (grounded model)
【Focal theory / conversation】... (process verb: ...)
【Deductive】H1 antecedent→mechanism→outcome (level); H2 mechanism; H3+ boundary+reason
【Inductive】first-order → second-order → aggregate dimensions → propositions
【Model figure】matches hypotheses/propositions one-to-one? yes/no
【Rival explanation engaged】...
【Next step】jms-literature-positioning, then jms-methods© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Journal-of-Management-Studies-Skills/skills/jms-theory-development of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jms Theory Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jms Theory Development this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Exploratory Data Analysisspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Excel and CSV Data Analysisbytedance/deer-flow | 84k | 4 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Exploratory Data AnalysisOleafly/Oleafly | 209 | 2 repos | ~3.4k | Automated safety check: Notes | MIT | |
| Pandas ProJeffallan/claude-skills | 12k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Python Executorcortega26/chile-hub | 113 | 2 repos | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Excel and CSV Data Analysis
bytedance/deer-flow
Analyzes uploaded Excel and CSV files with SQL through DuckDB, producing schema inspections, statistical summaries and exports to CSV, JSON or Markdown.
Exploratory Data Analysis
Oleafly/Oleafly
Perform bounded, local exploratory analysis of explicitly supported scientific files.
Pandas Pro
Jeffallan/claude-skills
Handles pandas DataFrame work: cleaning, merging, groupby aggregation, pivots, time-series resampling and memory tuning, with checks on dtypes, shapes and nulls.
Python Executor
cortega26/chile-hub
Execute Python code in a safe sandboxed environment via [inference.sh](https://inference.sh).
Agentic Kaggle Workflow
FrankS-IntelLab/agentic-kaggle-skill
Takes a Kaggle competition from rules and validation design through baselines, ensembling and notebook architecture to a scored submission.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Jms Theory Development
What does Jms Theory Development do?
A skill your agent uses when the theoretical argument is the bottleneck for a Journal of Management Studies (JMS) manuscript — building a mechanism and deriving hypotheses a priori, OR abstracting…. Jms Theory Development is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when the theoretical argument is the bottleneck for a Journal of Management Studies (JMS) manuscript — building a mechanism and deriving hypotheses a priori, OR abstracting grounded constructs and propositions from qualitative data.
When should I use Jms Theory Development?
Jms Theory Development fits situations like: abstracting grounded constructs and propositions from qualitative data; tasks that involve Data analysis.
How do I install Jms Theory Development in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-theory-development -a claude-code`. Or copy the skill folder (Journal-of-Management-Studies-Skills/skills/jms-theory-development in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jms-theory-development in your project. Claude Code loads it when a task matches its description.
How do I install Jms Theory Development in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-theory-development -a codex`. Or copy the skill folder (Journal-of-Management-Studies-Skills/skills/jms-theory-development in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jms-theory-development in your project. Codex loads it when a task matches its description.
Can I use Jms Theory Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-theory-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jms-theory-development, .gemini/skills/jms-theory-development, .github/skills/jms-theory-development and .opencode/skills/jms-theory-development in your project.
What does Jms Theory Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Jms Theory Development is instructions for the agent only.
Does Jms Theory Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Jms Theory Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Jms Theory Development use?
Jms Theory Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Jms Theory Development use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Jms Theory Development?
Skills that share tags, products or a category with Jms Theory Development: Exploratory Data Analysis (spacering-net/codeg, 3.9k stars), Excel and CSV Data Analysis (bytedance/deer-flow, 84k stars), Exploratory Data Analysis (Oleafly/Oleafly, 209 stars) and Pandas Pro (Jeffallan/claude-skills, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jms Theory Development?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.