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.
A skill your agent uses when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the…
MITAuto-check passed
Install Micro Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-submission .claude/skills/micro-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 "micro-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-submission into .claude/skills/micro-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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/MICRO-Skills/skills/micro-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 micro-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-submission .agents/skills/micro-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 "micro-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-submission into .agents/skills/micro-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 micro-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-submission .cursor/skills/micro-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 "micro-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-submission into .cursor/skills/micro-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 MICRO-Skills/skills/micro-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 micro-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-submission .gemini/skills/micro-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 "micro-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-submission into .gemini/skills/micro-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 micro-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 micro-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/MICRO-Skills/skills/micro-submission .github/skills/micro-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 "micro-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-submission into .github/skills/micro-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 micro-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 micro-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/MICRO-Skills/skills/micro-submission .opencode/skills/micro-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 "micro-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-submission into .opencode/skills/micro-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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
micro-submission- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 801 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 MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the…
- Works in 3 steps: Deadlines run on US Eastern time. MICRO… → The abstract deadline is a registration… → No appendix. At all. The 2026 guidelines…
- Auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed
- SKILL.md covers Three traps that are…, Format gate table (2026…, Anonymity, MICRO flavor and Mechanical pre-flight, plus 5 more sections
- Calls pdftotext
What it does
Micro Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the abstract-registration gate a week before the paper, minimum 9pt fonts, mandatory page numbers, all-author reference entries, and MICRO's visual-plus-automated format inspection.
Its SKILL.md is about 1.8k 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 MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed
- EDT (not AoE) deadline arithmetic
- The abstract-registration gate a week before the paper
- Minimum 9pt fonts
Example prompts
- “/micro-submission”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Deadlines run on US Eastern time. MICRO 2026 closed abstracts on March 31 and
- The abstract deadline is a registration gate, one week early. No abstract in
- No appendix. At all. The 2026 guidelines allow at most 11 pages of content
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
Micro Submission loads about 1.8k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 801 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). 801 words, ~1,761 tokens.
Download SKILL.mdSave it as
.claude/skills/micro-submission/SKILL.md (or your agent's skills folder).- name
- micro-submission
- description
- Use when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the abstract-registration gate a week before the paper, minimum 9pt fonts, mandatory page numbers, all-author reference entries, and MICRO's visual-plus-automated format inspection.
MICRO Submission
Run this audit against the exact PDF headed to HotCRP. Anchors below are the MICRO
2026 (59th) cycle — CFP and submission guidelines at microarch.org/micro59/submit/,
checked 2026-07-08. Every number is a snapshot; reopen the current cycle's pages.
Three traps that are specifically MICRO's
- Deadlines run on US Eastern time. MICRO 2026 closed abstracts on March 31 and papers on April 7, each at 11:59 PM EDT. Authors trained on AoE venues lose up to a working day by assuming AoE. Convert to every co-author's timezone in writing during deadline week.
- The abstract deadline is a registration gate, one week early. No abstract in HotCRP by the first date means no paper submission at all. Register placeholders for every plausible paper; withdrawing is free, adding late is impossible.
- No appendix. At all. The 2026 guidelines allow at most 11 pages of content
plus unlimited references — and explicitly permit no appendix. Anything you
planned to park after the references must be cut, absorbed into the 11 pages, or
moved to an anonymized artifact repository (see
micro-supplementary).
Format gate table (2026 guidelines)
| Rule | 2026 setting | Enforcement |
|---|---|---|
| Content length | ≤ 11 pages, everything except references | Inspected; overlength rejected |
| References | Unlimited pages | Must name all authors — no "et al." per entry |
| Appendix | Forbidden | No parking space exists |
| Fonts | Minimum 9pt everywhere, figures included | Checked visually, not just by tool |
| Page numbers | Required on the submission | Unusual — most venues strip them |
| Template | MICRO 2026 LaTeX template strongly encouraged | Geometry edits and \vspace squeezing barred |
| Inspection | Visual and automated | Passing the HotCRP format checker is not clearance |
The last row deserves emphasis: the guidelines state submissions can be rejected for format violations even if the HotCRP check passed. Treat the checker as a smoke test, then eyeball a printed copy — tiny axis labels on plots are the classic kill.
Anonymity, MICRO flavor
- Double-blind review, maintained through the rebuttal/revision window.
- Artifact links (e.g., a GitHub repository) must be fully anonymized, or removed if they cannot be — the 2026 guidelines say both halves explicitly.
- No acknowledgments section in the submission: no people, no funding agencies.
- Self-citations in third person; scrub PDF metadata, embedded paths, and simulator config files inside any linked artifact that carry usernames or lab hostnames.
Mechanical pre-flight
# page count and font floor
pdfinfo paper.pdf | grep Pages
pdffonts paper.pdf | awk 'NR>2 {print $1}' | sort -u # spot rasterized/tiny fonts manually
# page numbers present? (render page 2 footer and look)
pdftotext -f 2 -l 2 paper.pdf - | tail -3
# reference hygiene: no "et al." allowed inside entries
grep -n "et al" references.bib && echo "FIX: expand all author lists"
# identity leakage
pdftotext paper.pdf - | grep -inE "(our (prior|previous) work|anonymous|acknowledg)"
exiftool paper.pdf | grep -iE "author|creator"HotCRP sequencing for deadline week
- T-8 days (abstract deadline): register title, abstract, authors, topics, conflicts. Topic checkboxes drive reviewer assignment — pick for the mechanism, not the application domain.
- T-3: freeze the evaluation; regenerate all figures from the run archive so the artifact and the PDF cannot disagree later at AE time.
- T-1: full format pass (table above) on the final PDF; print pages with the densest figures and check 9pt compliance by eye.
- T-0, hours early in EDT terms: upload, confirm HotCRP shows the final PDF (re-download it and diff checksums), and have a second author log in independently to verify the submission state.
Show full SKILL.md (319 more words)Show less
What the abstract registration should actually contain
The T-8 abstract is not a formality — reviewers bid on it and topic-matching runs from it. Three failure modes to avoid at the registration gate:
- Placeholder prose ("we study caches") attracts mismatched bidders whose eventual reviews read the paper against the wrong literature.
- Overclaiming the final numbers before the sweep finishes — the PDF must deliver the abstract's promise, and the HotCRP abstract should be updated to match the final PDF before the paper deadline.
- Wrong topic checkboxes. Pick the mechanism area (memory hierarchy, branch prediction, accelerators, security) over the application domain (ML, graphs) — the mechanism community is who you want reviewing.
Conflicts deserve the same care at registration: advisors, recent co-authors, and institutional conflicts declared per the form's definitions. A conflict discovered after assignment is an integrity incident, not a paperwork fix.
Also decide: main track or Industry Track
MICRO 2026 opened an inaugural Industry Track with its own CFP and a review
process tailored to production constraints (micro59/submit/industrial.php). If the
paper's value is deployment evidence rather than a new general mechanism, route it
there deliberately — do not let a production paper be judged by main-track novelty
rules. Track-specific deadlines and rules: 待核实 against the live page.
If something goes wrong at the wire
- HotCRP shows "draft" at T-minus-minutes: an unfinished required field is the usual cause — the form, not the PDF. Fill, save, re-check the state label.
- The format checker rejects a compliant PDF: rebuild with the untouched template class file; embedded Type-3 fonts from a figure pipeline are the common trigger. Do not "fix" it by altering template geometry.
- A co-author spots an identity leak post-deadline: do not silently update anything; email the program chairs immediately — self-reporting a leak is survivable, discovery is not.
- Missed the abstract gate entirely: there is no paper this cycle. Move
straight to the lattice in
micro-workflowand book the next venue's window.
Output format
[Upload verdict] go / no-go (blocking items listed)
[Clock] deadline in EDT: <local equivalents per author>
[Abstract gate] registered by T-7: yes / no
[Pages] content: N/11 · references: N (unlimited) · appendix present: must be "no"
[Format] 9pt floor / page numbers / template intact / no vspace hacks: pass-fail each
[References] entries with "et al.": N (must be 0)
[Anonymity] artifact links anonymized-or-removed / metadata clean / no acks: pass-fail
[Track] main / industry — one-line justification© 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 MICRO-Skills/skills/micro-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Micro 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 |
|---|---|---|---|---|---|---|
| Micro Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | 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 | |
| Geo Auditsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Notes | 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
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.
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 Micro Submission
What does Micro Submission do?
A skill your agent uses when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the…. Micro Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the abstract-registration gate a week before the paper, minimum 9pt fonts, mandatory page numbers, all-author reference entries, and MICRO's visual-plus-automated format inspection.
When should I use Micro Submission?
Micro Submission fits situations like: auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed; EDT (not AoE) deadline arithmetic; the abstract-registration gate a week before the paper; minimum 9pt fonts.
How do I install Micro Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-submission -a claude-code`. Or copy the skill folder (MICRO-Skills/skills/micro-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/micro-submission in your project. Claude Code loads it when a task matches its description.
How do I install Micro Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-submission -a codex`. Or copy the skill folder (MICRO-Skills/skills/micro-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/micro-submission in your project. Codex loads it when a task matches its description.
Can I use Micro 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 micro-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/micro-submission, .gemini/skills/micro-submission, .github/skills/micro-submission and .opencode/skills/micro-submission in your project.
What does Micro Submission need to run?
Going by SKILL.md and its folder, Micro Submission needs the command-line tools its instructions call (pdftotext).
Does Micro 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 Micro 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 Micro Submission use?
Micro 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 Micro Submission use?
About 1.8k tokens (SKILL.md is roughly 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 Micro Submission?
Skills that share tags, products or a category with Micro Submission: Production Audit (affaan-m/ECC, 276k stars), Aims Audit (alirezarezvani/claude-skills, 28k stars), Geo Audit (sickn33/agentic-awesome-skills, 47k 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 Micro 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.