Convert
remotion-dev/remotion
Start the local @remotion/convert app and open it in the Codex browser.
A skill your agent uses when converting an ASPLOS acceptance or Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization, ACM rights and template…
MITAuto-check passed
Install Asplos Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-camera-ready .claude/skills/asplos-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 "asplos-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-camera-ready into .claude/skills/asplos-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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/ASPLOS-Skills/skills/asplos-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 asplos-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-camera-ready .agents/skills/asplos-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 "asplos-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-camera-ready into .agents/skills/asplos-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 asplos-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-camera-ready .cursor/skills/asplos-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 "asplos-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-camera-ready into .cursor/skills/asplos-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 ASPLOS-Skills/skills/asplos-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 asplos-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-camera-ready .gemini/skills/asplos-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 "asplos-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-camera-ready into .gemini/skills/asplos-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 asplos-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 asplos-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/ASPLOS-Skills/skills/asplos-camera-ready .github/skills/asplos-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 "asplos-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-camera-ready into .github/skills/asplos-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 asplos-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 asplos-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/ASPLOS-Skills/skills/asplos-camera-ready .opencode/skills/asplos-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 "asplos-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-camera-ready into .opencode/skills/asplos-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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
asplos-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 769 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting an ASPLOS acceptance or Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization, ACM rights and template…
- Works in 5 steps: Day 0-2: read the decision letter twice;… → Week 1: rights form; template migration;… → Weeks 2-4: shepherd/letter-required… → …
- Converting an ASPLOS acceptance
- SKILL.md covers Two tracks through the same…, De-anonymization, done as a diff, ACM-specific obligations and Artifact integration, plus 4 more sections
- Calls pdftotext
What it does
Asplos Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an ASPLOS acceptance or Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization, ACM rights and template obligations, the revision change note, artifact-appendix integration and badge placement, and Digital Library metadata checks.
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
- Converting an ASPLOS acceptance
- Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization
- ACM rights and template obligations
- The revision change note
Example prompts
- “/asplos-camera-ready”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Day 0-2: read the decision letter twice; extract every instruction and
- Week 1: rights form; template migration; de-anonymization diff.
- Weeks 2-4: shepherd/letter-required edits; final artifact deposit; appendix
- Week 5: full residue sweep; metadata check; co-author read of the exact PDF.
- Week 6: upload with margin; confirm the system shows the final version;
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
Asplos Camera Ready loads about 1.7k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 769 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). 769 words, ~1,667 tokens.
Download SKILL.mdSave it as
.claude/skills/asplos-camera-ready/SKILL.md (or your agent's skills folder).- name
- asplos-camera-ready
- description
- Use when converting an ASPLOS acceptance or Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization, ACM rights and template obligations, the revision change note, artifact-appendix integration and badge placement, and Digital Library metadata checks.
ASPLOS Camera-Ready
The camera-ready deadline at ASPLOS 2027 sits roughly six weeks after notification — verified indirectly, via the CFP's statement that Major Revisions are resubmitted "at the camera ready deadline (6 weeks from notification)" (checked 2026-07-08; the exact date and page allowance for camera-ready are 待核实 and arrive with the acceptance email). The window is shared by two very different tasks, so the first step is knowing which track you are on.
Two tracks through the same deadline
| Track | What is due | Judged by |
|---|---|---|
| Accepted paper | Final, de-anonymized, ACM-formatted PDF + forms | Publication staff + shepherd if assigned (shepherding for 2027: 待核实) |
| Major Revision | The revised submission — still a reviewed document | The program committee, as a submission on record |
Do not apply camera-ready instincts to a Major Revision: it stays within submission rules (anonymity unless told otherwise — confirm in the decision letter), and its companion document is a change note keyed to the decision letter, item by item, with pointers to where each required change landed. If this revision follows an earlier revision, the note describes deltas relative to the previous revision, per the CFP's revision-counts-as-submission rule.
De-anonymization, done as a diff
Reversing double-blind is not just adding an author block. Work from the submission-time anonymity sweep, inverting each entry:
- Restore author names, affiliations, and emails in the ACM template's format.
- Convert third-person self-citations back to natural first-person where it reads better — and check none of them still says "the authors of [12]" about yourself.
- Restore acknowledgments and grant numbers; keep the GenAI disclosure placed per ACM policy (immediately before References when in Acknowledgments).
- Re-point anonymized supplemental citations to their real, now-citable targets.
- Replace neutralized infrastructure descriptions with the real testbed identity where confidentiality allows.
# residue sweep on the final PDF
pdftotext final.pdf - | grep -niE 'anonym|blind|supplemental material \[|placeholder' | head
pdfinfo final.pdf | grep -iE 'author|creator' # metadata now SHOULD name youACM-specific obligations
- The rights form drives the copyright block: complete it early, because the generated rights text must be pasted into the paper before the final build, and DOI/ISBN metadata follows from it.
- Verify title and author-list exact match between the rights form, the PDF, and the submission system — mismatches stall Digital Library ingestion and corrupt citation records for years.
- ASPLOS proceedings publish in the ACM DL in multiple volumes per edition under the multi-cycle model; your cycle determines your volume. Production workflow details (TAPS or classic, camera-ready page allowance) for 2027: 待核实 with the acceptance instructions.
Artifact integration
Camera-ready is when artifact evaluation converges with the paper
(asplos-artifact-evaluation):
- The Artifact Appendix is finalized against the actual archived artifact — its dependency list is a promise readers will act on.
- Badges earned (Available / Functional / Reproducible) are attached by the authors or ACM; confirm placement follows the 2027 instructions rather than copying a previous year's badge layout.
- The archival deposit (DOI-issuing repository) must be public before the paper claims it; a dead artifact link in the DL is permanent embarrassment.
Show full SKILL.md (308 more words)Show less
Six-week sequence
- Day 0-2: read the decision letter twice; extract every instruction and deadline into a checklist; identify track (accept vs revision).
- Week 1: rights form; template migration; de-anonymization diff.
- Weeks 2-4: shepherd/letter-required edits; final artifact deposit; appendix sync. For revisions: the required experiments, and nothing speculative.
- Week 5: full residue sweep; metadata check; co-author read of the exact PDF.
- Week 6: upload with margin; confirm the system shows the final version; archive the tagged source.
Presentation and registration obligations for 2027 (who must attend Heraklion, April 11-15, 2027; fees; remote options) were 待核实 at pack-check time — read the acceptance email's requirements before booking or skipping travel.
Final-build quality gate
Run on the exact PDF going to production, not the working draft:
- Fonts embedded; figures vector where possible; colors legible in grayscale (the DL's print-view and many readers' printers are unforgiving).
- Every cross-reference resolves — a "Figure ??" in the published record is permanent, unlike in a submission.
- The bibliography still satisfies the full-name/DOI rules after camera-ready additions (new "since submission" citations arrive malformed by default).
- Appendix/artifact pointers updated from submission-time wording ("anonymous supplemental material") to their published targets.
- Title capitalization, author ordering, and affiliation strings match what co-authors expect to see indexed — this is the last moment ordering disputes can be resolved quietly.
After publication: the unglamorous checklist
- Verify the DL landing page within days of proceedings release: PDF correct, authors ordered, badges displayed, artifact link resolving. Ingestion errors fixed early are emails; fixed late they are erratum processes.
- Keep the archived artifact's README pointing at the DOI-versioned release, and route post-publication fixes to a new tagged version rather than mutating the evaluated one — the badge attaches to what the committee evaluated.
- Record the edition's ordinal and volume in your own records; ASPLOS's multi-volume-per-edition publishing makes later citation reconstruction error-prone without it.
Output format
[Track] accepted-final / major-revision
[Letter checklist] items: N · addressed: N · pointers recorded: Y/N
[De-anonymization] diff complete · residue sweep clean: Y/N
[ACM forms] rights done · title/author exact-match verified: Y/N
[Artifact] deposit public + DOI minted · appendix synced · badges per instructions
[待核实] camera-ready date / page allowance / shepherding / attendance rules© 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 ASPLOS-Skills/skills/asplos-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Asplos 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 |
|---|---|---|---|---|---|---|
| Asplos Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Convertremotion-dev/remotion | 63k | — | ~247 | Automated safety check: Pass | Custom licence | |
| 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 | |
| Word to Markdown Convertergithub/awesome-copilot | 40k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
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.
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.
- Official
Word to Markdown Converter
github/awesome-copilot
Converts Word .docx files to Markdown with a bundled script before analysis, extracting embedded images and handling whole folders alongside the PDF and Excel converters.
Earnings Revisions and Guidance
HKUDS/Vibe-Trading
Tracks analyst estimate revisions, earnings surprises, management guidance and post-earnings drift for US and Hong Kong stocks, and turns them into long and short signals.
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 Asplos Camera Ready
What does Asplos Camera Ready do?
A skill your agent uses when converting an ASPLOS acceptance or Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization, ACM rights and template…. Asplos Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an ASPLOS acceptance or Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization, ACM rights and template obligations, the revision change note, artifact-appendix integration and badge placement, and Digital Library metadata checks.
When should I use Asplos Camera Ready?
Asplos Camera Ready fits situations like: converting an ASPLOS acceptance; major Revision decision into a publishable ACM paper within the six-week window — de-anonymization; ACM rights and template obligations; the revision change note.
How do I install Asplos Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-camera-ready -a claude-code`. Or copy the skill folder (ASPLOS-Skills/skills/asplos-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/asplos-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Asplos Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-camera-ready -a codex`. Or copy the skill folder (ASPLOS-Skills/skills/asplos-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/asplos-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Asplos 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 asplos-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/asplos-camera-ready, .gemini/skills/asplos-camera-ready, .github/skills/asplos-camera-ready and .opencode/skills/asplos-camera-ready in your project.
What does Asplos Camera Ready need to run?
Going by SKILL.md and its folder, Asplos Camera Ready needs the command-line tools its instructions call (pdftotext).
Does Asplos 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 Asplos 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 Asplos Camera Ready use?
Asplos 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 Asplos Camera Ready 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 Asplos Camera Ready?
Skills that share tags, products or a category with Asplos Camera Ready: Convert (remotion-dev/remotion, 63k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars) and Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Asplos 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.