Iso27001 Audit Prep
alirezarezvani/claude-skills
/cs:iso27001-audit-prep <scope — ISO 27001 ISMS audit readiness 6-question forcing interrogation.
A skill your agent uses when auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines, single-column = 11pt format with no hard page limit, the…
MITAuto-check passed
Install Itcs Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-submission .claude/skills/itcs-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 "itcs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-submission into .claude/skills/itcs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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/ITCS-Skills/skills/itcs-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 itcs-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-submission .agents/skills/itcs-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 "itcs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-submission into .agents/skills/itcs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-submission .cursor/skills/itcs-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 "itcs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-submission into .cursor/skills/itcs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 ITCS-Skills/skills/itcs-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 itcs-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-submission .gemini/skills/itcs-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 "itcs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-submission into .gemini/skills/itcs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-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 itcs-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/ITCS-Skills/skills/itcs-submission .github/skills/itcs-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 "itcs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-submission into .github/skills/itcs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-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 itcs-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/ITCS-Skills/skills/itcs-submission .opencode/skills/itcs-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 "itcs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-submission into .opencode/skills/itcs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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
itcs-submission- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 703 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines, single-column = 11pt format with no hard page limit, the…
- Works in 7 steps: Freeze the model and definitions early;… → Register… → Run the proof-completeness pass: every… → …
- Auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines
- SKILL.md covers The two-step deadline, Format and page policy, Lightweight double-blind sweep and Prior-publication and…, plus 4 more sections
- Calls pdftotext
What it does
Itcs Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines, single-column = 11pt format with no hard page limit, the first-10-pages merits window, complete proofs of all central claims, the lightweight double-blind sweep, and the archival-prior-publication check.
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 an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines
- Single-column = 11pt format with no hard page limit
- The first-10-pages merits window
- Complete proofs of all central claims
Example prompts
- “/itcs-submission”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Freeze the model and definitions early; proofs can be polished, the framing cannot churn.
- Register title/abstract/authors/conflicts before the earlier registration cutoff.
- Run the proof-completeness pass: every central claim fully proved in the PDF.
- Run the mechanical anonymity checks on the final PDF (metadata + self-reference).
- Post the full version to arXiv/ECCC/ePrint if desired (allowed); keep the submission blinded.
- Fill every HotCRP field — topics, conflicts for every coauthor's institution and recent
- Re-download the uploaded PDF and read the first 10 pages cold to confirm the idea lands.
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
Itcs Submission loads about 1.7k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 703 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). 703 words, ~1,674 tokens.
Download SKILL.mdSave it as
.claude/skills/itcs-submission/SKILL.md (or your agent's skills folder).- name
- itcs-submission
- description
- Use when auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines, single-column >= 11pt format with no hard page limit, the first-10-pages merits window, complete proofs of all central claims, the lightweight double-blind sweep, and the archival-prior-publication check.
ITCS Submission
Run this audit before uploading to the ITCS HotCRP site. ITCS papers publish open access in
LIPIcs and are reviewed lightweight double-blind with no rebuttal, so the submitted PDF has
to be complete, self-defending, and correctly anonymized on the first and only try. Every rule
below was read from the ITCS 2026/2025 calls on 2026-07-09 via search renderings of the
itcs2026.hotcrp.com and itcs-conf.org URLs (see
../../resources/official-source-map.md); treat them as
a one-cycle snapshot and reopen the live call first.
The two-step deadline
ITCS separates the abstract/registration from the full-paper submission, and the abstract cutoff is earlier:
- Abstract / registration locks title, abstract, authors, and conflicts (ITCS 2026: 4 September 2025, 7:59:59 PM EDT). The abstract drives PC bidding — register the real title and abstract, not a placeholder.
- Full-paper submission uploads the anonymized PDF with complete proofs (ITCS 2026: 6 September 2025, 7:59:59 PM EDT). Miss the registration and no submission slot exists.
Format and page policy
- Single column, font size at least 11 point. Beyond that, the submission call imposes no
hard formatting template and no hard page limit (the LIPIcs
lipics-v2021class is a camera-ready requirement, not a submission one — seeitcs-camera-ready). - First-10-pages merits window. It is strongly recommended that the first ~10 pages give a
clear presentation of the paper's merits, significance, innovations, and place in the
literature. Reviewers judge the idea from this window; do not bury it (see
itcs-writing-style). - Complete proofs of all central claims must be included, in an appendix if needed. "Proof
omitted" or "see the full version" for a load-bearing claim is a substantive defect, not a
formatting one (see
itcs-supplementary).
Lightweight double-blind sweep
ITCS anonymity is lightweight: hide the authors in the PDF, but keep the references honest and allow a public full version. The leak surface is narrower than an empirical venue's (no code, no data), but real:
# Mechanical pass on the submission PDF
pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # scrub metadata identity
pdftotext paper.pdf - | grep -nEi 'thank|acknowledg|grant|supported by|our (previous|prior|earlier) (work|paper)' | head
pdftotext paper.pdf - | grep -nEi '\\bwe (previously|earlier) (showed|proved)\\b' | head- Remove author names, affiliations, emails, and acknowledgements/funding lines from the PDF.
- Neutralize first-person self-reference: rewrite "in our prior work [12]" as a third-person
"[Author, YEAR] showed." Do not anonymize or remove the reference itself — the reference
list stays intact (see
itcs-related-work). - A public arXiv/ECCC/ePrint full version is allowed and encouraged; you need not delay it for anonymity. Just keep the submitted PDF blinded.
Prior-publication and dual-submission check
- The result must not be published, presented, or under submission at another archival conference. Papers accepted to ITCS should not then go to another archival conference.
- Simultaneous submission to a journal is allowed — a distinctive ITCS latitude; a journal version in parallel is fine.
- Confirm the exact current wording each cycle; the archival/non-archival boundary and any workshop carve-outs are cycle-volatile.
Show full SKILL.md (269 more words)Show less
Desk-risk triage
| Finding at audit time | Severity | Real fix |
|---|---|---|
| Central claim lacks a complete proof | Substantive reject-grade | Add the full proof (appendix); do not defer to the preprint |
| Merits not legible within ~10 pages | High | Restructure so model+motivation+results come first |
| Author identity in PDF metadata/acknowledgements | Anonymity violation | Scrub metadata; remove acknowledgements/funding |
| First-person self-citation ("our prior [12]") | Anonymity leak | Rewrite in third person; keep the reference |
| References anonymized/removed | Breaks the lightweight rule; reads evasive | Restore normal citations |
| Abstract/authors not registered by the earlier cutoff | No submission slot | Nothing fixes this post-deadline — calendar it now |
| Result already at another archival venue | Dual-submission violation | Withdraw or reroute; journal parallel is OK |
| Font < 11pt or multi-column | Formatting non-compliance | Recompile single-column, >= 11pt |
Final-week order of operations
- Freeze the model and definitions early; proofs can be polished, the framing cannot churn.
- Register title/abstract/authors/conflicts before the earlier registration cutoff.
- Run the proof-completeness pass: every central claim fully proved in the PDF.
- Run the mechanical anonymity checks on the final PDF (metadata + self-reference).
- Post the full version to arXiv/ECCC/ePrint if desired (allowed); keep the submission blinded.
- Fill every HotCRP field — topics, conflicts for every coauthor's institution and recent collaborators — a day early; late conflicts are the classic midnight failure.
- Re-download the uploaded PDF and read the first 10 pages cold to confirm the idea lands.
Reverify each cycle
- The two cutoff dates and their timezone (EDT/AoE).
- Whether the current call still runs no rebuttal and lightweight double-blind.
- The exact prior-publication/dual-submission wording and any generative-AI-disclosure rule.
- That there is still no hard page limit and the 11pt/single-column format holds.
Output format
[ITCS submission status] ready / blocked / needs work
[Registration] title/abstract/authors/conflicts locked by the earlier deadline? yes/no
[Format] single-column, >= 11pt? merits legible within ~10 pages? yes/no
[Proofs] every central claim fully proved IN the PDF (not only the preprint)? yes/no
[Anonymity] metadata clean, self-cites neutralized, references intact? yes/no
[Prior publication] not at another archival venue (journal parallel OK)? yes/no
[Fix queue] <ordered, with owners and dates before the early-September cutoff>© 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 ITCS-Skills/skills/itcs-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Itcs 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 |
|---|---|---|---|---|---|---|
| Itcs Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Iso27001 Audit Prepalirezarezvani/claude-skills | 28k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Production Auditaffaan-m/ECC | 276k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Aims Auditalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| OmniRoute Audit and Policy CLIdiegosouzapw/OmniRoute | 75k | — | ~733 | Automated safety check: Pass | MIT | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | 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.
Aims Audit
alirezarezvani/claude-skills
/cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.
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.
Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
Qms Audit Expert
davila7/claude-code-templates
Senior QMS Audit Expert for internal and external quality management system auditing.
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 Itcs Submission
What does Itcs Submission do?
A skill your agent uses when auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines, single-column = 11pt format with no hard page limit, the…. Itcs Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines, single-column = 11pt format with no hard page limit, the first-10-pages merits window, complete proofs of all central claims, the lightweight double-blind sweep, and the archival-prior-publication check.
When should I use Itcs Submission?
Itcs Submission fits situations like: auditing an ITCS submission for HotCRP readiness — the early-September abstract-then-paper deadlines; single-column = 11pt format with no hard page limit; the first-10-pages merits window; complete proofs of all central claims.
How do I install Itcs Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-submission -a claude-code`. Or copy the skill folder (ITCS-Skills/skills/itcs-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/itcs-submission in your project. Claude Code loads it when a task matches its description.
How do I install Itcs Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-submission -a codex`. Or copy the skill folder (ITCS-Skills/skills/itcs-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/itcs-submission in your project. Codex loads it when a task matches its description.
Can I use Itcs 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 itcs-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/itcs-submission, .gemini/skills/itcs-submission, .github/skills/itcs-submission and .opencode/skills/itcs-submission in your project.
What does Itcs Submission need to run?
Going by SKILL.md and its folder, Itcs Submission needs the command-line tools its instructions call (pdftotext).
Does Itcs 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 Itcs 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 Itcs Submission use?
Itcs 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 Itcs Submission use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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 Itcs Submission?
Skills that share tags, products or a category with Itcs Submission: Iso27001 Audit Prep (alirezarezvani/claude-skills, 28k stars), Production Audit (affaan-m/ECC, 276k stars), Aims Audit (alirezarezvani/claude-skills, 28k stars) and OmniRoute Audit and Policy CLI (diegosouzapw/OmniRoute, 75k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Itcs 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.