Table Fit
asgeirtj/system_prompts_leaks
Keep a Markdown table readable in a narrow terminal of about 100 display columns - a wide table or one carrying prose in its cells wraps into unreadable ragged rows.
A skill your agent uses when deciding whether a systems project fits OSDI, choosing between its Research and Operational Systems tracks, or routing the work to SOSP, NSDI, FAST, EuroSys, or the…
MITAuto-check passed
Install Osdi Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-topic-selection .claude/skills/osdi-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 "osdi-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-topic-selection into .claude/skills/osdi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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/OSDI-Skills/skills/osdi-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 osdi-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-topic-selection .agents/skills/osdi-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 "osdi-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-topic-selection into .agents/skills/osdi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 osdi-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-topic-selection .cursor/skills/osdi-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 "osdi-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-topic-selection into .cursor/skills/osdi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 OSDI-Skills/skills/osdi-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 osdi-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-topic-selection .gemini/skills/osdi-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 "osdi-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-topic-selection into .gemini/skills/osdi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 osdi-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 osdi-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/OSDI-Skills/skills/osdi-topic-selection .github/skills/osdi-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 "osdi-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-topic-selection into .github/skills/osdi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 osdi-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 osdi-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/OSDI-Skills/skills/osdi-topic-selection .opencode/skills/osdi-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 "osdi-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-topic-selection into .opencode/skills/osdi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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
osdi-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 734 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 fits OSDI, choosing between its Research and Operational Systems tracks, or routing the work to SOSP, NSDI, FAST, EuroSys, or the…
- Works in 3 steps: Does the system exist? Not a simulator… → Has it been measured against something… → Is there an idea that survives the…
- Deciding whether a systems project fits OSDI
- SKILL.md covers The built-and-measured test, Is it in scope?, Two tracks, one deadline and Routing against the sibling…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Osdi Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a systems project fits OSDI, choosing between its Research and Operational Systems tracks, or routing the work to SOSP, NSDI, FAST, EuroSys, or the post-USENIX ATC instead — applying the built-and-measured test before a December deadline is spent on a misfit.
Its SKILL.md is about 1.6k 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 fits OSDI
- Choosing between its Research and Operational Systems tracks
- Routing the work to SOSP
- The post-USENIX ATC instead — applying the built-and-measured test before a December deadline is spent on a misfit
Example prompts
- “/osdi-topic-selection”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Does the system exist? Not a simulator of the idea — the artifact itself,
- Has it been measured against something that fights back? A mature baseline, a
- Is there an idea that survives the implementation? Name the abstraction,
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
Osdi Topic Selection loads about 1.6k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 734 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). 734 words, ~1,596 tokens.
Download SKILL.mdSave it as
.claude/skills/osdi-topic-selection/SKILL.md (or your agent's skills folder).- name
- osdi-topic-selection
- description
- Use when deciding whether a systems project fits OSDI, choosing between its Research and Operational Systems tracks, or routing the work to SOSP, NSDI, FAST, EuroSys, or the post-USENIX ATC instead — applying the built-and-measured test before a December deadline is spent on a misfit.
OSDI Topic Selection
Decide venue months before writing, not days. Everything below reflects the OSDI '26
pages as read on 2026-07-08; the scope paragraph and track structure are re-issued in
every CFP, so reopen usenix.org/conference/osdi<yy>/call-for-papers before committing
a project to the December deadline.
The built-and-measured test
OSDI's identity is in its name: design and implementation. Before anything else, answer three questions honestly:
- Does the system exist? Not a simulator of the idea — the artifact itself, runnable under load. A design argued only from simulation or analysis is fighting the venue's instincts.
- Has it been measured against something that fights back? A mature baseline, a production-derived workload, a deployment. Microbenchmarks alone signal a workshop paper.
- Is there an idea that survives the implementation? Name the abstraction, mechanism, or principle a different team could reuse. If the honest answer is "we engineered X to be faster," the contribution is engineering, and OSDI reviewers will say so.
Failing question 1 or 2 does not kill the project — it re-times it. Both OS flagships now run annually (OSDI since 2021, SOSP since 2024), so waiting one build cycle costs months, not the two years it cost under the old alternation.
Is it in scope?
The OSDI '26 CFP takes a deliberately broad view of "systems": operating systems, file and storage systems, distributed systems, cloud computing, mobile systems, secure and reliable systems, systems aspects of big data, machine-learning systems, embedded systems, virtualization, networking as it relates to operating systems, and management and troubleshooting of complex systems. Two practical readings:
- ML-systems work is squarely welcome as systems work — scheduling, serving,
memory, parallelism — not as model-accuracy work (see TensorFlow and Orca in
../../resources/exemplars/library.md). - "Networking as it relates to operating systems" is the OSDI/NSDI border in one phrase: if the network is the object of study, it is NSDI's; if the host stack is, it can be OSDI's.
Two tracks, one deadline
OSDI '26 reviewed two tracks side by side, registered and submitted on the same December dates:
| Track | The paper it wants | Choose it when |
|---|---|---|
| Research | New design + implementation + evaluation | The idea is the contribution and you built it to prove it |
| Operational Systems | Design, implementation, analysis, and experience of a deployed system | The system has run in production and the lessons are the contribution |
The Operational Systems track changes the evidence bar, not the quality bar: deployment scale, incident history, and longitudinal behavior substitute for head-to-head novelty. Do not put a research prototype in the operational track to dodge a novelty fight — experience is exactly what it cannot show.
Show full SKILL.md (308 more words)Show less
Routing against the sibling venues
Decision sketch (verify each venue's live CFP before acting):
built OS/storage/distributed system, idea-led -> OSDI (Research)
same, but the story is production experience -> OSDI (Operational Systems)
same community, ACM cadence fits better -> SOSP (annual since 2024)
network is the object (protocols, fabrics) -> NSDI
persistence/storage stack is the whole story -> FAST
strong systems work, flagship bar uncertain -> EuroSys / ACM SIGOPS ATC
(USENIX ATC ended after ATC '25)
position paper, no artifact yet -> HotOS-style workshop firstTwo cadence facts matter for routing. First, OSDI sits mid-year (OSDI '26: July 13–15, Seattle) with a December submission — a December miss can retarget to SOSP or NSDI within months. Second, USENIX ATC no longer exists as a USENIX venue; its successor is stewarded by ACM SIGOPS, so pre-2026 advice that treats ATC as OSDI's co-located little sibling is stale.
Timing snapshot for the routing decision
Anchor the decision to real dates, then re-verify them live:
- OSDI '26 (20th): July 13–15, 2026, Seattle; its submission gates were December 4/11, 2025 — already history for new work.
- OSDI '27 (21st): official page exists; secondary sources report July 7–9,
2027, Baltimore, and by historical pattern its deadline lands around December
2026 — but the '27 CFP was unreadable at 2026-07-08, so both the deadline and any
policy carry-over (tracks, page budget, no-response process) are 待核实 until
usenix.org/conference/osdi27publishes them. - A project deciding venue in mid-2026 is therefore really choosing between an expected December OSDI '27 deadline and whatever SOSP/NSDI gates fall earlier — pull all three live pages before promising the team a date.
Signals you are about to misfire
- The evaluation section would be all microbenchmarks — no end-to-end workload exists
yet. (Wait a cycle; see
osdi-experiments.) - The paper's strongest sentence is about the model, not the system — route to an ML venue, or reframe until the systems claim stands alone.
- The design is real but unbuilt — OSDI reviewers read "we expect" as "we have not."
- The contribution is a measurement study of others' systems with no design lesson — possible at OSDI, but the bar is a lesson that changes how people build, not a benchmark report.
- You cannot fit the idea into 12 reviewed pages without appendices — OSDI '26 allowed none at submission, so a proof-heavy contribution may belong at a venue that reviews supplements.
Output format
[OSDI fit] strong / plausible / misfit (one-line reason)
[Built-and-measured] artifact exists? measured against a real opponent? idea survives?
[Track] Research / Operational Systems (why)
[Scope lane] which CFP topic phrase this sits under
[Re-route] best alternative venue + next live deadline to check
[Cycle math] months lost if we wait one build cycle vs risk of submitting now© 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 OSDI-Skills/skills/osdi-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Osdi 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 |
|---|---|---|---|---|---|---|
| Osdi Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Table Fitasgeirtj/system_prompts_leaks | 69k | — | ~772 | Automated safety check: Pass | CC0-1.0 | |
| Furniture Fit Checkpascalorg/editor | 25k | — | ~5.1k | Automated safety check: Pass | MIT | |
| TopicsZimoLiao/scholaraio | 577 | — | ~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 |
Similar skills
Furniture Fit Check
pascalorg/editor
Checks whether a sofa, table, bed or appliance fits in a measured Pascal room and reports only what the evidence supports, or asks for the missing measurements.
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.
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.
Fitness Program
revfactory/harness-100
A full pipeline where an agent team collaborates to generate everything from goal-based fitness program design to progress tracking templates.
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 Osdi Topic Selection
What does Osdi Topic Selection do?
A skill your agent uses when deciding whether a systems project fits OSDI, choosing between its Research and Operational Systems tracks, or routing the work to SOSP, NSDI, FAST, EuroSys, or the…. Osdi Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a systems project fits OSDI, choosing between its Research and Operational Systems tracks, or routing the work to SOSP, NSDI, FAST, EuroSys, or the post-USENIX ATC instead — applying the built-and-measured test before a December deadline is spent on a misfit.
When should I use Osdi Topic Selection?
Osdi Topic Selection fits situations like: deciding whether a systems project fits OSDI; choosing between its Research and Operational Systems tracks; routing the work to SOSP; the post-USENIX ATC instead — applying the built-and-measured test before a December deadline is spent on a misfit.
How do I install Osdi Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-topic-selection -a claude-code`. Or copy the skill folder (OSDI-Skills/skills/osdi-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/osdi-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Osdi Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-topic-selection -a codex`. Or copy the skill folder (OSDI-Skills/skills/osdi-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/osdi-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Osdi 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 osdi-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/osdi-topic-selection, .gemini/skills/osdi-topic-selection, .github/skills/osdi-topic-selection and .opencode/skills/osdi-topic-selection in your project.
What does Osdi Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Osdi Topic Selection is instructions for the agent only.
Does Osdi 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 Osdi 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 Osdi Topic Selection use?
Osdi 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 Osdi Topic Selection use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Osdi Topic Selection?
Skills that share tags, products or a category with Osdi Topic Selection: Table Fit (asgeirtj/system_prompts_leaks, 69k stars), Furniture Fit Check (pascalorg/editor, 25k stars), Topics (ZimoLiao/scholaraio, 577 stars) and Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Osdi Topic Selection?
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.