Topics
ZimoLiao/scholaraio
A skill your agent uses when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.
Agent skill
Eurosys Topic Selection
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when deciding whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS, distributed systems, storage, cloud, virtualization, security, and ML…
MITAuto-check passed
Install Eurosys Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-topic-selection --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-topic-selection .claude/skills/eurosys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-topic-selection into .claude/skills/eurosys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-topic-selection", 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-topic-selectionType 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-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-topic-selection --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-topic-selection .agents/skills/eurosys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-topic-selection into .agents/skills/eurosys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-topic-selection", 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-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-topic-selection --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-topic-selection .cursor/skills/eurosys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-topic-selection into .cursor/skills/eurosys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-topic-selection", 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-topic-selection--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-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills eurosys-topic-selection --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-topic-selection .gemini/skills/eurosys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-topic-selection into .gemini/skills/eurosys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-topic-selection", 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-topic-selectionInstalls 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-topic-selection -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-topic-selection .github/skills/eurosys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-topic-selection into .github/skills/eurosys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-topic-selection", 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-topic-selection -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-topic-selection --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-topic-selection .opencode/skills/eurosys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EuroSys-Skills/skills/eurosys-topic-selection into .opencode/skills/eurosys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eurosys-topic-selection", 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-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 656 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS, distributed systems, storage, cloud, virtualization, security, and ML…
- Deciding whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS
- SKILL.md covers The substance bar, Routing from the EuroSys seat, Fit self-interrogation and Contribution shapes EuroSys…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Distributed systems
What it does
Eurosys Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS, distributed systems, storage, cloud, virtualization, security, and ML systems — or routes better to SOSP, OSDI, NSDI, ASPLOS, ATC, FAST, or SoCC, and how the April slot and dual deadlines affect that call.
Its SKILL.md is about 1.5k 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 whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS
- Distributed systems
- Routes better to SOSP
- How the April slot and dual deadlines affect that call
Example prompts
- “/eurosys-topic-selection”
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
Eurosys Topic Selection loads about 1.5k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 656 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). 656 words, ~1,536 tokens.
Download SKILL.mdSave it as
.claude/skills/eurosys-topic-selection/SKILL.md (or your agent's skills folder).- name
- eurosys-topic-selection
- description
- Use when deciding whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS, distributed systems, storage, cloud, virtualization, security, and ML systems — or routes better to SOSP, OSDI, NSDI, ASPLOS, ATC, FAST, or SoCC, and how the April slot and dual deadlines affect that call.
EuroSys Topic Selection
Use this before serious writing begins. EuroSys is the flagship conference of
the European Chapter of ACM SIGOPS (eurosys.org, rendered 2026-07-08),
running annually since 2006 and seeking papers on all areas of computer
systems — it is a broad-church systems venue, not a niche. The 2026 edition
(the 21st) met in Edinburgh in April; 2027 meets in Rabat. The right question
is rarely "is this systems?" but "is this conference-grade systems, and is
EuroSys the best-positioned jury and calendar slot for it?"
The substance bar
A EuroSys-ready project typically has all four:
- A built thing. An implemented system or substantial modification, not a simulation of one (measurement and experience papers are the exception, and must be framed as such).
- A transferable idea. An abstraction, mechanism, or empirically established principle that outlives this codebase.
- Evidence under realistic conditions. Workloads and scale that resemble the deployment story being told.
- An articulable insight. One sentence a reviewer can carry into the PC meeting. Strong engineering without a nameable idea routes to ATC-style venues or an experience track.
Routing from the EuroSys seat
| Center of gravity | Stay or route | Why |
|---|---|---|
| OS/kernel, runtimes, virtualization, distributed infra | EuroSys core | The venue's home ground since 2006 |
| ML systems (serving, training infra) | EuroSys core, growing | Recent best papers are LLM-serving systems (e.g., EuroSys '25) |
| Once-a-generation OS-principles result | Consider SOSP/OSDI too | Same-family flagships; route by cycle timing and audience |
| Network protocols, measurement of networks | NSDI / SIGCOMM | EuroSys reads it as out-of-center networking |
| Hardware/software interface, arch mechanisms | ASPLOS | Architecture jury evaluates architecture ideas |
| Storage-stack internals | FAST first | Deepest storage jury; EuroSys viable for broader claims |
| Cloud-native ops, serverless economics | SoCC / Middleware also viable | Match the paper's altitude to the jury |
| Pragmatic engineering, tool papers | USENIX ATC | Idea-density bar differs there |
Two calendar facts sharpen the call: EuroSys's April conference and dual gates (May and September submissions for 2027) interleave with the SOSP/OSDI and NSDI cycles, so a systems result can almost always find a flagship gate within a few months — pick by fit and readiness, never by whichever deadline is nearest. And a EuroSys rejection blocks the same round for a year, which makes premature submission genuinely expensive.
Fit self-interrogation
1. Insight test: state the idea in one sentence without naming your system.
2. Jury test: which three published papers would this one sit between?
If ≥2 are EuroSys/SOSP/OSDI papers, EuroSys is plausible.
3. Evidence test: does the current evaluation reach the four-layer stack
(end-to-end / decomposition / cost / boundary)? If not, is it reachable
by the target gate?
4. Regime test: is the claim's deployment story credible to reviewers who
run real infrastructure?
5. Calendar test: which gate (spring/fall) matches the project's maturity,
accounting for the one-year ban if it fails?Show full SKILL.md (294 more words)Show less
Contribution shapes EuroSys publishes
The exemplars library (resources/exemplars/library.md) documents these
shapes across two decades of the venue's own award line:
| Shape | Award-line instance | What it must bring |
|---|---|---|
| General abstraction + engine | Dryad (2007) | Proof the abstraction subsumes existing practice |
| Tool with a thesis | Coccinelle line (2008) | Validation on the real ecosystem it targets |
| Small mechanism, big evidence | Delay Scheduling (2010) | Production-shaped workloads carrying a simple idea |
| Design-space taxonomy | Omega (2013) | Vocabulary plus trace-driven comparison |
| Production retrospective | Borg (2015) | Transferable lessons including failures |
| ML-infrastructure mechanism | CacheBlend (2025) | A systems idea legible without ML expertise |
If the project matches none of these shapes, that is not disqualifying — but it should prompt a harder look at what the contribution type is before a EuroSys jury is chosen for it.
Signals you are forcing it
- The contribution sentence contains "we combine" and three technique names but no invariant or tradeoff.
- The evaluation exists only at benchmark scale while the pitch is production scale.
- The nearest related work is entirely from another community's venues — the jury you are choosing has no vocabulary for the delta.
- The plan is "submit to fall EuroSys because SOSP just closed" — deadline proximity masquerading as venue fit.
When EuroSys is the strategically right flagship
Beyond raw fit, three situations tilt toward EuroSys among the systems flagships:
- The work speaks to infrastructure and communities strongly represented on European PCs (e.g., European cloud/telecom operators, EU data-locality constraints) and benefits from that jury's context.
- The project's maturity curve matches a EuroSys gate now, and waiting for another flagship's next cycle risks being scooped by a fast-moving line of work.
- The team wants the artifact culture: sysartifacts badges plus a named artifact award make EuroSys a strong home for systems whose artifact is part of the contribution.
Output format
[Verdict] EuroSys-ready / EuroSys-plausible after gaps / route elsewhere
[Insight sentence] <the transferable idea, system name omitted>
[Neighbor triangulation] <three papers this would sit between>
[Best-fit gate] spring / fall 2027+ with readiness rationale
[If routing away] <venue + the specific mismatch driving it>© 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-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Eurosys Topic Selection 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 Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| TopicsZimoLiao/scholaraio | 576 | — | ~294 | Automated safety check: Pass | MIT | |
| Topic Modelingbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Bestblogs Topicginobefun/BestBlogs | 4k | — | ~670 | Automated safety check: Pass | None | |
| Zsxq Topicitwanger/toBeBetterJavaer | 18k | — | ~564 | Automated safety check: Pass | None | |
| Eurosysfranklee16/academic-research-skills | 223 | 1 repos | ~1.8k | Automated safety check: Pass | None |
Similar skills
Topic Modeling
brycewang-stanford/Auto-Empirical-Research-Skills
Structural topic modeling: STM spec, topic count, coherence-exclusivity.
Bestblogs Topic
ginobefun/BestBlogs
A skill your agent uses when the user asks about a specific topic, subject area, or wants to explore curated topic pages on BestBlogs.
Zsxq Topic
itwanger/toBeBetterJavaer
知识星球主题管理：搜索主题、查看主题详情、发布帖子、编辑主题、发表评论、回复某条评论（楼中楼）、回答提问、删除主题；通过 api call 查看主题评论列表、设置精华、设置标签、查看自己提的问题与已回答记录。当用户需要查找内容、发帖、编辑主题、评论、回复评论、回答问题、删除主题、查看主题评论、查看自己的提问记录、或管理主题精华和标签时使用。
Eurosys
franklee16/academic-research-skills
A skill your agent uses when targeting EuroSys (EuroSys) or deciding whether a computer-science manuscript fits this venue.
Pubmed Topic Recommend
aipoch/medical-research-skills
Generate ~5 actionable research topic recommendations by querying PubMed E-utilities; use when a user provides a research direction/constraints and needs evidence-backed topic ideas quickly.
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 Topic Selection
What does Eurosys Topic Selection do?
A skill your agent uses when deciding whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS, distributed systems, storage, cloud, virtualization, security, and ML…. Eurosys Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS, distributed systems, storage, cloud, virtualization, security, and ML systems — or routes better to SOSP, OSDI, NSDI, ASPLOS, ATC, FAST, or SoCC, and how the April slot and dual deadlines affect that call.
When should I use Eurosys Topic Selection?
Eurosys Topic Selection fits situations like: deciding whether a systems project belongs at EuroSys — the ACM SIGOPS-Europe flagship spanning OS; distributed systems; routes better to SOSP; how the April slot and dual deadlines affect that call.
How do I install Eurosys Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-topic-selection -a claude-code`. Or copy the skill folder (EuroSys-Skills/skills/eurosys-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/eurosys-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Eurosys Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-topic-selection -a codex`. Or copy the skill folder (EuroSys-Skills/skills/eurosys-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/eurosys-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Eurosys Topic Selection 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-topic-selection -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-topic-selection, .gemini/skills/eurosys-topic-selection, .github/skills/eurosys-topic-selection and .opencode/skills/eurosys-topic-selection in your project.
What does Eurosys Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Eurosys Topic Selection is instructions for the agent only.
Does Eurosys Topic Selection 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 Eurosys Topic Selection 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 Topic Selection use?
Eurosys Topic Selection 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 Topic Selection use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Topic Selection?
Skills that share tags, products or a category with Eurosys Topic Selection: Topics (ZimoLiao/scholaraio, 576 stars), Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Bestblogs Topic (ginobefun/BestBlogs, 4k stars) and Zsxq Topic (itwanger/toBeBetterJavaer, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eurosys Topic Selection?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.