QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
A skill your agent uses when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration…
MITAuto-check passed
Install Micro Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-camera-ready --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-camera-ready .claude/skills/micro-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-camera-ready into .claude/skills/micro-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-camera-ready", 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-camera-readyType 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-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-camera-ready --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-camera-ready .agents/skills/micro-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-camera-ready into .agents/skills/micro-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-camera-ready", 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-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-camera-ready --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-camera-ready .cursor/skills/micro-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-camera-ready into .cursor/skills/micro-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-camera-ready", 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-camera-ready--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-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-camera-ready --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-camera-ready .gemini/skills/micro-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-camera-ready into .gemini/skills/micro-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-camera-ready", 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-camera-readyInstalls 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-camera-ready -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-camera-ready .github/skills/micro-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-camera-ready into .github/skills/micro-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-camera-ready", 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-camera-ready -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-camera-ready --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-camera-ready .opencode/skills/micro-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-camera-ready into .opencode/skills/micro-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-camera-ready", 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-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 717 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration…
- A MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle
- SKILL.md covers The nine-week plan, De-anonymization is an…, Page arithmetic changes and Publication and indexing facts…, plus 4 more sections
- Calls pdftotext
- De-anonymization and acknowledgments restoration
What it does
Micro Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration, keeping the all-author reference rule, integrating rebuttal promises, the optional post-AE artifact appendix, and IEEE/ACM publication logistics.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- A MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle
- De-anonymization and acknowledgments restoration
- Keeping the all-author reference rule
- Integrating rebuttal promises
Example prompts
- “/micro-camera-ready”
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 Camera Ready loads about 1.6k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 717 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). 717 words, ~1,611 tokens.
Download SKILL.mdSave it as
.claude/skills/micro-camera-ready/SKILL.md (or your agent's skills folder).- name
- micro-camera-ready
- description
- Use when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration, keeping the all-author reference rule, integrating rebuttal promises, the optional post-AE artifact appendix, and IEEE/ACM publication logistics.
MICRO Camera-Ready
For the 2026 cycle: notification July 7, camera-ready September 11, 2026 — nine
weeks, with artifact evaluation (see micro-artifact-evaluation) running inside
the same span and the symposium following in Athens, Oct 31 – Nov 4. This skill
turns the acceptance email into a correct published record.
The nine-week plan
| Weeks | Work |
|---|---|
| 1 | Re-read reviews cold; extract every fix promised in the rebuttal into a tracked worklist |
| 2–4 | Execute the worklist: new runs promised, clarified methodology text, corrected figures |
| 3–6 | Artifact evaluation submission and evaluator support (parallel track) |
| 7 | De-anonymization pass + acknowledgments + final reference audit |
| 8 | Publisher formatting, copyright/rights forms, metadata |
| 9 | Buffer; upload early — September 11 is also the AE endgame in recent cycles |
De-anonymization is an additive diff, not a rewrite
Produce the camera-ready as a reviewed diff against the accepted PDF:
- Author block, affiliations, ORCIDs in.
- Acknowledgments restored — people, funding agencies, grant numbers were required to be absent at submission (2026 guidelines), so they are easy to forget permanently. Check the grant-numbers list with every PI.
- Self-citations rewritten from third person where it now reads awkwardly.
- Artifact links swapped from anonymized mirrors to the permanent public home — coordinated with AE badge requirements (archival repository for the Available badge; a GitHub URL alone does not qualify).
- Nothing else moves without a reason traceable to a review or the rebuttal log. Silent post-acceptance content changes are how camera-readies grow claims the PC never reviewed.
# guardrails on the final build
latexdiff accepted.tex camera.tex > diff.tex && pdflatex diff.tex # human-review the delta
grep -n "et al" references.bib && echo "STILL banned at camera-ready: expand authors"
grep -inE "anonym|under review|blind" camera.tex # stale scaffolding
pdftotext camera.pdf - | grep -iE "acknowledg" || echo "MISSING acknowledgments?"Note the second line: MICRO's all-authors-no-"et al." reference rule is a formatting requirement of the venue, not an anonymity artifact — it survives into the final version. New references added at camera-ready must follow it too.
Page arithmetic changes
Camera-ready page allowances (and whether the artifact appendix rides free) are set by the publisher instructions that arrive with acceptance — the 2025 cycle granted a two-page artifact appendix at no charge for papers passing AE; assume the same shape for 2026 but treat exact numbers as 待核实 until the author kit lands. Budget the appendix content early from the AE package README rather than writing it fresh in week 8.
Publication and indexing facts worth knowing
- MICRO proceedings appear in both the ACM Digital Library and IEEE Xplore (the symposium is IEEE/ACM; e.g., the 58th's proceedings are in the ACM DL, the 40th's in Xplore). Your DOI will be the citable anchor — put it in the artifact README when the publisher assigns it.
- AE badges (Available / Functional / Reproducible, per the 2025 AE pages) are printed on the paper and attached as ACM DL metadata — the camera-ready and the AE outcome must land together.
- Attendance/registration obligations for publication (who must register, whether
presentation is in-person-only for Athens): 待核实 on
micro59/attend/— verify before booking nothing or everything.
Show full SKILL.md (270 more words)Show less
Presentation pipeline (the deadline after the deadline)
Athens follows seven weeks after camera-ready. Start the talk while the paper is still warm:
- The talk is the four-beat argument at 4x compression (see
micro-writing-style): one characterization slide, one insight slide, the block diagram, the headline bar chart with the cost line on the same slide. Everything else is backup slides for Q&A. - Q&A at MICRO is methodology Q&A. Prepare backup slides for: baseline config table, sensitivity sweep edges, the worst-regressing workload, and the iso-storage comparison. These four cover most questions actually asked.
- Whether lightning sessions, poster obligations, or speaker-registration deadlines apply for the 2026 program: 待核实 on the program pages when they post — assign an owner to watch for them.
Post-camera-ready checklist
- arXiv posting updated to the final text (respecting the publisher's policy).
- Artifact repository tagged
micro26-camera-ready, badge requirements met. - Talk and poster pipeline started — the Athens slot arrives fast after the September deadline.
- Consider IEEE Micro Top Picks submission when the call opens: it selects from the year's architecture conference papers, and MICRO papers are core candidates.
Metadata that outlives the conference
The camera-ready fixes the paper's permanent search surface — worth ten deliberate minutes:
- Title and abstract as submitted to the publisher become the ACM DL / IEEE Xplore record; typos here are forever.
- Author name forms and ORCIDs consistent with each author's prior record, or the bibliometric graph splits.
- Index terms/keywords chosen for the mechanism community's search habits (structure names, not application buzzwords).
- The artifact DOI and the paper DOI should cross-reference: paper's artifact statement cites the Zenodo DOI; the Zenodo record cites the paper DOI once assigned.
Output format
[Worklist] rebuttal promises: N total, N done, N dropped-with-reason
[Diff audit] camera vs accepted: additive-only confirmed / flagged changes listed
[Restored] authors / acks+grants / self-citations / permanent links: done each
[References] et-al scan clean incl. new entries: yes / no
[AE coupling] badge target · archival deposit done · appendix drafted: status
[Publisher] rights form / metadata / page allowance: done each (待核实 items named)
[Logistics] registration & presentation rules verified on live page: yes / pending© 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-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Micro Camera Ready 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 Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Acceptance Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~943 | Automated safety check: Pass | MIT | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 | |
| Change, Accept or Leave Frameworkkangarooking/cangjie-skill | 11k | — | ~700 | Automated safety check: Pass | MIT | |
| LobeHub Micro App Splitting Guidelobehub/lobehub | 83k | — | ~9.3k | Automated safety check: Pass | Custom licence |
Similar skills
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
Change, Accept or Leave Framework
kangarooking/cangjie-skill
Helps someone stuck ruminating over an unchangeable situation decide whether to change it, accept it, or leave it, drawn from a chapter of Navalism-style writing.
LobeHub Micro App Splitting Guide
lobehub/lobehub
Documents how LobeHub's standalone micro apps are hosted, built and routed differently on Cloud versus self-hosted Docker, so a change does not break one path while fixing the other.
Frost Sequence Camera Orbit
heygen-com/hyperframes
A ready-made HyperFrames video block where an orbiting camera follows an ice logo that shatters, reforms into two text lines and fades, at 1920×1080.
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 Camera Ready
What does Micro Camera Ready do?
A skill your agent uses when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration…. Micro Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration, keeping the all-author reference rule, integrating rebuttal promises, the optional post-AE artifact appendix, and IEEE/ACM publication logistics.
When should I use Micro Camera Ready?
Micro Camera Ready fits situations like: A MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle; de-anonymization and acknowledgments restoration; keeping the all-author reference rule; integrating rebuttal promises.
How do I install Micro Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-camera-ready -a claude-code`. Or copy the skill folder (MICRO-Skills/skills/micro-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/micro-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Micro Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-camera-ready -a codex`. Or copy the skill folder (MICRO-Skills/skills/micro-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/micro-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Micro Camera Ready 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-camera-ready -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-camera-ready, .gemini/skills/micro-camera-ready, .github/skills/micro-camera-ready and .opencode/skills/micro-camera-ready in your project.
What does Micro Camera Ready need to run?
Going by SKILL.md and its folder, Micro Camera Ready needs the command-line tools its instructions call (pdftotext).
Does Micro Camera Ready 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 Camera Ready 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 Camera Ready use?
Micro Camera Ready 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 Camera Ready use?
About 1.6k tokens (SKILL.md is roughly 6.4k 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 Camera Ready?
Skills that share tags, products or a category with Micro Camera Ready: QA Acceptance (paperclipai/paperclip, 99k stars), Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars), Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars) and Change, Accept or Leave Framework (kangarooking/cangjie-skill, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Micro Camera Ready?
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.