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 a SenSys submission — confirming the right per-edition HotCRP site and which of the two deadlines is open, the AoE cutoff in local…
MITAuto-check passed
Install Sensys Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-submission .claude/skills/sensys-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 "sensys-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-submission into .claude/skills/sensys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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/SenSys-Skills/skills/sensys-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 sensys-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-submission .agents/skills/sensys-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 "sensys-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-submission into .agents/skills/sensys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-submission .cursor/skills/sensys-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 "sensys-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-submission into .cursor/skills/sensys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 SenSys-Skills/skills/sensys-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 sensys-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-submission .gemini/skills/sensys-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 "sensys-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-submission into .gemini/skills/sensys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-submission .github/skills/sensys-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 "sensys-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-submission into .github/skills/sensys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-submission .opencode/skills/sensys-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 "sensys-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-submission into .opencode/skills/sensys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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
sensys-submission- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 587 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 a SenSys submission — confirming the right per-edition HotCRP site and which of the two deadlines is open, the AoE cutoff in local…
- The AoE cutoff in local time
- SKILL.md covers Gate 1 — the deadline is real…, Gate 2 — the geometry is legal, Gate 3 — nobody can tell whose… and Gate 4 — the form and the…, plus 2 more sections
- Calls pdftotext
- The 12/6-page double-column cap
What it does
Sensys Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-upload audit of a SenSys submission — confirming the right per-edition HotCRP site and which of the two deadlines is open, the AoE cutoff in local time, the 12/6-page double-column cap, the double-blind sweep including hardware and deployment leaks, and the resubmission-with-revision contract at the second deadline.
Its SKILL.md is about 1.4k 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
- The AoE cutoff in local time
- The 12/6-page double-column cap
- The double-blind sweep including hardware and deployment leaks
- The resubmission-with-revision contract at the second deadline
Example prompts
- “/sensys-submission”
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
Sensys Submission loads about 1.4k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 587 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). 587 words, ~1,436 tokens.
Download SKILL.mdSave it as
.claude/skills/sensys-submission/SKILL.md (or your agent's skills folder).- name
- sensys-submission
- description
- Use when running the final pre-upload audit of a SenSys submission — confirming the right per-edition HotCRP site and which of the two deadlines is open, the AoE cutoff in local time, the 12/6-page double-column cap, the double-blind sweep including hardware and deployment leaks, and the resubmission-with-revision contract at the second deadline.
SenSys Submission
Order the checks by how permanent the mistake is. A paper aimed at the wrong deadline, or a
first-deadline reject re-entered without its required revision, is bounced before a reviewer ever
opens it — nothing recovers that. Formatting and anonymity slips, by contrast, are fixable right
up to upload. So the audit below front-loads the irreversible gates and leaves the mechanical
sweeps for last. Treat every number as the 2026/2027 snapshot; the live HotCRP /deadlines page
overrides it.
Gate 1 — the deadline is real and yours
SenSys submits through a per-edition HotCRP instance (e.g. sensys27.hotcrp.com) and offers
two deadlines per cycle, each fully reviewed on its own. Confirm on the deadlines page:
- Whether the open deadline is the first or the second, and which edition it feeds — a mid-cycle submission competes for that edition's program, not one already decided.
- Whether this edition requires abstract registration ahead of the paper, and its date.
- That the cutoff is AoE, then convert it to each coauthor's wall clock — a Paris or New York time printed on the page is nobody's local midnight.
The resubmission gate is the one authors miss: if you are re-entering a first-deadline reject at
the second deadline, the submission is invalid without a substantive revision and a "Response
to Reviewers" tying each prior concern to a concrete change (sensys-author-response). A
repackaged reject is a desk reject.
Gate 2 — the geometry is legal
| Item | Rule (2027 cycle) | How to check |
|---|---|---|
| Full paper | ≤ 12 pages including figures and tables | Count the compiled PDF |
| Short paper | ≤ 6 pages (vision/experience track) | Confirm which track you entered |
| References | unlimited, beyond the cap | Nothing load-bearing tucked among them |
| Appendices | optional, after references, beyond the cap | Nothing a reviewer must read to believe the claim |
| Template | ACM double-column, geometry from the class file | Diff against the template; never resize by hand |
At SenSys the cap pressure is figures — power traces, latency CDFs, and testbed schematics eat
the body. Relieve it by cutting content, not by \vspace tricks or shrinking a measurement plot
past legibility; production and reviewers both notice. The exact template version and font floor
are 待核实 for the cycle — read the CFP.
Show full SKILL.md (228 more words)Show less
Gate 3 — nobody can tell whose paper it is
Beyond the standard anonymization (no names, affiliations, funding lines, or acknowledgments; third-person self-citation; references intact), SenSys papers leak identity through their hardware and deployments. Sweep the exact upload candidate:
# 1. text + metadata identity
pdftotext final.pdf - | grep -niE 'acknowledg|funded by|grant no|@[a-z]+\.(edu|com)'
pdfinfo final.pdf | grep -iE 'author|creator|producer'
# 2. paths and un-blinded artifact hosts
grep -rniE 'github\.com/[a-z0-9_-]+|zenodo\.org|/home/[a-z]+|/Users/[a-z]+' *.tex figures/
# 3. the SenSys-specific tell: a nameable site, testbed, or deployment
pdftotext final.pdf - | grep -niE 'our (lab|building|campus|deployment|testbed)|[A-Z][a-z]+ Hall|room [0-9]+|IRB'Strings are the easy part. A "30-node testbed across our engineering building" beside a photo of a distinctive atrium narrows to one group; soften identifying specifics to scale-descriptive language. And every artifact URL must resolve to a blinded repo or an author-stripped Zenodo deposit. A machine finds the strings; only a human reading for implication catches the rest — hand the PDF to a non-author and ask what lab they'd guess.
Gate 4 — the form and the policies
The HotCRP record is read before the PDF: title and abstract must match the paper word for word; topic tags steer the paper toward the sensing / embedded / IoT / on-device-AI reviewers you want bidding, so pick for reviewer fit rather than breadth; and the full author list is registered for conflict computation even while the PDF stays blind — a late author addition after assignment is a chairs-level problem. Declare conflicts exactly as the site defines them. Then clear the policy gates: no concurrent submission elsewhere; a stated delta for any overlapping workshop or poster; human-subjects and third-party-infrastructure handling addressed (wording 待核实); and the cycle's AI-use rule read live rather than assumed.
Run-of-show
T-8d account on the right instance + deadline; form fields drafted; conflicts entered
T-7d abstract registered if required; topic tags chosen for reviewer fit
T-2d content freeze; Gates 2-3 run on the near-final PDF; resubmission packet attached
T-1d coauthors sign off; HotCRP title/abstract match the PDF verbatim
T-0 upload → status ready; then re-download the stored file and open it — only server bytes countReport back
[Gate1] instance + first/second deadline + edition fed + AoE cutoff in local time
[Gate2] full/short track + page/column/template verdict
[Gate3] mechanical hits + human-read verdict (deployment + artifact-link giveaways)
[Resub] revision + Response-to-Reviewers attached? (second-deadline re-entry only)
[Gate4] form verbatim-match + conflicts + dual-sub/ethics/AI each cleared or flagged
[Open] live blockers, most-permanent first, each with an owner and hours-to-fix© 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 SenSys-Skills/skills/sensys-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sensys 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 |
|---|---|---|---|---|---|---|
| Sensys Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | 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 Sensys Submission
What does Sensys Submission do?
A skill your agent uses when running the final pre-upload audit of a SenSys submission — confirming the right per-edition HotCRP site and which of the two deadlines is open, the AoE cutoff in local…. Sensys Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-upload audit of a SenSys submission — confirming the right per-edition HotCRP site and which of the two deadlines is open, the AoE cutoff in local time, the 12/6-page double-column cap, the double-blind sweep including hardware and deployment leaks, and the resubmission-with-revision contract at the second deadline.
When should I use Sensys Submission?
Sensys Submission fits situations like: the AoE cutoff in local time; the 12/6-page double-column cap; the double-blind sweep including hardware and deployment leaks; the resubmission-with-revision contract at the second deadline.
How do I install Sensys Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-submission -a claude-code`. Or copy the skill folder (SenSys-Skills/skills/sensys-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sensys-submission in your project. Claude Code loads it when a task matches its description.
How do I install Sensys Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-submission -a codex`. Or copy the skill folder (SenSys-Skills/skills/sensys-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sensys-submission in your project. Codex loads it when a task matches its description.
Can I use Sensys 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 sensys-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/sensys-submission, .gemini/skills/sensys-submission, .github/skills/sensys-submission and .opencode/skills/sensys-submission in your project.
What does Sensys Submission need to run?
Going by SKILL.md and its folder, Sensys Submission needs the command-line tools its instructions call (pdftotext).
Does Sensys 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 Sensys 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 Sensys Submission use?
Sensys 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 Sensys Submission use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Sensys Submission?
Skills that share tags, products or a category with Sensys 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 Sensys 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.