File Uploads
davila7/claude-code-templates
Expert at handling file uploads and cloud storage. An agent skill from davila7/claude-code-templates.
A skill your agent uses when running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST, the 12-page/no-appendix check…
MITAuto-check passed
Install Osdi Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-submission --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-submission .claude/skills/osdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-submission into .claude/skills/osdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-submission --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-submission .agents/skills/osdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-submission into .agents/skills/osdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-submission --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-submission .cursor/skills/osdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-submission into .cursor/skills/osdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-submission --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-submission .gemini/skills/osdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-submission into .gemini/skills/osdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/osdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-submission into .github/skills/osdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-submission", 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-submission -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-submission --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-submission .opencode/skills/osdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-submission into .opencode/skills/osdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 760 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST, the 12-page/no-appendix check…
- Works in 2 steps: Institutions are anonymized too. Not… → The renamed-system rule. Prior…
- Running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST
- SKILL.md covers The two December gates, in…, Format gate (rejection-grade), Anonymity gate: OSDI's two… and Policy gate, plus 4 more sections
- Calls pdftotext
What it does
Osdi Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST, the 12-page/no-appendix check, institution-level double-blind rules, the renamed-system requirement, track choice, and the eight-submission author cap.
Its SKILL.md is about 1.6k 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
- Running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST
- The 12-page/no-appendix check
- Institution-level double-blind rules
- The renamed-system requirement
Example prompts
- “/osdi-submission”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Institutions are anonymized too. Not only names — the paper must not identify
- The renamed-system rule. Prior non-peer-reviewed exposure (arXiv, tech reports,
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
Shell commands in SKILL.md call:
pdftotext
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 Submission loads about 1.6k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 760 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). 760 words, ~1,624 tokens.
Download SKILL.mdSave it as
.claude/skills/osdi-submission/SKILL.md (or your agent's skills folder).- name
- osdi-submission
- description
- Use when running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST, the 12-page/no-appendix check, institution-level double-blind rules, the renamed-system requirement, track choice, and the eight-submission author cap.
OSDI Submission
Run this audit before touching the HotCRP upload form. Every rule below is the OSDI
'26 cycle as read on 2026-07-08 (osdi26.usenix.hotcrp.com plus the CFP); treat the
numbers as one year's snapshot and reopen the current CFP before acting.
The two December gates, in Pacific time
OSDI '26 split the deadline in two, and both were 2:59 pm PST — USENIX's local afternoon convention, not AoE midnight:
- Registration (Dec 4, 2025): title, abstract, authors, and track (Research or Operational Systems) created in HotCRP. Unregistered papers cannot be submitted a week later, full stop.
- Full submission (Dec 11, 2025): the final anonymized PDF uploaded and marked complete. HotCRP "complete" status is the state that counts — a draft sitting in the form is not a submission.
Convert 2:59 pm PST to every coauthor's time zone in writing. It is 10:59 pm in London, 6:59 am the next day in Beijing — the single most common OSDI logistics error is an AoE reflex from ML venues.
Format gate (rejection-grade)
| Check | OSDI '26 rule |
|---|---|
| Body length | ≤ 12 pages, single-spaced, including figures and tables |
| References | Unlimited extra pages |
| Appendices | Forbidden in the submission — no supplementary material |
| Type/layout | 10-pt Times-like on 12-pt leading, two columns, 7"×9" text block |
| Length norm | "The right length" — reviewers told to down-rank padded papers |
| Per-author load | At most eight submissions per author across the PC's pile |
The 12-page count including figures is stricter than it sounds: a figure-heavy systems
paper loses two pages to its own graphs. Compress via osdi-writing-style's passes,
never via geometry or font tampering.
Anonymity gate: OSDI's two distinctive rules
Beyond standard double-blind hygiene, OSDI '26 imposed two requirements authors from other venues miss:
- Institutions are anonymized too. Not only names — the paper must not identify the authors' institutions explicitly or by implication. "Our datacenter fleet" plus a trace only one company could own is an implication; describe the deployment in neutral scale terms.
- The renamed-system rule. Prior non-peer-reviewed exposure (arXiv, tech reports, talks, social posts) is permitted only if the submission uses a different, anonymized project/system name than any of those venues. Rename before the deadline, then sweep for the old name everywhere — body, figures, config listings, embedded paths.
# Mechanical sweep on the exact PDF you will upload
pdftotext paper.pdf - | grep -nEi 'OLDNAME|github\.com|gitlab|acknowledg|grant' | head
pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # metadata identity
pdffonts paper.pdf | head # embedded, expected fonts
# figures often embed usernames in paths: check figure sources too
grep -rnEi 'home/|Users/|OLDNAME' figures/ *.tex | headSelf-citations stay, in third person, treated as someone else's work
(osdi-related-work has the full protocol). Program co-chair conflicts are handled
by recusal on the PC side — your job is accurate conflict declaration in HotCRP, not
creative omission.
Policy gate
- Dual submission: not under review elsewhere; concurrent arXiv is fine (renamed), concurrent conference review is not.
- Track sanity: an experience paper registered as Research (or vice versa) is
reviewed against the wrong bar — re-check the registration before the Dec 4 gate
closes (
osdi-topic-selection). - Ethics: if measurements involved production users, disclosed vulnerabilities, or third-party infrastructure, address the ethics posture in the paper; check the current CFP's exact ethics wording (marked 待核实 in the source map) rather than assuming any specific code applies.
Show full SKILL.md (276 more words)Show less
HotCRP field hygiene
The form is read before the PDF and drives assignment; draft it before deadline day:
- Title and abstract must match the PDF verbatim — reviewers bid on the form, and drift between form and paper reads as carelessness.
- Topics/keywords route the paper to reviewers: pick for the reviewer you want (storage vs ML-systems vs distributed) rather than checking everything plausible.
- Author list complete at registration, even though anonymized in the PDF — HotCRP uses it for conflict computation, and a coauthor added after review assignment is a chairs-level problem.
- Conflicts: declared per HotCRP's definitions (advisors, recent coauthors, same institution), accurately and no wider — conflict inflation to dodge feared reviewers is detectable and sanctionable.
- The eight-per-author cap counts submissions on the form, so groups running multiple December papers should reconcile author lists before registration week.
Why this audit is terminal at OSDI
OSDI '26 had no author-response period. There is no later moment to explain that the missing baseline exists, that the leak was an oversight, or that page 13 was an accident. The submission as uploaded is the entire conversation until notification — which is also why the last step is non-negotiable: re-download the PDF from HotCRP and read it cold, checking that what reviewers will open is what you think you sent.
Final sequence
- T-7 days: register title/abstract/track (Dec 4 gate).
- T-3 days: freeze content; run the format gate table top to bottom.
- T-2 days: anonymity sweep (mechanical checks above + a human pass over figures).
- T-1 day: coauthor sign-off on the exact PDF; HotCRP fields match the PDF verbatim.
- T-0: upload, mark complete, re-download, cold-read, archive the receipt.
Output format
[Gate status] registration / format / anonymity / policy — each pass/fail
[Clock] local-time equivalent of the Pacific deadline; hours remaining
[Anonymity findings] <leak list or clean> incl. institution-implication check
[Renamed system] old name absent from body/figures/metadata? yes/no
[Terminal risks] items that cannot be explained later (no response period)
[Fix order] <ordered blockers before upload>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Osdi Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| File Uploadsdavila7/claude-code-templates | 33k | 4 repos | ~238 | Automated safety check: Pass | MIT | |
| File Upload Accessibilitythedaviddias/Front-End-Checklist | 74k | — | ~418 | Automated safety check: Pass | MIT | |
| Upload R2remotion-dev/remotion | 63k | — | ~535 | Automated safety check: Notes | Custom licence | |
| Hunt File Uploadsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Upload Element Previewsremotion-dev/remotion | 63k | — | ~265 | Automated safety check: Pass | Custom licence |
Similar skills
File Upload Accessibility
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Make file uploads accessible.
- Official
Upload R2
remotion-dev/remotion
Upload large Remotion repository assets to the Cloudflare R2 bucket behind remotion.media and replace local public/ assets with hosted URLs.
Hunt File Upload
sickn33/agentic-awesome-skills
Hunt file upload bugs
- Official
Upload Element Previews
remotion-dev/remotion
Upload a Remotion Element's preview assets to remotion.media and replace local preview URLs.
R2 Upload
zebbern/claude-code-guide
Upload files to Cloudflare R2, AWS S3, or any S3-compatible storage (like MinIO) and generate secure, time-limited presigned download links with configurable expiration, typically set to 5 minutes.
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 Submission
What does Osdi Submission do?
A skill your agent uses when running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST, the 12-page/no-appendix check…. Osdi Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST, the 12-page/no-appendix check, institution-level double-blind rules, the renamed-system requirement, track choice, and the eight-submission author cap.
When should I use Osdi Submission?
Osdi Submission fits situations like: running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST; the 12-page/no-appendix check; institution-level double-blind rules; the renamed-system requirement.
How do I install Osdi Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-submission -a claude-code`. Or copy the skill folder (OSDI-Skills/skills/osdi-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/osdi-submission in your project. Claude Code loads it when a task matches its description.
How do I install Osdi Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-submission -a codex`. Or copy the skill folder (OSDI-Skills/skills/osdi-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/osdi-submission in your project. Codex loads it when a task matches its description.
Can I use Osdi Submission 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-submission -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-submission, .gemini/skills/osdi-submission, .github/skills/osdi-submission and .opencode/skills/osdi-submission in your project.
What does Osdi Submission need to run?
Going by SKILL.md and its folder, Osdi Submission needs the command-line tools its instructions call (pdftotext).
Does Osdi Submission 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 Submission 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 Submission use?
Osdi Submission 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 Submission use?
About 1.6k tokens (SKILL.md is roughly 6.5k 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 Submission?
Skills that share tags, products or a category with Osdi Submission: File Uploads (davila7/claude-code-templates, 33k stars), File Upload Accessibility (thedaviddias/Front-End-Checklist, 74k stars), Upload R2 (remotion-dev/remotion, 63k stars) and Hunt File Upload (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Osdi Submission?
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.