Short
sickn33/agentic-awesome-skills
Rewrite the previous response more briefly while preserving the substance.
A skill your agent uses when auditing a SIGIR full or short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside, ACM sigconf anonymization, per-track OpenReview…
MITAuto-check passed
Install Sigir Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-submission --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/SIGIR-Skills/skills/sigir-submission .claude/skills/sigir-submission && 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 "sigir-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-submission into .claude/skills/sigir-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-submission", 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/SIGIR-Skills/skills/sigir-submissionType 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 sigir-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-submission --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/SIGIR-Skills/skills/sigir-submission .agents/skills/sigir-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sigir-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-submission into .agents/skills/sigir-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-submission", 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 sigir-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-submission --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/SIGIR-Skills/skills/sigir-submission .cursor/skills/sigir-submission && 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 "sigir-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-submission into .cursor/skills/sigir-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-submission", 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 SIGIR-Skills/skills/sigir-submission--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 sigir-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-submission --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/SIGIR-Skills/skills/sigir-submission .gemini/skills/sigir-submission && 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 "sigir-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-submission into .gemini/skills/sigir-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-submission", 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 sigir-submissionInstalls 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 sigir-submission -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/SIGIR-Skills/skills/sigir-submission .github/skills/sigir-submission && 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 "sigir-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-submission into .github/skills/sigir-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-submission", 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 sigir-submission -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 sigir-submission --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/SIGIR-Skills/skills/sigir-submission .opencode/skills/sigir-submission && 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 "sigir-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-submission into .opencode/skills/sigir-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-submission", 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
sigir-submission- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 786 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing a SIGIR full or short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside, ACM sigconf anonymization, per-track OpenReview…
- Works in 5 steps: Freeze runs: regenerate every table from… → Re-run the significance script last —… → Compress into the page budget by… → …
- Auditing a SIGIR full
- SKILL.md covers The two-format trap, Anonymization for IR papers…, Policy gates (2026, source:… and Desk-reject triage, plus 4 more sections
- Calls pdftotext
What it does
Sigir Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a SIGIR full or short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside, ACM sigconf anonymization, per-track OpenReview groups, the PC-member nomination duty, cross-track double-submission bans, AI-use disclosure, and desk-reject triage for the ACM SIGIR conference.
Its SKILL.md is about 1.7k 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
- Auditing a SIGIR full
- Short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside
- ACM sigconf anonymization
- Per-track OpenReview groups
Example prompts
- “/sigir-submission”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Freeze runs: regenerate every table from versioned run files (TREC-format
- Re-run the significance script last — copy-pasted p-values from stale runs are a
- Compress into the page budget by demoting per-query analyses to the repository,
- Anonymity sweep: PDF metadata, acknowledgments, repo URL, system name, log
- Upload to the correct track group, complete the AI-disclosure and PC-nomination
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pdftotext
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
Sigir Submission loads about 1.7k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 786 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). 786 words, ~1,721 tokens.
Download SKILL.mdSave it as
.claude/skills/sigir-submission/SKILL.md (or your agent's skills folder).- name
- sigir-submission
- description
- Use when auditing a SIGIR full or short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside, ACM sigconf anonymization, per-track OpenReview groups, the PC-member nomination duty, cross-track double-submission bans, AI-use disclosure, and desk-reject triage for the ACM SIGIR conference.
SIGIR Submission
Run this audit before anything is uploaded to a SIGIR OpenReview group. SIGIR is a multi-track venue where the same manuscript can be legal in one track and desk-rejectable in another, so the audit starts with "which track is this PDF for?" and only then checks format. Reopen the current edition's track page — every number below is a 2026-cycle anchor (verified 2026-07-08, exact deadlines 待核实), not a rule.
The two-format trap
SIGIR's full and short formats are not a long and a short version of the same bar. A 4-page short paper is a complete argument about one focused finding; a 9-page full paper is expected to carry a rounded evidence program (multiple collections, ablations, significance tests, efficiency notes). The most common self-inflicted wound is submitting a compressed full paper as a short paper — reviewers see missing evidence, not admirable focus.
| Check | Full papers | Short papers |
|---|---|---|
| Page budget (2026) | ≤ 9 pages, references excluded | ≤ 4 pages, references excluded |
| Appendices | Count inside the budget (2025 wording: everything except references) | Same — no appendix escape hatch |
| Template | ACM Primary Article Template, LaTeX sigconf / Word Interim | Same |
| Review | Double-blind, fully anonymized | Double-blind, fully anonymized |
| OpenReview group | Main conference group | Separate Short Papers Track group |
| PC duty | One author nominated as PC member per submission | Confirm on the current track page |
The appendix rule is the sharpest edge on this table: unlike NeurIPS-style venues, SIGIR gives you no unlimited appendix after the references. Proofs, prompt listings, extra tables — either they fit in the budget or they move to the cited repository.
Anonymization for IR papers specifically
Generic double-blind advice misses the leaks IR papers actually have:
- The system name. If your ranker is already public under the same name (arXiv, a leaderboard, a plugin for Anserini/PyTerrier), the name itself de-anonymizes. Rename for review or argue from the current policy page that preprints are allowed.
- Leaderboard submissions. MS MARCO / TREC-style leaderboards show team names and dates. Do not cite your own leaderboard row in a way that only the submitting team could.
- Proprietary query logs. "Queries sampled from our commercial search engine's logs in country X" can identify the company. Genericize the description, keep the statistics.
- Self-citations in third person; repository links anonymized (e.g., an anonymous.4open.science mirror); PDF metadata stripped.
Policy gates (2026, source: submission-policies page)
- Parallel submission = desk reject, regardless of how the other venue decides.
- Cross-track double submission inside SIGIR is banned — e.g., the dataset you submit as a Resource paper cannot also be the novel contribution of your full paper. Decide which track owns each contribution before the abstract deadline.
- Generative-AI use must be disclosed; AI tools cannot be authors; SIGIR reserves automated compliance checks. Assume your PDF will be machine-screened.
- ACM authorship policy applies: the author list is expected to be stable and human.
Show full SKILL.md (323 more words)Show less
Desk-reject triage
| Trigger | Severity | Can it be fixed after the deadline? |
|---|---|---|
| Over budget (appendix counted in) | Desk reject | No |
| Wrong track's OpenReview group | Desk reject or forced withdrawal | Usually no |
| Identity leak (name, log, leaderboard) | Desk reject | No |
| Parallel submission discovered | Desk reject at any time | No |
| Same content in two SIGIR tracks | Both at risk | Only by withdrawing one first |
| Missing PC-member nomination | Chair follow-up / submission incomplete | Sometimes, briefly |
| No significance testing on close results | Review-stage damage | Only before the deadline |
Final-week sequence for a retrieval paper
- Freeze runs: regenerate every table from versioned run files (TREC-format
runs/*.trec) so the PDF, repository, and any leaderboard entry agree. - Re-run the significance script last — copy-pasted p-values from stale runs are a classic reviewer catch when the numbers moved.
- Compress into the page budget by demoting per-query analyses to the repository,
not by shrinking floats or tampering with
sigconfspacing. - Anonymity sweep: PDF metadata, acknowledgments, repo URL, system name, log provenance.
- Upload to the correct track group, complete the AI-disclosure and PC-nomination fields, and verify the OpenReview abstract matches the PDF abstract.
# Pre-upload checks that catch the silent killers
pdfinfo paper.pdf | grep -iE "author|creator" # metadata identity leak
grep -inE "acknowledg|our (system|engine|company)" *.tex # textual leaks
grep -c "documentclass\[sigconf" main.tex # right ACM class
pdftotext paper.pdf - | grep -icE "p ?[<=] ?0\.05|t-test|significan" # stats present?Abstract-deadline gotchas
The abstract deadline (a week before the PDF in recent cycles) is a harder gate than teams expect:
- Title, author list, and track are effectively frozen there; ACM authorship policy makes later author changes painful and cross-track moves are usually impossible.
- The abstract text should be the PDF's abstract, not a placeholder — reviewers bid on it, and a bait-and-switch abstract draws mismatched expertise.
- Conflicts-of-interest declarations and the PC-member nominee belong to this stage; chasing a nominee's consent during PDF week is a self-inflicted crisis.
What this audit does not cover
Evidence quality lives in sigir-experiments; page-budget writing strategy in
sigir-writing-style and sigir-supplementary; track choice in
sigir-topic-selection. If the paper is a dataset or a replication, stop here and
re-route: Resources and Reproducibility have different budgets, different anonymity
regimes (Resources is single-anonymous), and different dates.
Output format
[SIGIR readiness] Ready / Needs fixes / Wrong track / Not ready
[Track + group] full / short + OpenReview group id
[Budget check] <pages used>/<budget>, appendix-inside-budget confirmed yes-no
[Anonymity risks] <system name / leaderboard / logs / metadata / links>
[Policy gates] parallel-submission, cross-track, AI-disclosure, PC-nomination status
[Fix order] <ordered blocking fixes>
[Reopen first] <current track page URL to re-verify dates and budgets>© 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 SIGIR-Skills/skills/sigir-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigir Submission 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 |
|---|---|---|---|---|---|---|
| Sigir Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Shortsickn33/agentic-awesome-skills | 47k | 1 repos | ~281 | Automated safety check: Pass | MIT | |
| Production Auditaffaan-m/ECC | 277k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| SEO Auditevery-app/open-seo | 23k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Aims Auditalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Geo Auditsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
Production Audit
affaan-m/ECC
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.
SEO Audit
every-app/open-seo
Audit a website, investigate its real search opportunities, and deliver a short data-backed report on the few changes most likely to grow organic traffic that converts.
Aims Audit
alirezarezvani/claude-skills
/cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.
Geo Audit
sickn33/agentic-awesome-skills
Full website GEO+SEO audit with parallel subagent delegation.
OmniRoute Audit and Policy CLI
diegosouzapw/OmniRoute
Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.
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 Sigir Submission
What does Sigir Submission do?
A skill your agent uses when auditing a SIGIR full or short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside, ACM sigconf anonymization, per-track OpenReview…. Sigir Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a SIGIR full or short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside, ACM sigconf anonymization, per-track OpenReview groups, the PC-member nomination duty, cross-track double-submission bans, AI-use disclosure, and desk-reject triage for the ACM SIGIR conference.
When should I use Sigir Submission?
Sigir Submission fits situations like: auditing a SIGIR full; short paper before the deadline — the 9-page vs 4-page budgets with appendices counted inside; ACM sigconf anonymization; per-track OpenReview groups.
How do I install Sigir Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-submission -a claude-code`. Or copy the skill folder (SIGIR-Skills/skills/sigir-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigir-submission in your project. Claude Code loads it when a task matches its description.
How do I install Sigir Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-submission -a codex`. Or copy the skill folder (SIGIR-Skills/skills/sigir-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigir-submission in your project. Codex loads it when a task matches its description.
Can I use Sigir Submission 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 sigir-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sigir-submission, .gemini/skills/sigir-submission, .github/skills/sigir-submission and .opencode/skills/sigir-submission in your project.
What does Sigir Submission need to run?
Going by SKILL.md and its folder, Sigir Submission needs the command-line tools its instructions call (pdftotext).
Does Sigir Submission 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 Sigir Submission 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 Sigir Submission use?
Sigir Submission 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 Sigir Submission use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 Sigir Submission?
Skills that share tags, products or a category with Sigir Submission: Short (sickn33/agentic-awesome-skills, 47k stars), Production Audit (affaan-m/ECC, 277k stars), SEO Audit (every-app/open-seo, 23k stars) and Aims Audit (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sigir Submission?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.