Convert
remotion-dev/remotion
Start the local @remotion/convert app and open it in the Codex browser.
A skill your agent uses when converting an OSDI acceptance into the published paper — the June final-paper deadline, expansion to 14 pages plus appendices, the two-page Artifact Appendix…
MITAuto-check passed
Install Osdi Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-camera-ready --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/OSDI-Skills/skills/osdi-camera-ready .claude/skills/osdi-camera-ready && 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 "osdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-camera-ready into .claude/skills/osdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-camera-ready", 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/OSDI-Skills/skills/osdi-camera-readyType 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 osdi-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-camera-ready --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/OSDI-Skills/skills/osdi-camera-ready .agents/skills/osdi-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "osdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-camera-ready into .agents/skills/osdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-camera-ready", 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 osdi-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-camera-ready --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/OSDI-Skills/skills/osdi-camera-ready .cursor/skills/osdi-camera-ready && 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 "osdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-camera-ready into .cursor/skills/osdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-camera-ready", 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 OSDI-Skills/skills/osdi-camera-ready--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 osdi-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-camera-ready --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/OSDI-Skills/skills/osdi-camera-ready .gemini/skills/osdi-camera-ready && 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 "osdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-camera-ready into .gemini/skills/osdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-camera-ready", 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 osdi-camera-readyInstalls 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 osdi-camera-ready -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/OSDI-Skills/skills/osdi-camera-ready .github/skills/osdi-camera-ready && 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 "osdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-camera-ready into .github/skills/osdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-camera-ready", 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 osdi-camera-ready -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 osdi-camera-ready --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/OSDI-Skills/skills/osdi-camera-ready .opencode/skills/osdi-camera-ready && 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 "osdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-camera-ready into .opencode/skills/osdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-camera-ready", 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
osdi-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 771 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting an OSDI acceptance into the published paper — the June final-paper deadline, expansion to 14 pages plus appendices, the two-page Artifact Appendix…
- Works in 3 steps: Shepherd-mandated changes (conditional… → Expansion into the final budget: up to… → De-anonymization: real authors and…
- Converting an OSDI acceptance into the published paper — the June final-paper deadline
- SKILL.md covers The June 9 deliverable, De-anonymization checklist, What USENIX publication means… and Presentation and the event, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Osdi Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an OSDI acceptance into the published paper — the June final-paper deadline, expansion to 14 pages plus appendices, the two-page Artifact Appendix, de-anonymization and restored acknowledgments, USENIX open-access publication from day one, and presenter obligations in Seattle.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Converting an OSDI acceptance into the published paper — the June final-paper deadline
- Expansion to 14 pages plus appendices
- The two-page Artifact Appendix
- De-anonymization and restored acknowledgments
Example prompts
- “/osdi-camera-ready”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Shepherd-mandated changes (conditional accepts): completed and approved, or
- Expansion into the final budget: up to 14 pages including figures and
- De-anonymization: real authors and institutions on the title page; the
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
Osdi Camera Ready loads about 1.7k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 771 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). 771 words, ~1,695 tokens.
Download SKILL.mdSave it as
.claude/skills/osdi-camera-ready/SKILL.md (or your agent's skills folder).- name
- osdi-camera-ready
- description
- Use when converting an OSDI acceptance into the published paper — the June final-paper deadline, expansion to 14 pages plus appendices, the two-page Artifact Appendix, de-anonymization and restored acknowledgments, USENIX open-access publication from day one, and presenter obligations in Seattle.
OSDI Camera-Ready
Deliver the final paper and the conference obligations. Dates and budgets below are the OSDI '26 cycle (notification March 26; final printable PDF due June 9, 2026; conference July 13–15, Seattle — verified 2026-07-08); confirm the current Requirements for Authors page before trusting any of them for another year.
The June 9 deliverable
The final paper is not the submission with names added. Between March and June three transformations happen, in this order:
- Shepherd-mandated changes (conditional accepts): completed and approved, or
the acceptance lapses — this dominates the calendar (
osdi-author-response). - Expansion into the final budget: up to 14 pages including figures and
tables, plus unlimited pages for references and appendices — the appendix
right the submission never had. Execute the expansion plan annotated in the
source at submission time (
osdi-supplementary): restore cut failure cases, attach the full proof, publish the complete result grids. - De-anonymization: real authors and institutions on the title page; the renamed system optionally reverts to its public name — decide deliberately, update every occurrence (body, figures, artifact, README), and keep paper and artifact names consistent forever after.
Plus the earned extra: papers that passed artifact evaluation may add a two-page
Artifact Appendix in the standard format, condensed from the AE runbook
(osdi-artifact-evaluation).
De-anonymization checklist
| Restore / fix | Detail commonly botched |
|---|---|
| Author block + affiliations | Ordering agreed in writing; affiliations as of the work, footnotes for moves |
| Acknowledgments | Funders, grant numbers, testbed credits (e.g., shared-cluster acknowledgment policies), colleagues |
| System name | If reverting from the anonymized name: figures and config listings too, not just prose |
| Self-citations | Third-person contortions rewritten as honest first person |
| Artifact pointer | The permanent archive identifier (DOI) in the paper, matching the AE record |
| PDF metadata | Title/author fields now should be populated correctly |
What USENIX publication means (and does not cost)
OSDI is a USENIX venue, which changes the publication economics authors expect from ACM conferences:
- Open access, immediately. The proceedings PDF is free to everyone from the day
the event begins — no paywall, no ACM DL entitlements, no separate "open access
option" to purchase. Your paper's canonical, citable home is a free
usenix.orgURL. - No author publication charge. USENIX funds events through registration (with hardship discounts offered for OSDI '26); there is no APC line item to budget.
- Slides and video posted after the event are likewise open. Assume the talk is a permanent public artifact and prepare it to that standard.
- Registration rates and any presenter-registration requirement were not readable at verification time (待核实) — confirm both on the attend pages before booking.
Consequence worth planning for: the paper is public during the conference, so reproduction attempts, blog dissections, and follow-up emails start in July, not after some embargo. Have the artifact live and the README polished by the event.
Show full SKILL.md (317 more words)Show less
Presentation and the event
- One author presents in Seattle (July 13–15 for the '26 cycle); check the Instructions for Presenters page for slide specs, session logistics, and A/V deadlines.
- The Jay Lepreau Best Paper Awards are announced from the accepted program — the opening-session tradition since OSDI '08.
- Prepare the talk against the same arc as the paper (pain → idea → evidence), not as a section tour; the audience holds the free PDF in their laps.
Between final paper and Seattle
The five weeks from June 9 to the July 13 opening are not idle:
- Talk first draft within a week of the final paper, while the argument is warm; systems talks fail from cramming the evaluation, so pick the two results that carry the idea and cut the rest to backup slides.
- Dry-run twice, once with systems people (they attack the design) and once with outsiders (they reveal which slide loses the room).
- Artifact final polish: the README's public debut is effectively July 13; run one last cold-start reproduction on a fresh machine or fresh container.
- Coordinate the announcement: with open-access publication at event start, the
lab blog post, the repository going public under its real name, and any preprint
update should all land the same week, pointing at the canonical
usenix.orgURL. - At the venue: sessions are recorded and posted openly; treat Q&A answers as citable statements about the system's limits.
Final-week mechanics
final-week checklist (against the '26 Requirements for Authors)
[ ] shepherd approval recorded (conditional accepts) — BLOCKING
[ ] 14-page budget respected; appendices compile; refs unlimited but clean
[ ] artifact appendix (if badged) in standard format, <= 2 pages
[ ] de-anonymization table above executed; grep for the anonymized name
[ ] figures regenerate from the ledger at the final commit (no stale panels)
[ ] printable PDF validates: fonts embedded, no overfull cropping, metadata set
[ ] uploaded to the submissions system before June 9; confirmation archived
[ ] consent/copyright forms: check current cycle's requirements (待核实)Discoverability after publication
Small June decisions determine how the paper is found for a decade: keep the title
byte-identical everywhere (final PDF, HotCRP record, talk slides, repository README)
so citation databases merge rather than fork the entries; put the artifact's DOI in
the paper and the paper's usenix.org URL in the artifact so each permanently
resolves the other; and once the dblp conf/osdi/ entry appears, adopt it as the
canonical BibTeX rather than letting five hand-typed variants propagate from the
lab's webpage.
Output format
[Deadline runway] days to final-paper due; shepherd status (n/a | pending | approved)
[Expansion] 14-page budget used how; appendix plan executed? artifact appendix in?
[De-anonymization] checklist rows outstanding: <list>
[Open-access readiness] artifact live + README public-grade before the event? yes/no
[Presenter logistics] registration/attendance items confirmed vs 待核实© 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 OSDI-Skills/skills/osdi-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Osdi Camera Ready 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 |
|---|---|---|---|---|---|---|
| Osdi Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Convertremotion-dev/remotion | 63k | — | ~247 | Automated safety check: Pass | Custom licence | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Acceptance Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~943 | Automated safety check: Pass | MIT | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 | |
| Word to Markdown Convertergithub/awesome-copilot | 40k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
- Official
Word to Markdown Converter
github/awesome-copilot
Converts Word .docx files to Markdown with a bundled script before analysis, extracting embedded images and handling whole folders alongside the PDF and Excel converters.
Change, Accept or Leave Framework
kangarooking/cangjie-skill
Helps someone stuck ruminating over an unchangeable situation decide whether to change it, accept it, or leave it, drawn from a chapter of Navalism-style writing.
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…
Questions about Osdi Camera Ready
What does Osdi Camera Ready do?
A skill your agent uses when converting an OSDI acceptance into the published paper — the June final-paper deadline, expansion to 14 pages plus appendices, the two-page Artifact Appendix…. Osdi Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an OSDI acceptance into the published paper — the June final-paper deadline, expansion to 14 pages plus appendices, the two-page Artifact Appendix, de-anonymization and restored acknowledgments, USENIX open-access publication from day one, and presenter obligations in Seattle.
When should I use Osdi Camera Ready?
Osdi Camera Ready fits situations like: converting an OSDI acceptance into the published paper — the June final-paper deadline; expansion to 14 pages plus appendices; the two-page Artifact Appendix; de-anonymization and restored acknowledgments.
How do I install Osdi Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-camera-ready -a claude-code`. Or copy the skill folder (OSDI-Skills/skills/osdi-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/osdi-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Osdi Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-camera-ready -a codex`. Or copy the skill folder (OSDI-Skills/skills/osdi-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/osdi-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Osdi Camera Ready 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 osdi-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/osdi-camera-ready, .gemini/skills/osdi-camera-ready, .github/skills/osdi-camera-ready and .opencode/skills/osdi-camera-ready in your project.
What does Osdi Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Osdi Camera Ready is instructions for the agent only.
Does Osdi Camera Ready 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 Osdi Camera Ready 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 Osdi Camera Ready use?
Osdi Camera Ready 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 Osdi Camera Ready use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Osdi Camera Ready?
Skills that share tags, products or a category with Osdi Camera Ready: Convert (remotion-dev/remotion, 63k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars) and Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Osdi Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.