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.
A skill your agent uses when deciding whether a software-engineering project belongs in the ICSE research track or should be routed to FSE, ASE, ISSTA, MSR, ICSME, EMSE/TSE/TOSEM, or an ICSE…
MITAuto-check passed
Install Icse Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-topic-selection .claude/skills/icse-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 "icse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-topic-selection into .claude/skills/icse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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/ICSE-Skills/skills/icse-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 icse-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-topic-selection .agents/skills/icse-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 "icse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-topic-selection into .agents/skills/icse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-topic-selection .cursor/skills/icse-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 "icse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-topic-selection into .cursor/skills/icse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 ICSE-Skills/skills/icse-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 icse-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-topic-selection .gemini/skills/icse-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 "icse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-topic-selection into .gemini/skills/icse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-topic-selection .github/skills/icse-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 "icse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-topic-selection into .github/skills/icse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-topic-selection .opencode/skills/icse-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 "icse-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-topic-selection into .opencode/skills/icse-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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
icse-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 940 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 software-engineering project belongs in the ICSE research track or should be routed to FSE, ASE, ISSTA, MSR, ICSME, EMSE/TSE/TOSEM, or an ICSE…
- Works in 2 steps: Who changes their behavior if this paper… → Would an SE empiricist accept the…
- Deciding whether a software-engineering project belongs in the ICSE research track
- SKILL.md covers The two-question fit test, Contribution shapes ICSE rewards, Routing table and Timing reality for the current…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Icse Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a software-engineering project belongs in the ICSE research track or should be routed to FSE, ASE, ISSTA, MSR, ICSME, EMSE/TSE/TOSEM, or an ICSE co-located track such as NIER, SEIP, SEIS, or Demonstrations, based on contribution type, evidence maturity, and audience.
Its SKILL.md is about 1.9k 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 software-engineering project belongs in the ICSE research track
- Should be routed to FSE
- An ICSE co-located track such as NIER
- Based on contribution type
Example prompts
- “/icse-topic-selection”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Who changes their behavior if this paper is right? If the answer names
- Would an SE empiricist accept the evidence? ICSE's culture demands evidence
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
Icse Topic Selection loads about 1.9k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 940 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). 940 words, ~1,889 tokens.
Download SKILL.mdSave it as
.claude/skills/icse-topic-selection/SKILL.md (or your agent's skills folder).- name
- icse-topic-selection
- description
- Use when deciding whether a software-engineering project belongs in the ICSE research track or should be routed to FSE, ASE, ISSTA, MSR, ICSME, EMSE/TSE/TOSEM, or an ICSE co-located track such as NIER, SEIP, SEIS, or Demonstrations, based on contribution type, evidence maturity, and audience.
ICSE Topic Selection
Decide venue before writing a single section. ICSE — the IEEE/ACM International Conference on Software Engineering — is the flagship of the SE research community, which means its reviewer pool expects a contribution to software engineering knowledge, evaluated against the four posted criteria of the research track: novelty, rigor, relevance, and verifiability/transparency (ICSE 2027 CFP wording, checked 2026-07-08). A technically excellent paper whose lesson is about databases, PL semantics, or pure ML will be respected and then rejected as out of scope.
The two-question fit test
- Who changes their behavior if this paper is right? If the answer names software developers, testers, maintainers, reviewers, build engineers, or SE researchers studying them, ICSE is plausible. If the answer names compiler writers, DB implementers, or ML-architecture designers, route elsewhere.
- Would an SE empiricist accept the evidence? ICSE's culture demands evidence proportional to the claim: real subject programs or projects, credible baselines, a threats-to-validity analysis, and (by the open-science policy) an inspectable artifact. A motivating anecdote plus a toy prototype fails the rigor criterion regardless of the idea's quality.
Contribution shapes ICSE rewards
- Technique + tool + empirical evaluation — the classic shape: a new analysis, testing, repair, or synthesis technique evaluated on real programs against real baselines (e.g., automated program repair, whose founding ICSE 2009 paper later won the ten-year Most Influential Paper award).
- Empirical study — quantitative mining, controlled experiments, or qualitative interview/survey work that changes what the community believes about practice.
- Human-factors / developer-experience study — how practitioners actually use (or refuse) tools, with sound qualitative methodology.
- SE for AI and AI for SE — testing ML systems, LLM-based SE techniques; the fastest-growing lane, and also the one with the fastest-staling related work.
- Methodology, benchmark, or dataset contributions when they unlock a research area rather than repackage existing data.
Routing table
| Signal in your project | Better home | Why |
|---|---|---|
| Idea is promising but evaluation is preliminary | ICSE NIER (4 pages + 1 ref page, requires a "Future Plans" section per the 2027 call) | NIER reviews vision, not completed evidence |
| Contribution is a deployed industrial experience | ICSE SEIP | Reviewed on relevance to practice, not research novelty |
| Contribution is the tool packaging or a reusable dataset | ICSE Demonstrations / Data Showcase | Purpose-built venue with interactive review |
| Societal impact of software is the point | ICSE SEIS | Dedicated reviewer pool |
| Testing/analysis is the core, SE framing thin | ISSTA | Deeper testing expertise, same community |
| Automation of a development task, systems flavor | ASE | Sibling flagship, tool-centric |
| Repository mining is the whole method | MSR | Purpose-built co-located conference |
| Maintenance/evolution focus | ICSME | Scope match |
| Study too long or too nuanced for 10 pages | EMSE, TSE, TOSEM | No page ceiling, journal-first return path to ICSE |
| Already published at TSE/TOSEM/EMSE | ICSE Journal-first (2027 window: journal acceptance between Oct 11, 2025 and Oct 10, 2026) | Presentation slot without re-review; secondary studies excluded |
Timing reality for the current cycle
The ICSE 2027 research-track deadline (abstract June 23, submission June 30, 2026, AoE) has already passed as of 2026-07-08, and the 2027 call posts a single submission cycle — a departure from the two-cycle model ICSE ran in 2025 and 2026. So "just aim for the next ICSE window" now means roughly a year of waiting. That makes routing honesty cheaper than it used to be: FSE, ASE, ISSTA, and the journals all have nearer deadlines, and a journal-first acceptance can still put you on the Dublin stage.
Show full SKILL.md (384 more words)Show less
Evidence-maturity ladder
Fit is necessary but not sufficient; the same idea belongs at different ICSE doors depending on how far the evidence has come. Grade honestly:
| Maturity rung | You have... | Right door now |
|---|---|---|
| Insight | An observation and an argument, no system or study yet | Workshop or NIER; write the "Future Plans" section the NIER call requires |
| Prototype | A working technique, evaluated on examples you chose | NIER, or hold one cycle and build the real evaluation |
| Evidence | Real subjects, credible baselines, statistics, threats analysis, artifact | Research track — the four criteria are all satisfiable |
| Deployment | Adoption data from practice, weaker research novelty | SEIP, whose reviewers weigh practice lessons over novelty |
| Archive-grade depth | More study than 10 pages can hold | TSE/TOSEM/EMSE first, then journal-first back to the ICSE stage |
The costly mismatch is submitting one rung early: research-track reviewers reject prototypes politely ("promising, but..."), and the year lost to a single-cycle calendar is the real price. One rung of patience is usually one rung of acceptance probability.
Anti-patterns that predict rejection
- Venue shopping downward: a paper rejected from a PL or ML venue, resubmitted to ICSE without re-framing for the SE audience. Reviewers detect the foreign citation graph immediately.
- Solution looking for a problem: no evidence any practitioner or researcher has the pain the tool cures — fails the relevance criterion.
- Benchmark-only novelty: a known technique run on a new dataset with no new question answered.
- Scope camouflage: renaming an ML contribution "SE for AI" without any engineering question. Ask: if the model were swapped, would the SE lesson survive?
Reading the room before committing
Two cheap reconnaissance moves sharpen the verdict. First, scan the last two
editions' accepted-paper titles (ICSE program pages, dblp) for your exact
subarea: three or more recent acceptances means a reviewer pool exists;
zero may mean either an opening or a scope mismatch — the exemplars in
resources/exemplars/library.md help tell which. Second, check where the
papers you cite most were published: if your own bibliography is majority
non-SE venues, ICSE reviewers will experience your paper as a visitor, and
the introduction must do extra naturalization work before the fit test
passes.
Decision procedure
[Audience] who acts differently if the claim is true? -> SE actors? yes/no
[Claim type] technique / empirical / human-factors / benchmark / methodology
[Evidence maturity] complete + real subjects? -> full track
promising + partial? -> NIER or workshop
industrial + deployed? -> SEIP
[Deadline math] next ICSE window vs FSE/ASE/ISSTA/journal calendars
[Verdict] ICSE research track / co-located track / sibling venue + one-line reasonRun this before the writing skills; a wrong venue decision wastes every later step.
When the verdict is ICSE, continue with icse-workflow for the calendar and
icse-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
Files
Just SKILL.md in ICSE-Skills/skills/icse-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icse 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 |
|---|---|---|---|---|---|---|
| Icse Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.9k | 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 | |
| Zsxq Topicitwanger/toBeBetterJavaer | 18k | — | ~564 | Automated safety check: Pass | None | |
| Pubmed Topic Recommendaipoch/medical-research-skills | 2k | — | ~1.9k | Automated safety check: Pass | MIT |
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 查看主题评论列表、设置精华、设置标签、查看自己提的问题与已回答记录。当用户需要查找内容、发帖、编辑主题、评论、回复评论、回答问题、删除主题、查看主题评论、查看自己的提问记录、或管理主题精华和标签时使用。
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.
TiXL UI Topic Doc Writer
tixl3d/tixl
Fills in empty embedded help text for TiXL's UI topics by distilling the maintainer's own video explanations into short, user-facing doc entries.
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 Icse Topic Selection
What does Icse Topic Selection do?
A skill your agent uses when deciding whether a software-engineering project belongs in the ICSE research track or should be routed to FSE, ASE, ISSTA, MSR, ICSME, EMSE/TSE/TOSEM, or an ICSE…. Icse Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a software-engineering project belongs in the ICSE research track or should be routed to FSE, ASE, ISSTA, MSR, ICSME, EMSE/TSE/TOSEM, or an ICSE co-located track such as NIER, SEIP, SEIS, or Demonstrations, based on contribution type, evidence maturity, and audience.
When should I use Icse Topic Selection?
Icse Topic Selection fits situations like: deciding whether a software-engineering project belongs in the ICSE research track; should be routed to FSE; an ICSE co-located track such as NIER; based on contribution type.
How do I install Icse Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-topic-selection -a claude-code`. Or copy the skill folder (ICSE-Skills/skills/icse-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icse-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Icse Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-topic-selection -a codex`. Or copy the skill folder (ICSE-Skills/skills/icse-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icse-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Icse 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 icse-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/icse-topic-selection, .gemini/skills/icse-topic-selection, .github/skills/icse-topic-selection and .opencode/skills/icse-topic-selection in your project.
What does Icse Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Icse Topic Selection is instructions for the agent only.
Does Icse 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 Icse 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 Icse Topic Selection use?
Icse 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 Icse Topic Selection use?
About 1.9k tokens (SKILL.md is roughly 7.6k 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 Icse Topic Selection?
Skills that share tags, products or a category with Icse Topic Selection: Topics (ZimoLiao/scholaraio, 577 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 Icse 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.