Configuring Horizon
coollabsio/coolify
A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.
A skill your agent uses when deciding whether a cloud-computing project belongs at ACM SoCC or should be routed to OSDI, NSDI, EuroSys, USENIX ATC, SOSP, or a data venue (SIGMOD/VLDB), leaning on…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-topic-selection .claude/skills/socc-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 "socc-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-topic-selection into .claude/skills/socc-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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/SoCC-Skills/skills/socc-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 socc-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-topic-selection .agents/skills/socc-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 "socc-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-topic-selection into .agents/skills/socc-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-topic-selection .cursor/skills/socc-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 "socc-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-topic-selection into .cursor/skills/socc-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 SoCC-Skills/skills/socc-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 socc-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-topic-selection .gemini/skills/socc-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 "socc-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-topic-selection into .gemini/skills/socc-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-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 socc-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/SoCC-Skills/skills/socc-topic-selection .github/skills/socc-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 "socc-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-topic-selection into .github/skills/socc-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-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 socc-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/SoCC-Skills/skills/socc-topic-selection .opencode/skills/socc-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 "socc-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-topic-selection into .opencode/skills/socc-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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.
socc-topic-selectionA skill your agent uses when deciding whether a cloud-computing project belongs at ACM SoCC or should be routed to OSDI, NSDI, EuroSys, USENIX ATC, SOSP, or a data venue (SIGMOD/VLDB), leaning on…
Socc Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a cloud-computing project belongs at ACM SoCC or should be routed to OSDI, NSDI, EuroSys, USENIX ATC, SOSP, or a data venue (SIGMOD/VLDB), leaning on SoCC's unique joint SIGMOD+SIGOPS identity, its welcome of measurement and experience papers alongside systems-building, and the model-swap and re-label tests.
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.
It sits in Backend & APIs. 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.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Socc Topic Selection loads about 1.6k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 687 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 687 words, ~1,615 tokens.
.claude/skills/socc-topic-selection/SKILL.md (or your agent's skills folder).Decide the venue before drafting. SoCC — the ACM Symposium on Cloud Computing — is the only conference co-sponsored by SIGMOD and SIGOPS, and that joint sponsorship is its identity: it sits at the systems-and-data intersection of cloud research. Reviewers read for a cloud contribution that matters at scale, and the venue explicitly welcomes not just clean-slate systems but measurement studies, experience papers, and cloud-economics work that a pure OS/networking flagship might treat as second-class. A technically strong paper whose real home is kernel scheduling, network fabric, or query-optimizer internals is respected and then routed elsewhere.
The decisive question is rarely "is this cloud?" but "does this contribution live at the systems-and-data intersection that SoCC owns, or is it a pure-systems or pure-data result better served by a specialized flagship?" SoCC's sweet spot is the paper that a datacenter operator or cloud platform team would act on: storage and data services, resource management and scheduling, serverless, multi-tenancy, big-data and ML-systems infrastructure, edge/fog, and the cost and economics of running all of it.
| Signal in your project | Better home | Why |
|---|---|---|
| Cloud infrastructure at the systems+data intersection: storage/data services, resource mgmt, serverless, ML-systems infra, multi-tenancy, cloud economics | ACM SoCC | The joint SIGMOD+SIGOPS venue; welcomes systems and measurement/experience |
| Core is a novel OS/kernel or a clean-slate distributed-systems mechanism, depth over cloud framing | OSDI / SOSP | OS and systems flagships; deeper systems-novelty bar |
| Core is the network — datacenter fabric, congestion control, RDMA, SDN | NSDI | Networked-systems flagship |
| General systems contribution, European rotation, OS/runtime flavor | EuroSys | Broad systems venue; ACM, different community and calendar |
| Solid systems/experience result that fits a broad practitioner venue | USENIX ATC | General systems + experience; USENIX template and process |
| Core is a database engine, query processing, transactions, or data mgmt theory | SIGMOD / VLDB | Data-management flagships; SoCC shares SIGMOD sponsorship but is systems-facing |
| Pure ML modeling result whose cloud consequence is incidental | an ML venue | The model, not the cloud system, is the contribution |
Two quick tests sharpen a borderline verdict:
Fit is necessary but not sufficient: the same idea sits at different doors depending on how far the evidence has come. A mechanism evaluated only in simulation needs a testbed or deployment before the research track; a measurement study needs a trace or corpus a reviewer can scrutinize; an experience paper needs a system that was actually operated. Submitting a simulation-only systems claim invites the "does this hold on a real deployment?" reject that both sponsoring communities apply.
[Scope] scan the last two SoCC programs (dblp conf/cloud, acmsocc.org) for your subarea
-> 3+ recent papers = a reviewer pool exists; 0 = opening or mismatch
[Citations] is your bibliography a mix of systems (OSDI/NSDI/EuroSys/ATC/SoCC) and data
(SIGMOD/VLDB) venues? -> a SoCC paper usually cites both lanes
[Calendar] SoCC has two rounds/year; compare the nearer round with OSDI/NSDI/EuroSys/ATC and
SIGMOD/VLDB dates -> route to the nearest honest fit, but never reuse a Round-1 reject
in Round 2[Audience] who acts differently if the claim holds? -> cloud operators / platform teams / data-infra builders?
[Claim type] cloud system / measurement / benchmark / experience / cloud-economics
[Intersection check] does it span systems AND data/scale, or is it pure-OS / pure-network / pure-DB?
[Sibling check] kernel depth -> OSDI/SOSP; network fabric -> NSDI; DB engine -> SIGMOD/VLDB
[Verdict] SoCC research track / sibling venue, with a one-line reasonRun this before the writing skills; a wrong venue decision wastes every later step. When the
verdict is SoCC, continue with socc-workflow for the two-round calendar and socc-writing-style
for the paper shape.
© 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
Just SKILL.md in SoCC-Skills/skills/socc-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Socc 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 |
|---|---|---|---|---|---|---|
| Socc Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Configuring Horizoncoollabsio/coolify | 63k | 4 repos | ~898 | Automated safety check: Pass | MIT | |
| Nestjs Best Practicesrolling-scopes/rsschool-app | 10k | 6 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Sub2API AdminWei-Shaw/sub2api | 44k | 1 repos | ~717 | Automated safety check: Pass | LGPL-3.0 | |
| Firecrawl Build Onboardingfirecrawl/firecrawl | 190k | 1 repos | ~1.4k | Automated safety check: Notes | ISC | |
| Obsidian BasesAtmosphere/atmosphere | 3.8k | 22 repos | ~3.2k | Automated safety check: Pass | Apache-2.0 |
coollabsio/coolify
A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.
rolling-scopes/rsschool-app
NestJS best practices and architecture patterns for building production-ready applications.
Wei-Shaw/sub2api
Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.
firecrawl/firecrawl
Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.
Atmosphere/atmosphere
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries.
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
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…
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…
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…
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…
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…
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…
Categories
A skill your agent uses when deciding whether a cloud-computing project belongs at ACM SoCC or should be routed to OSDI, NSDI, EuroSys, USENIX ATC, SOSP, or a data venue (SIGMOD/VLDB), leaning on…. Socc Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a cloud-computing project belongs at ACM SoCC or should be routed to OSDI, NSDI, EuroSys, USENIX ATC, SOSP, or a data venue (SIGMOD/VLDB), leaning on SoCC's unique joint SIGMOD+SIGOPS identity, its welcome of measurement and experience papers alongside systems-building, and the model-swap and re-label tests.
Socc Topic Selection fits situations like: deciding whether a cloud-computing project belongs at ACM SoCC; should be routed to OSDI; A data venue (SIGMOD/VLDB); leaning on SoCCs unique joint SIGMOD+SIGOPS identity.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-topic-selection -a claude-code`. Or copy the skill folder (SoCC-Skills/skills/socc-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/socc-topic-selection in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-topic-selection -a codex`. Or copy the skill folder (SoCC-Skills/skills/socc-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/socc-topic-selection in your project. Codex loads it when a task matches its description.
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 socc-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/socc-topic-selection, .gemini/skills/socc-topic-selection, .github/skills/socc-topic-selection and .opencode/skills/socc-topic-selection in your project.
SKILL.md names no scripts, command-line tools or credentials: Socc Topic Selection is instructions for the agent only.
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.
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.
Socc 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.
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Socc Topic Selection: Configuring Horizon (coollabsio/coolify, 63k stars), Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Sub2API Admin (Wei-Shaw/sub2api, 44k stars) and Firecrawl Build Onboarding (firecrawl/firecrawl, 190k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.