Agent skill · Data & Analytics

jmis-tables-figures

Use when the exhibits are the bottleneck for a Journal of Management Information Systems (JMIS) manuscript — regression/SEM tables, platform/value figures, measurement-model exhibits, or artifact-evaluation charts that must carry the argument inside the 50-page budget. Finalizes exhibits and labeling; it does not run the analysis (jmis-data-analysis) or polish prose (jmis-writing-style).

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

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

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Path: Journal-of-Management-Information-Systems-Skills/skills/jmis-tables-figures/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

# Tables and Figures (jmis-tables-figures) ## When to trigger - A reader cannot get the headline result from the tables/figures without the text - Exhibits are dense, mislabeled, or report estimates without economic magnitude - The exhibit count is pushing the manuscript over the **50-page** ceiling - Survey papers lack the measurement-model exhibits reviewers expect (reliability/validity, loadings, HTMT) ## Make each exhibit answer one question A JMIS exhibit should be readable on its own: a self-contained title, defined variables and units, the sample and period, and a note stating the estimator, clustering, and what the stars/SEs mean. The reader should be able to state the finding from the table alone. Order exhibits to track the argument — descriptive/measurement first, main result next, mechanism and robustness after. ## Report magnitudes, not just significance JMIS values managerial relevance, so a coefficient table that shows only significance underdelivers. Report **economic magnitude** — marginal effects, elasticities, dollar value, or lift — alongside (or instead of) raw coefficients, and put the number that matters in the table the reader will actually look at. Report s

What's inside
Steps it walks through
  1. When to trigger
  2. Make each exhibit answer one question
  3. Report magnitudes, not just significance
  4. Exhibits by evidence type
  5. Respect the page budget and the appendix boundary
  6. Worked example: turning a coefficient table into a JMIS exhibit (illustrative)
  7. Sequence the exhibits to track the argument
  8. Execution bridge (StatsPAI / Stata MCP)
  9. Checklist
  10. Number and reference exhibits for JMIS's house style
  11. Anti-patterns
  12. Common exhibit defects JMIS referees flag
  13. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jmis-tables-figures skill do?

Use when the exhibits are the bottleneck for a Journal of Management Information Systems (JMIS) manuscript — regression/SEM tables, platform/value figures, measurement-model exhibits, or artifact-evaluation charts that must carry the argument inside the 50-page budget. Finalizes exhibits and labeling; it does not run the analysis (jmis-data-analysis) or polish prose (jmis-writing-style).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-tables-figures --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