Aria Hidden Body
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Do not use aria-hidden on the document body.
A skill your agent uses when deciding what goes in a SenSys paper's body versus its unlimited references and appendices versus HotCRP fields — keeping the double-column body carrying the argument…
MITAuto-check passed
Install Sensys Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-supplementary --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-supplementary .claude/skills/sensys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-supplementary into .claude/skills/sensys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-supplementary", 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-supplementaryType 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-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-supplementary --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-supplementary .agents/skills/sensys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-supplementary into .agents/skills/sensys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-supplementary", 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-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-supplementary --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-supplementary .cursor/skills/sensys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-supplementary into .cursor/skills/sensys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-supplementary", 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-supplementary--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-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-supplementary --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-supplementary .gemini/skills/sensys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-supplementary into .gemini/skills/sensys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-supplementary", 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-supplementaryInstalls 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-supplementary -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-supplementary .github/skills/sensys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-supplementary into .github/skills/sensys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-supplementary", 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-supplementary -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-supplementary --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-supplementary .opencode/skills/sensys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-supplementary into .opencode/skills/sensys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-supplementary", 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-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 417 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding what goes in a SenSys paper's body versus its unlimited references and appendices versus HotCRP fields — keeping the double-column body carrying the argument…
- Moving full protocols
- SKILL.md covers The placement decision, The body earns its space, Blind the artifact links and Keep the resubmission packet…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Derivations to the appendix
What it does
Sensys Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what goes in a SenSys paper's body versus its unlimited references and appendices versus HotCRP fields — keeping the double-column body carrying the argument, moving full protocols, extra plots, and derivations to the appendix, blinding anonymous artifact links, and keeping the Response to Reviewers out of the body.
Its SKILL.md is about 1k 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
- Moving full protocols
- Derivations to the appendix
- Blinding anonymous artifact links
- Keeping the Response to Reviewers out of the body
Example prompts
- “/sensys-supplementary”
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
Sensys Supplementary loads about 1k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 417 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). 417 words, ~1,000 tokens.
Download SKILL.mdSave it as
.claude/skills/sensys-supplementary/SKILL.md (or your agent's skills folder).- name
- sensys-supplementary
- description
- Use when deciding what goes in a SenSys paper's body versus its unlimited references and appendices versus HotCRP fields — keeping the double-column body carrying the argument, moving full protocols, extra plots, and derivations to the appendix, blinding anonymous artifact links, and keeping the Response to Reviewers out of the body.
SenSys Supplementary Material
SenSys gives you an unusual amount of room outside the page cap: references and appendices are unlimited. That freedom is a trap if it becomes a dumping ground. The discipline is to keep the ≤ 12-page (full) or ≤ 6-page (short) body carrying the argument, and to place everything a reviewer might want but does not need to judge the claim in the appendix — reachable, but not in the way of the story.
The placement decision
For each piece of content, ask: must a reviewer read this to believe the headline claim?
| Content | Body (in the cap) | Appendix (unlimited) | HotCRP field |
|---|---|---|---|
| The mechanism and its constraint model | Yes | — | — |
| The headline energy/latency/accuracy results | Yes | — | — |
| Full measurement protocol (instrument settings, calibration steps) | Summary only | Full detail | — |
| Extra ablations and secondary plots | The load-bearing ones | The rest | — |
| Derivations / proofs of a bound | Statement + intuition | Full proof | — |
| Complete hardware BOM and wiring | — | Yes | — |
| Deployment logs, per-node uptime tables | Summary | Full tables | — |
| Title, abstract, topics, conflicts | — | — | Yes (verbatim-match PDF) |
| Anonymous artifact link | Cited in text (blinded) | — | If the form asks |
The body earns its space
Because appendices are free, the body must be ruthless: every paragraph either advances the
sensing-pain → mechanism → measured-behavior arc (sensys-writing-style) or moves to the
appendix. A body padded with protocol detail reads as unfocused; a body that states results and
points to App. B for the protocol reads as confident. Reviewers are not obligated to read
appendices, so nothing load-bearing may hide there — if the claim depends on it, summarize it
in the body and expand in the appendix.
Show full SKILL.md (158 more words)Show less
Blind the artifact links
Supplementary artifact links are the classic anonymity leak. During double-blind review:
[ ] Repo link is an anonymized mirror (no username, no lab/org in the URL).
[ ] Zenodo/OSF deposit has authors anonymized.
[ ] No link resolves to a personal, lab, department, or company domain.
[ ] Trace/data archives carry no author metadata or identifying paths.A single un-blinded GitHub URL in the supplement can de-anonymize the whole submission — sweep the
appendix with the same rigor as the body (sensys-submission).
Keep the resubmission packet out of the body
If you are resubmitting at the next deadline, the Response to Reviewers is a separate document
(sensys-author-response), not appended to the paper's body — it must not consume page budget and
must follow the CFP's stated form (待核实 for the exact mechanism). The revised paper stands on its
own; the response explains how it changed.
Structure the appendix so it is navigable
An unlimited appendix that no one can navigate is wasted. Give it the same structure your body promises: if §4.2 says "full protocol in App. B," App. B exists, is labeled, and contains exactly that. Cross-reference precisely — a reviewer checking one number should reach it in one hop.
Output format
[Body] is every body paragraph load-bearing? list what should move to appendix
[Appendix] is anything load-bearing hiding in the (optional-to-read) appendix?
[Blind] artifact/data links swept for anonymity — pass/gap
[Resub] response-to-reviewers kept out of the body? (if applicable)
[Nav] body cross-references resolve to labeled appendix sections? pass/gap
[Open] the one placement decision most affecting how the paper reads© 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-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sensys Supplementary 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 Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Aria Hidden Bodythedaviddias/Front-End-Checklist | 74k | — | ~444 | Automated safety check: Pass | MIT | |
| Meta In Bodythedaviddias/Front-End-Checklist | 74k | — | ~541 | Automated safety check: Pass | MIT | |
| Pull Request Title and Body Writeropeninterpreter/openinterpreter | 69k | 2 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Function Bodyonnx/onnx | 22k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Aer Paper Bodybrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | 1 repos | ~3.3k | Automated safety check: Pass | Custom licence |
Similar skills
Meta In Body
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing HTML document structure.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
Add Function Body
onnx/onnx
Add a function body definition to an ONNX operator, defining how it decomposes into simpler ops.
Aer Paper Body
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when drafting or revising the body sections of an AER, AER:Insights, or AEJ manuscript — institutional background, data, empirical strategy, results, mechanisms, and…
Three-Body Video Creation Pipeline
anbeime/skill
Multi-stage workflow for producing videos set in the Three-Body universe, from lore research and storyboards to voice, sound and music generation and final compositing.
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 Supplementary
What does Sensys Supplementary do?
A skill your agent uses when deciding what goes in a SenSys paper's body versus its unlimited references and appendices versus HotCRP fields — keeping the double-column body carrying the argument…. Sensys Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what goes in a SenSys paper's body versus its unlimited references and appendices versus HotCRP fields — keeping the double-column body carrying the argument, moving full protocols, extra plots, and derivations to the appendix, blinding anonymous artifact links, and keeping the Response to Reviewers out of the body.
When should I use Sensys Supplementary?
Sensys Supplementary fits situations like: moving full protocols; derivations to the appendix; blinding anonymous artifact links; keeping the Response to Reviewers out of the body.
How do I install Sensys Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-supplementary -a claude-code`. Or copy the skill folder (SenSys-Skills/skills/sensys-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sensys-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Sensys Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-supplementary -a codex`. Or copy the skill folder (SenSys-Skills/skills/sensys-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sensys-supplementary in your project. Codex loads it when a task matches its description.
Can I use Sensys Supplementary 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-supplementary -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-supplementary, .gemini/skills/sensys-supplementary, .github/skills/sensys-supplementary and .opencode/skills/sensys-supplementary in your project.
What does Sensys Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Sensys Supplementary is instructions for the agent only.
Does Sensys Supplementary 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 Supplementary 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 Supplementary use?
Sensys Supplementary 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 Supplementary use?
About 1k tokens (SKILL.md is roughly 4k 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 Supplementary?
Skills that share tags, products or a category with Sensys Supplementary: Aria Hidden Body (thedaviddias/Front-End-Checklist, 74k stars), Meta In Body (thedaviddias/Front-End-Checklist, 74k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Add Function Body (onnx/onnx, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sensys Supplementary?
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.