ijoc-tables-figures
Use when the computational exhibits — performance profiles, runtime-vs-size plots, and results tables — are dense, misleading, or do not answer the question for an INFORMS Journal on Computing (IJOC) manuscript. Designs exhibits that make the computational claim legible; it does not generate the underlying results.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-tables-figures --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Performance Exhibits (ijoc-tables-figures) ## When to trigger - Your results are in giant tables of times and gaps that no reader can parse - You are comparing several methods across many instances and need a single legible exhibit - A referee says the figures "do not show the claimed advantage" or are hard to read - You need to show **scaling** and cannot tell whether the growth is linear, polynomial, or exponential ## The IJOC exhibit toolkit IJOC exhibits exist to make a *computational* claim legible at a glance. Choose the exhibit to the claim: - **Performance profile (Dolan–Moré).** The default for "our solver dominates across an instance set." Plot the fraction of instances solved within a factor τ of the best solver; the curve that is highest-and-leftmost wins. Far more honest and readable than a table of per-instance times. - **Runtime / memory vs. instance size.** Use **log scales** (often log–log or semilog) so polynomial vs. exponential growth is visible as a slope. Overlay the theoretical complexity from `ijoc-theory-development` so theory and experiment are seen together. - **Time-to-target / quality-over-time plots.** For anytime algorithms and heuristics, show solu
- When to trigger
- The IJOC exhibit toolkit
- Tables that earn their space
- Make the exhibit answer the claim
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Output format
What does the ijoc-tables-figures skill do?
Use when the computational exhibits — performance profiles, runtime-vs-size plots, and results tables — are dense, misleading, or do not answer the question for an INFORMS Journal on Computing (IJOC) manuscript. Designs exhibits that make the computational claim legible; it does not generate the underlying results.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-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 984 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.