Live Dashboard
NousResearch/hermes-agent
Build self-updating dashboards from live sources. An agent skill from NousResearch/hermes-agent.
A skill your agent uses when deciding what lives outside a EuroSys paper's 12 technical pages — free reference pages, whether the current round permits appendices or supplementary uploads…
MITAuto-check passed
Install Eurosys Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-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/EuroSys-Skills/skills/eurosys-supplementary .claude/skills/eurosys-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 "eurosys-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-supplementary into .claude/skills/eurosys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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/EuroSys-Skills/skills/eurosys-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 eurosys-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-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/EuroSys-Skills/skills/eurosys-supplementary .agents/skills/eurosys-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 "eurosys-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-supplementary into .agents/skills/eurosys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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 eurosys-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-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/EuroSys-Skills/skills/eurosys-supplementary .cursor/skills/eurosys-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 "eurosys-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-supplementary into .cursor/skills/eurosys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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 EuroSys-Skills/skills/eurosys-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 eurosys-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-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/EuroSys-Skills/skills/eurosys-supplementary .gemini/skills/eurosys-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 "eurosys-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-supplementary into .gemini/skills/eurosys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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 eurosys-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 eurosys-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/EuroSys-Skills/skills/eurosys-supplementary .github/skills/eurosys-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 "eurosys-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-supplementary into .github/skills/eurosys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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 eurosys-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 eurosys-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/EuroSys-Skills/skills/eurosys-supplementary .opencode/skills/eurosys-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 "eurosys-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-supplementary into .opencode/skills/eurosys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-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
eurosys-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 686 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 lives outside a EuroSys paper's 12 technical pages — free reference pages, whether the current round permits appendices or supplementary uploads…
- Works in 4 steps: Compress prose before cutting content —… → Merge figures that make one point;… → Move corroborating (not load-bearing)… → …
- Deciding what lives outside a EuroSys papers 12 technical pages — free reference pages
- SKILL.md covers The four shelves, What systems reviewers push…, Anonymized repository mechanics and Reference-page hygiene, plus 4 more sections
- Calls git
What it does
Eurosys Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what lives outside a EuroSys paper's 12 technical pages — free reference pages, whether the current round permits appendices or supplementary uploads, anonymized artifact repositories linked from the submission, and extended technical reports — without moving decision-critical evidence out of the reviewed pages.
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
- Deciding what lives outside a EuroSys papers 12 technical pages — free reference pages
- Whether the current round permits appendices
- Supplementary uploads
- Anonymized artifact repositories linked from the submission
Example prompts
- “/eurosys-supplementary”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Compress prose before cutting content — systems drafts carry 10–15% slack in
- Merge figures that make one point; delete figures that make none.
- Move corroborating (not load-bearing) material to the artifact repo with a
- Only then consider an appendix or tech report, after confirming the round's
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:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Eurosys Supplementary loads about 1.4k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 686 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). 686 words, ~1,446 tokens.
Download SKILL.mdSave it as
.claude/skills/eurosys-supplementary/SKILL.md (or your agent's skills folder).- name
- eurosys-supplementary
- description
- Use when deciding what lives outside a EuroSys paper's 12 technical pages — free reference pages, whether the current round permits appendices or supplementary uploads, anonymized artifact repositories linked from the submission, and extended technical reports — without moving decision-critical evidence out of the reviewed pages.
EuroSys Supplementary
Use this when a EuroSys draft overflows its 12 pages of technical content. The governing fact (EuroSys 2027 CFP, rendered 2026-07-08): the budget is 12 pages of technical content plus unlimited reference pages. Whether the current round accepts appendices beyond the references, or a separate supplementary upload in HotCRP, is per-cycle policy that was not verifiable on 2026-07-08 — 待核实 in the live CFP and the HotCRP submission form before relying on either.
The four shelves
| Shelf | Review status | What belongs there |
|---|---|---|
| 12 technical pages | Fully reviewed, the paper | Design, key mechanisms, headline evaluation, honest limitations |
| Reference pages | Free, always allowed | Bibliography only — never technical content disguised as notes |
| Anonymized artifact repo | Reviewer-optional | Code, configs, full result sets, extra graphs, raw logs |
| Extended tech report / appendix | Only if the round permits (待核实) | Proofs, protocol details, exhaustive parameter sweeps |
The iron rule across all shelves: a reviewer who reads only the 12 pages must be able to accept the paper. Anything reviewer-optional is corroboration, not argument. If the claim's only support sits on shelf 3 or 4, the claim is unsupported at decision time.
What systems reviewers push outward — and what they don't
Safe to externalize:
- Full configuration dumps and tuning grids behind a summarized sensitivity plot.
- Per-benchmark breakdowns when the body shows the aggregate plus the outliers.
- Formal-model details for a mechanism whose intuition the body already conveys.
- Additional workloads that repeat, rather than extend, the body's conclusion.
Dangerous to externalize at EuroSys:
- The baseline-fairness evidence (versions, tuning) — its absence from the body reads as concealment, the single most corrosive suspicion in systems review.
- The one experiment that tests the design's stated weakness.
- Failure-handling behavior for a system whose pitch is reliability.
Anonymized repository mechanics
When linking supporting material from a double-blind submission:
# Build an identity-clean mirror rather than sanitizing in place
git clone --depth 1 file:///lab/systemX systemX-anon && cd systemX-anon
rm -rf .git && grep -rInE 'university|lab-name|@|githubusercontent' . | less
# fix hits, then publish to an anonymous host (e.g., an anonymized-repo service)- Strip commit history entirely; author fields in old commits are the classic leak.
- Check config files and comments for hostnames, cluster names, and usernames.
- Keep the mirror frozen during review so reviewers see one consistent state.
Reference-page hygiene
The unlimited reference allowance is generous, not lawless:
- Bibliography pages hold citations — footnote essays, extended tables, or "notes" sections smuggled after the references invite a compliance read of the whole paper.
- Cite the version that supports the claim: a versioned release or paper, not a bare project homepage that will drift.
- Under double-blind, reference entries for your own artifacts must not resolve to identifying URLs; cite the anonymized mirror during review.
- Long URLs and dataset citations belong in the bibliography, where they are free, rather than inline where they spend technical-page budget.
Show full SKILL.md (262 more words)Show less
Micro-example: a 13.5-page draft
A distributed-tracing paper is 1.5 pages over. The cuts that worked, in order of pain: the second motivating scenario compressed to two sentences (0.4 pages); three per-workload latency plots collapsed into one CDF panel with the full set moved to the artifact repository (0.5 pages); the formal-consistency argument reduced to its statement plus intuition, full treatment in the repo's design note (0.4 pages); prose narration of Figure 4 deleted because the caption already said it (0.2 pages). Nothing reviewers needed for the accept/reject call left the body — that is the test each cut must pass.
Overflow triage, in order
- Compress prose before cutting content — systems drafts carry 10–15% slack in restated motivations and figure narration.
- Merge figures that make one point; delete figures that make none.
- Move corroborating (not load-bearing) material to the artifact repo with a one-line pointer in the body.
- Only then consider an appendix or tech report, after confirming the round's policy (待核实) and remembering reviewers owe it nothing.
Coordination with the review timeline
- Whatever optional material accompanies the submission must be final at the paper gate; there is no mid-review update channel, and a stale repo contradicting the PDF is worse than no repo.
- If a rebuttal phase exists, it cannot introduce a new supplement — externalized material must already be in place to be pointed at.
- A one-shot revision, by contrast, is a full resubmission: the revised round is the moment to promote material inward (e.g., a boundary experiment the conditions demanded) rather than to grow the repo.
Output format
[Page pressure] <current overflow in pages>
[Shelf plan] <item -> body / references / artifact repo / appendix-if-allowed>
[Decision-critical check] <claims whose evidence would leave the body: none / list>
[Anonymity status of repo] <clean / leaks found>
[待核实] <does this round allow appendices or supplementary uploads?>© 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 EuroSys-Skills/skills/eurosys-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Eurosys 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 |
|---|---|---|---|---|---|---|
| Eurosys Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Live DashboardNousResearch/hermes-agent | 252k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Live Dashboardnexu-io/open-design | 100k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Living Docs Governanceaffaan-m/ECC | 277k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Team Live OpsDonchitos/Claude-Code-Game-Studios | 26k | — | ~4.2k | Automated safety check: Notes | MIT |
Similar skills
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Live Dashboard
nexu-io/open-design
Notion-style team dashboard rendered as a Live Artifact. An agent skill from nexu-io/open-design.
Living Docs Governance
affaan-m/ECC
Keep a long-lived project's documentation from rotting by assigning existing project docs clear constitution, map, status, and history roles, then wiring the active agent harness to those canonical…
Team Live Ops
Donchitos/Claude-Code-Game-Studios
Orchestrate the live-ops team — live-ops-designer, economy-designer, analytics-engineer, community-manager, writer — for a season or live event.
Aria Live Regions
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Announce dynamic content with ARIA live regions.
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 Eurosys Supplementary
What does Eurosys Supplementary do?
A skill your agent uses when deciding what lives outside a EuroSys paper's 12 technical pages — free reference pages, whether the current round permits appendices or supplementary uploads…. Eurosys Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what lives outside a EuroSys paper's 12 technical pages — free reference pages, whether the current round permits appendices or supplementary uploads, anonymized artifact repositories linked from the submission, and extended technical reports — without moving decision-critical evidence out of the reviewed pages.
When should I use Eurosys Supplementary?
Eurosys Supplementary fits situations like: deciding what lives outside a EuroSys papers 12 technical pages — free reference pages; whether the current round permits appendices; supplementary uploads; anonymized artifact repositories linked from the submission.
How do I install Eurosys Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-supplementary -a claude-code`. Or copy the skill folder (EuroSys-Skills/skills/eurosys-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/eurosys-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Eurosys Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-supplementary -a codex`. Or copy the skill folder (EuroSys-Skills/skills/eurosys-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/eurosys-supplementary in your project. Codex loads it when a task matches its description.
Can I use Eurosys 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 eurosys-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/eurosys-supplementary, .gemini/skills/eurosys-supplementary, .github/skills/eurosys-supplementary and .opencode/skills/eurosys-supplementary in your project.
What does Eurosys Supplementary need to run?
Going by SKILL.md and its folder, Eurosys Supplementary needs the command-line tools its instructions call (git).
Does Eurosys Supplementary access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Eurosys 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 Eurosys Supplementary use?
Eurosys 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 Eurosys Supplementary use?
About 1.4k tokens (SKILL.md is roughly 5.8k 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 Eurosys Supplementary?
Skills that share tags, products or a category with Eurosys Supplementary: Live Dashboard (NousResearch/hermes-agent, 252k stars), Openclaw Live Updater (openclaw/openclaw, 392k stars), Live Dashboard (nexu-io/open-design, 100k stars) and Living Docs Governance (affaan-m/ECC, 277k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eurosys 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.