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 EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that…
MITAuto-check passed
Install Edbt Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills edbt-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/EDBT-Skills/skills/edbt-supplementary .claude/skills/edbt-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 "edbt-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-supplementary into .claude/skills/edbt-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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/EDBT-Skills/skills/edbt-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 edbt-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills edbt-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/EDBT-Skills/skills/edbt-supplementary .agents/skills/edbt-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 "edbt-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-supplementary into .agents/skills/edbt-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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 edbt-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills edbt-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/EDBT-Skills/skills/edbt-supplementary .cursor/skills/edbt-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 "edbt-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-supplementary into .cursor/skills/edbt-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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 EDBT-Skills/skills/edbt-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 edbt-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills edbt-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/EDBT-Skills/skills/edbt-supplementary .gemini/skills/edbt-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 "edbt-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-supplementary into .gemini/skills/edbt-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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 edbt-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 edbt-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/EDBT-Skills/skills/edbt-supplementary .github/skills/edbt-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 "edbt-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-supplementary into .github/skills/edbt-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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 edbt-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 edbt-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/EDBT-Skills/skills/edbt-supplementary .opencode/skills/edbt-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 "edbt-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EDBT-Skills/skills/edbt-supplementary into .opencode/skills/edbt-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edbt-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
edbt-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 426 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 EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that…
- Deciding what belongs in an EDBT paper body versus its artifact and appendices
- SKILL.md covers What goes where, The page-budget discipline…, Reproducibility-forward… and Appendix architecture (when…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the per-shape page budget with unlimited references
What it does
Edbt Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in an EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that decision-critical evidence stays inside the reviewed pages, and how to split a database-systems paper between body and reproducible package.
Its SKILL.md is about 1.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
- Deciding what belongs in an EDBT paper body versus its artifact and appendices
- Covering the per-shape page budget with unlimited references
- The rule that decision-critical evidence stays inside the reviewed pages
- How to split a database-systems paper between body and reproducible package
Example prompts
- “/edbt-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
Edbt Supplementary loads about 1.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 426 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). 426 words, ~1,118 tokens.
Download SKILL.mdSave it as
.claude/skills/edbt-supplementary/SKILL.md (or your agent's skills folder).- name
- edbt-supplementary
- description
- Use when deciding what belongs in an EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that decision-critical evidence stays inside the reviewed pages, and how to split a database-systems paper between body and reproducible package.
EDBT Supplementary
Use this when assembling EDBT supplementary material. The governing rule is simple and strict: the paper must be judgeable from the reviewed pages alone. The artifact and any appendix support the paper; they do not hold the argument. Reviewers open the artifact at their discretion, so anything the decision depends on lives in the body.
What goes where
| Content | Body (within page budget) | Artifact / appendix |
|---|---|---|
| The problem, contribution, and what it enables | Yes | — |
| Core mechanism / system design | Yes | Full parameter grids, extra configs |
| The headline results and the scope/overhead | Yes | Full result tables, secondary sweeps |
| The evaluation setup a claim depends on | Named in the body | The complete harness and logs |
| Workload / dataset summary + derivation | Summary + criterion | The full derivation scripts and data |
| Raw logs, build scripts, containers | — | Yes |
| Reproduction instructions | A pointer | The README and run scripts |
If a reviewer would need to open the artifact to know whether to accept, the paper is mis-partitioned — move that evidence into the body.
The page-budget discipline (per shape)
EDBT's budget depends on the paper shape (EDBT 2022 CFP; reverify per cycle): Regular and Experiments & Analysis papers ≤12 pages; Vision papers ≤6; references are unlimited and do not count. Consequences:
- References do not eat your budget — cite generously; the constraint is body text, figures, tables, and in-body appendices.
- Keep the headline result tables and the scope/overhead discussion in the body — they are decision-critical.
- Long parameter sweeps, per-configuration breakdowns, and full harness output go to the artifact with explicit forward references.
- Do not use the artifact to smuggle in a result that would not fit — an argument that only closes with material outside the reviewed pages reads as unreviewable.
Show full SKILL.md (148 more words)Show less
Reproducibility-forward supplementary rules
[Runnable] the artifact builds and runs from its README on a clean machine; a demo run succeeds
[Provenance] dataset versions, workload derivation, engine build/commit, and seeds are pinned
[Consistency] every body number traces to a script in the package
[Clean archive] no stray credentials, caches, or huge irrelevant files; (if double-blind) no
identity strings, owner paths, or cluster names
[Opens clean] verify the archive unpacks and the README orients a reader in one minuteAppendix architecture (when the template allows in-body appendices)
- Order appendix sections to mirror the evaluation's structure; reviewers navigate by result, not page number.
- Keep each appendix section referenced from the body at least once — orphaned material is invisible under discretionary review.
- Confirm on the current call whether in-body appendices count against the page budget (they usually do) versus supplementary material attached separately; this changes the split.
Vignette: splitting a distributed-systems paper
A paper contributing a query-processing operator and its evaluation: the body keeps the problem, the mechanism, the headline latency/scalability results with variance, the overhead-on-skew-free case, and a scope subsection; the artifact holds the container/build recipe, the workload-derivation scripts with pinned dataset versions, the full parameter sweeps, the raw logs, and the analysis notebooks. Nothing decision-critical lives only in the artifact, because artifact inspection is discretionary and the reviewers judge from the pages.
Output format
[Supplement status] ready / needs fixes / not ready
[Shape + budget] Regular | Experiments-&-Analysis | Vision — body within limit?
[Partition check] anything decision-critical outside the body? <none / move: what>
[Reproducibility] artifact runnable + provenance pinned + consistent with paper? yes/no
[Clean archive] (if double-blind) identity-free; no stray files? passed/issues
[Body dependency] <what a reviewer can decide without opening the artifact>© 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 EDBT-Skills/skills/edbt-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Edbt 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 |
|---|---|---|---|---|---|---|
| Edbt Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.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 | |
| Ase Supplementarybrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~987 | 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.
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…
Facct Supplementary
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when deciding what belongs in an ACM FAccT paper body versus its endmatter statements, appendices, and supplementary material — the 14-page acmart budget, the extra endmatter…
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 Edbt Supplementary
What does Edbt Supplementary do?
A skill your agent uses when deciding what belongs in an EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that…. Edbt Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what belongs in an EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that decision-critical evidence stays inside the reviewed pages, and how to split a database-systems paper between body and reproducible package.
When should I use Edbt Supplementary?
Edbt Supplementary fits situations like: deciding what belongs in an EDBT paper body versus its artifact and appendices; covering the per-shape page budget with unlimited references; the rule that decision-critical evidence stays inside the reviewed pages; how to split a database-systems paper between body and reproducible package.
How do I install Edbt Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-supplementary -a claude-code`. Or copy the skill folder (EDBT-Skills/skills/edbt-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/edbt-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Edbt Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-supplementary -a codex`. Or copy the skill folder (EDBT-Skills/skills/edbt-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/edbt-supplementary in your project. Codex loads it when a task matches its description.
Can I use Edbt 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 edbt-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/edbt-supplementary, .gemini/skills/edbt-supplementary, .github/skills/edbt-supplementary and .opencode/skills/edbt-supplementary in your project.
What does Edbt Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Edbt Supplementary is instructions for the agent only.
Does Edbt 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 Edbt 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 Edbt Supplementary use?
Edbt 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 Edbt Supplementary use?
About 1.1k tokens (SKILL.md is roughly 4.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 Edbt Supplementary?
Skills that share tags, products or a category with Edbt 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 Edbt 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.