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 belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that…
MITAuto-check passed
Install Percom Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-supplementary .claude/skills/percom-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 "percom-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-supplementary into .claude/skills/percom-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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/PerCom-Skills/skills/percom-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 percom-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-supplementary .agents/skills/percom-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 "percom-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-supplementary into .agents/skills/percom-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-supplementary .cursor/skills/percom-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 "percom-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-supplementary into .cursor/skills/percom-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 PerCom-Skills/skills/percom-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 percom-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-supplementary .gemini/skills/percom-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 "percom-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-supplementary into .gemini/skills/percom-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-supplementary .github/skills/percom-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 "percom-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-supplementary into .github/skills/percom-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-supplementary .opencode/skills/percom-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 "percom-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-supplementary into .opencode/skills/percom-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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
percom-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 442 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 belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that…
- Deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix
- SKILL.md covers What goes where, The 9-page-budget discipline, Double-blind supplementary rules and Appendix architecture (when…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the tight IEEEtran 9+1 page budget
What it does
Percom Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary material, and how to split a human-subjects sensing paper between body and dataset.
Its SKILL.md is about 1.2k 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
- Deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix
- Covering the tight IEEEtran 9+1 page budget
- The rule that decision-critical evidence stays inside the reviewed pages
- Double-blind supplementary material
Example prompts
- “/percom-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
Percom Supplementary loads about 1.2k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 442 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). 442 words, ~1,171 tokens.
Download SKILL.mdSave it as
.claude/skills/percom-supplementary/SKILL.md (or your agent's skills folder).- name
- percom-supplementary
- description
- Use when deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary material, and how to split a human-subjects sensing paper between body and dataset.
PerCom Supplementary
Use this when assembling PerCom supplementary material. The governing rule is simple and strict: the paper must be judgeable from the reviewed pages alone. The dataset and any appendix support the paper; they do not hold the argument. Reviewers read supplementary material at their discretion, so anything the decision depends on lives in the 9 pages — and PerCom's budget is tight, which makes the split unforgiving.
What goes where
| Content | Body (within 9-page budget) | Dataset / appendix |
|---|---|---|
| The pervasive-computing claim and headline result | Yes | — |
| Core technique or study design | Yes | Full hyperparameter grids, extra config |
| The cross-subject (LOSO) headline evaluation | Yes | Full per-subject / per-session tables |
| Metrics behind a claim (F1, event-level) | The result + metric named | The computation notebook |
| Subject and sensor description | Summary + selection criterion | The complete datasheet |
| Raw signals, logs, labels, scripts | — | Yes |
| Reproduction instructions | A pointer | The README and run scripts |
If a reviewer would need to open the dataset to know whether to accept, the paper is mis-partitioned — move that evidence into the body.
The 9-page-budget discipline
PerCom's IEEEtran budget (9 pages technical content + 1 page references) is a fraction of a single-column ACM budget and counts figures, tables, and any in-paper appendix. Consequences:
- The cross-subject result and its key limitation must be in the body — they are decision-critical, and reviewers will not go hunting for them.
- Long per-subject breakdowns, full hyperparameter grids, additional sensor modalities, and extra ablations go to the dataset/appendix with explicit forward references.
- Do not use the dataset to smuggle in a result that would not fit — an argument that only closes with material outside the reviewed pages reads as unreviewable.
- Compress with editing (tighter figures, merged tables), never by shrinking the font or margins —
that is a desk-reject ground at IEEE venues (
percom-submission).
Show full SKILL.md (150 more words)Show less
Double-blind supplementary rules
[No identity] no authors, affiliations, acknowledgements, grants, testbed/lab names, deployment
sites, or dataset-owner strings anywhere in the archive or appendix
[Anonymized links] the dataset/code link points at an anonymizing host, not a personal repo
[Clean archive] no .git history, .DS_Store, credentials, caches, or large irrelevant files
[No re-ID media] no photos/video revealing a face, building, or badge that de-anonymizes authors
[Opens clean] verify the archive unzips and the README orients a reader in one minute on a
fresh machineAppendix architecture (when the template allows in-paper appendices)
- Remember appendices count against the 9 pages — an in-paper appendix trades against the body. Prefer the external dataset/artifact for bulk material.
- Order any appendix to mirror the RQ / evaluation order; reviewers navigate by claim, not page.
- Keep each appendix section referenced from the body at least once — orphaned material is invisible under discretionary review.
Vignette: splitting a mixed-modality sensing paper
A paper combining wrist-IMU recognition with an ambient-sensor deployment: the body keeps the claim, the study design, the leave-one-subject-out headline result with F1 and confidence intervals, the key deployment finding, and a limitations subsection; the dataset/artifact holds the full per-subject tables, the ambient-sensor logs, the labeling protocol with annotator agreement, the device/sampling datasheet, and the analysis notebooks. Nothing decision-critical lives only in the artifact, because artifact inspection is discretionary and the reviewers judge from the 9 pages.
Output format
[Supplement status] ready / needs fixes / not ready
[Partition check] anything decision-critical (esp. cross-subject result) outside the body? <none / move: what>
[Page budget] body within 9 pages? appendices counted? refs within 1 page? yes/no
[Anonymity] archive clean of identity + re-identifying media? passed/issues
[Body dependency] <what a reviewer can decide without opening the dataset>© 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 PerCom-Skills/skills/percom-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Percom 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 |
|---|---|---|---|---|---|---|
| Percom Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | 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 | |
| Icdm Supplementarybrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT |
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.
Icdm Supplementary
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when organizing supplementary and appendix material for an ICDM (IEEE International Conference on Data Mining) paper - deciding what belongs in the body, in an appendix that…
Ase Supplementary
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when deciding what belongs in the 10-page ASE (IEEE/ACM Automated Software Engineering) paper body versus the artifact and supplementary material, splitting content by…
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 Percom Supplementary
What does Percom Supplementary do?
A skill your agent uses when deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that…. Percom Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary material, and how to split a human-subjects sensing paper between body and dataset.
When should I use Percom Supplementary?
Percom Supplementary fits situations like: deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix; covering the tight IEEEtran 9+1 page budget; the rule that decision-critical evidence stays inside the reviewed pages; double-blind supplementary material.
How do I install Percom Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-supplementary -a claude-code`. Or copy the skill folder (PerCom-Skills/skills/percom-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/percom-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Percom Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-supplementary -a codex`. Or copy the skill folder (PerCom-Skills/skills/percom-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/percom-supplementary in your project. Codex loads it when a task matches its description.
Can I use Percom 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 percom-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/percom-supplementary, .gemini/skills/percom-supplementary, .github/skills/percom-supplementary and .opencode/skills/percom-supplementary in your project.
What does Percom Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Percom Supplementary is instructions for the agent only.
Does Percom 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 Percom 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 Percom Supplementary use?
Percom 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 Percom Supplementary use?
About 1.2k tokens (SKILL.md is roughly 4.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 Percom Supplementary?
Skills that share tags, products or a category with Percom 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 Percom Supplementary?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.