Longbridge Research
helsome/folio
Institution ratings, consensus price targets, EPS/revenue forecasts, finance calendar, shareholder data, fund holders, insider trades (SEC Form 4), short interest, industry rankings, peer group…
A skill your agent uses when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or…
Install Oopsla Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-workflow --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/OOPSLA-Skills/skills/oopsla-workflow .claude/skills/oopsla-workflow && 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 "oopsla-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-workflow into .claude/skills/oopsla-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-workflow", 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/OOPSLA-Skills/skills/oopsla-workflowType 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 oopsla-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-workflow --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/OOPSLA-Skills/skills/oopsla-workflow .agents/skills/oopsla-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oopsla-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-workflow into .agents/skills/oopsla-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-workflow", 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 oopsla-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-workflow --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/OOPSLA-Skills/skills/oopsla-workflow .cursor/skills/oopsla-workflow && 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 "oopsla-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-workflow into .cursor/skills/oopsla-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-workflow", 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 OOPSLA-Skills/skills/oopsla-workflow--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 oopsla-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-workflow --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/OOPSLA-Skills/skills/oopsla-workflow .gemini/skills/oopsla-workflow && 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 "oopsla-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-workflow into .gemini/skills/oopsla-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-workflow", 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 oopsla-workflowInstalls 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 oopsla-workflow -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/OOPSLA-Skills/skills/oopsla-workflow .github/skills/oopsla-workflow && 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 "oopsla-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-workflow into .github/skills/oopsla-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-workflow", 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 oopsla-workflow -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 oopsla-workflow --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/OOPSLA-Skills/skills/oopsla-workflow .opencode/skills/oopsla-workflow && 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 "oopsla-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-workflow into .opencode/skills/oopsla-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-workflow", 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
oopsla-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 437 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or…
- Planning an OOPSLA campaign on the two-round clock — choosing October vs March entry
- SKILL.md covers Door choice: October vs March, Campaign state machine, Backward plan from a target… and Revision-path budgeting, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Budgeting for Minor
What it does
Oopsla Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or OOPSLA2 PACMPL issue, scheduling artifact evaluation, and landing the SPLASH talk, with dates re-anchored to the live cycle.
Its SKILL.md is about 1.1k 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 Business, Finance & HR, covering Budgeting and forecasting. 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
- Planning an OOPSLA campaign on the two-round clock — choosing October vs March entry
- Budgeting for Minor
- Major Revision paths
- Mapping acceptance to the OOPSLA1
Example prompts
- “/oopsla-workflow”
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
Oopsla Workflow loads about 1.1k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 437 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). 437 words, ~1,066 tokens.
Download SKILL.mdSave it as
.claude/skills/oopsla-workflow/SKILL.md (or your agent's skills folder).- name
- oopsla-workflow
- description
- Use when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or OOPSLA2 PACMPL issue, scheduling artifact evaluation, and landing the SPLASH talk, with dates re-anchored to the live cycle.
OOPSLA Workflow
OOPSLA gives a paper two doors per year into the same PACMPL volume — for 2026, October 10, 2025 (Round 1 → Issue OOPSLA1, published from April 1, 2026) and March 17, 2026 (Round 2 → Issue OOPSLA2, from October 1, 2026), with all outcomes presented at SPLASH (Oakland, October 4–9, 2026; OOPSLA talks October 5–7). Planning an OOPSLA campaign is therefore a routing problem over rounds and revision outcomes, not a countdown to a single deadline. As of 2026-07-08 the next open door is the 2027 volume's Round 1, CFP not yet posted (待核实) — re-anchor every date below to live pages.
Door choice: October vs March
| Factor | Favors the October round | Favors the March round |
|---|---|---|
| Revision insurance | Major Revision lands in March, same volume | Major Revision waits ~7 months for next volume's R1 |
| Publication timing | April issue; citable before the conference | October issue; publishes near conference time |
| Evidence maturity | Requires the evaluation done by early fall | Buys a winter of experiments |
| Team calendar | Summer build, fall write | Fall build, winter write |
| Talk lead time | Long runway to SPLASH | Acceptance close to travel booking |
Default heuristic: enter the earliest round where the evidence (not the prose) is complete — the revision insurance of the early round compounds, because the most likely non-accept outcome for solid work is a revision, and same-volume revision is the cheapest one available anywhere in the SIGPLAN family.
Campaign state machine
PLAN ──> ROUND N SUBMITTED ──> RESPONSE WINDOW ──> outcome?
Accept ─────────────► CAMERA-READY ► ARTIFACT ► ISSUE ► SPLASH TALK
Minor Revision ─────► execute list, same round ► (as Accept)
Major Revision ─────► revise against expectations ► ROUND N+1 (same
reviewers where possible)
Reject ─────────────► diagnose ► re-route (oopsla-topic-selection)
or rebuild ► a later round
Each transition has an owner and a date pulled from the live track page.Show full SKILL.md (204 more words)Show less
Backward plan from a target round (T = deadline)
- T-12 to T-8 weeks — freeze claim list; run
oopsla-experimentsrouting; start the demand matrix and reproducibility ledger. - T-8 to T-4 — full draft in the 23-page frame; related-work family
sweep (
oopsla-related-work); internal red-team read using the four SIGPLAN pillars. - T-4 to T-1 — style pass (
oopsla-writing-style); appendix layering (oopsla-supplementary); Data-Availability Statement drafted from the ledger. - Final 72 hours — the filing-day sequence in
oopsla-submission. - Post-submission — pre-write response scaffolding: the concerns you already know about, with PDF pointers ready for the four-day window.
Revision-path budgeting
Reserve capacity after submission: the two most probable outcomes for competent work — Minor and Major Revision — both demand engineering time on a fixed clock. A team that disbands to other projects the week after the deadline systematically converts Minor Revisions into missed opportunities. Rule of thumb: hold 20% of the build team's time in reserve until the outcome letter, then re-plan against the actual expectation list.
Post-acceptance rail
Camera-ready reconciliation (oopsla-camera-ready) → artifact kick-the-tires
and badges (oopsla-artifact-evaluation) → Zenodo DOI into the final
statement → issue publication → SPLASH registration, talk, and optional
poster. The talk lands months after OOPSLA1 publication — plan it as a
presentation of known work, and budget travel to the SPLASH city early.
Output format
[Cycle anchor] current volume + next open round (live URL + date checked)
[Door choice] round + rationale from the table
[State] position in the state machine
[Reserve] revision capacity held + expiry
[Next transition] owner, date, blocking items© 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 OOPSLA-Skills/skills/oopsla-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Oopsla Workflow 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 |
|---|---|---|---|---|---|---|
| Oopsla Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Longbridge Researchhelsome/folio | 269 | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Cre Asset Managementahacker-1/cre-agent-skills | 113 | 1 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Bet SizingJoelLewis/finance_skills | 205 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Dd LogsDataDog/pup | 1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Cash Flow ForecastWellApp-ai/Well | 345 | — | ~567 | Automated safety check: Pass | MIT |
Similar skills
Cre Asset Management
ahacker-1/cre-agent-skills
CRE Asset Management analysis suite — 9 specialist skills for post-acquisition multifamily operations including annual budgeting, monthly variance analysis, rent collection, renewal decisions…
Bet Sizing
JoelLewis/finance_skills
Determine how much capital to allocate to individual positions within a portfolio.
- Official
Dd Logs
DataDog/pup
Log management - search, pipelines, archives, and cost control.
Cash Flow Forecast
WellApp-ai/Well
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions.
Cash Flow Snapshot
sandbaseai/sandbase-skills
Create a 30/60/90-day cash-flow forecast from AR, AP, opening cash, payment timing, and fixed-cost data.
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 Oopsla Workflow
What does Oopsla Workflow do?
A skill your agent uses when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or…. Oopsla Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or OOPSLA2 PACMPL issue, scheduling artifact evaluation, and landing the SPLASH talk, with dates re-anchored to the live cycle.
When should I use Oopsla Workflow?
Oopsla Workflow fits situations like: planning an OOPSLA campaign on the two-round clock — choosing October vs March entry; budgeting for Minor; major Revision paths; mapping acceptance to the OOPSLA1.
How do I install Oopsla Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-workflow -a claude-code`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/oopsla-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Oopsla Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-workflow -a codex`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/oopsla-workflow in your project. Codex loads it when a task matches its description.
Can I use Oopsla Workflow 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 oopsla-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oopsla-workflow, .gemini/skills/oopsla-workflow, .github/skills/oopsla-workflow and .opencode/skills/oopsla-workflow in your project.
What does Oopsla Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Oopsla Workflow is instructions for the agent only.
Does Oopsla Workflow 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 Oopsla Workflow 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 Oopsla Workflow use?
Oopsla Workflow 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 Oopsla Workflow use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 Oopsla Workflow?
Skills that share tags, products or a category with Oopsla Workflow: Longbridge Research (helsome/folio, 269 stars), Cre Asset Management (ahacker-1/cre-agent-skills, 113 stars), Bet Sizing (JoelLewis/finance_skills, 205 stars) and Dd Logs (DataDog/pup, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oopsla Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.