Agent skill

Chi Camera Ready

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when preparing an accepted ACM CHI paper for publication — the TAPS source upload, the PCS publication-ready package, mandatory accessibility work (alt text…

MITAuto-check passedFrontend & Design

Install Chi Camera Ready

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-camera-ready -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-camera-ready --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/CHI-Skills/skills/chi-camera-ready .claude/skills/chi-camera-ready && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "chi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-camera-ready into .claude/skills/chi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-camera-ready

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-camera-ready -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-camera-ready --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/CHI-Skills/skills/chi-camera-ready .agents/skills/chi-camera-ready && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "chi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-camera-ready into .agents/skills/chi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-camera-ready -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-camera-ready --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/CHI-Skills/skills/chi-camera-ready .cursor/skills/chi-camera-ready && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "chi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-camera-ready into .cursor/skills/chi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path CHI-Skills/skills/chi-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-camera-ready -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-camera-ready --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/CHI-Skills/skills/chi-camera-ready .gemini/skills/chi-camera-ready && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "chi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-camera-ready into .gemini/skills/chi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-camera-ready

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-camera-ready -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/CHI-Skills/skills/chi-camera-ready .github/skills/chi-camera-ready && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "chi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-camera-ready into .github/skills/chi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-camera-ready -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-camera-ready --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/CHI-Skills/skills/chi-camera-ready .opencode/skills/chi-camera-ready && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "chi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-camera-ready into .opencode/skills/chi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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: chi-camera-ready
GitHub stars: 1.2k
Token cost: ~1.5k tokens
SKILL.md length: 688 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when preparing an accepted ACM CHI paper for publication — the TAPS source upload, the PCS publication-ready package, mandatory accessibility work (alt text…

Works in 6 steps: Week of acceptance: e-rights form, ORCID… → Early January: TAPS compile attempt #1;… → Jan 14: TAPS source in. Respond to TAPS… → …
Preparing an accepted ACM CHI paper for publication — the TAPS source upload
SKILL.md covers TAPS is a compiler, not a…, The accessibility pass is…, Open access and rights and The February and March…, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Chi Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ACM CHI paper for publication — the TAPS source upload, the PCS publication-ready package, mandatory accessibility work (alt text, screen-reader-friendly PDFs, table headers), video previews, ACM's open-access model, e-rights, and registration deadlines.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Accessibility. 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

Preparing an accepted ACM CHI paper for publication — the TAPS source upload
The PCS publication-ready package
Mandatory accessibility work (alt text
Screen-reader-friendly PDFs

Example prompts

“/chi-camera-ready”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Week of acceptance: e-rights form, ORCID collection, owner per deliverable.
Early January: TAPS compile attempt #1; fix class errors; alt-text sweep done.
Jan 14: TAPS source in. Respond to TAPS validation quickly — the queue slows near
Early February: proof the TAPS PDF and HTML rendering; check every figure,
Feb 18: PCS publication-ready package: final PDF sign-off, supplements, captions,
Mar 4: registration confirmed, presentation video uploaded.

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
No scripts in the folder and no shell commands in SKILL.md (its code samples are latex and bash).
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

Chi Camera Ready loads about 1.5k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 688 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~76
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

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). 688 words, ~1,499 tokens.

Download SKILL.mdSave it as .claude/skills/chi-camera-ready/SKILL.md (or your agent's skills folder).

name: chi-camera-ready
description: Use when preparing an accepted ACM CHI paper for publication — the TAPS source upload, the PCS publication-ready package, mandatory accessibility work (alt text, screen-reader-friendly PDFs, table headers), video previews, ACM's open-access model, e-rights, and registration deadlines.

CHI Camera-Ready

Acceptance at CHI starts a production pipeline with more moving parts than most venues: ACM TAPS renders your paper from source, an accessibility pass is mandatory rather than aspirational, and the video preview and registration have their own deadlines. CHI 2027 dates (chi2027.acm.org, read 2026-07-08): TAPS source upload January 14, 2027; publication-ready package on PCS February 18, 2027; registration and presentation video March 4, 2027.

TAPS is a compiler, not a dropbox

The ACM Publishing System ingests your LaTeX or Word source and generates the final double-column PDF plus HTML for the Digital Library. You reviewed in single-column; TAPS produces the publication look. Consequences:

Hand-tuned spacing, hacked floats, and non-standard packages that survived your local build can fail in TAPS. Compile with the current acmart class settings early, and budget a round trip for TAPS errors before January 14.
The HTML edition means your content must survive reflow: content buried in absolutely-positioned figures or images-of-text will degrade or vanish.
De-anonymize deliberately: restore authors, affiliations, ORCIDs (get every coauthor's ORCID before January), acknowledgements, grant numbers, and re-link repositories and OSF projects under real identities.

The accessibility pass is required work

SIGCHI's accessibility guidance and the CHI publication-ready instructions make the author responsible for a paper that works with screen readers. The posted division of labor: an external provider tags the TAPS-produced PDF, but authors must supply meaningful alt text for every figure in the source and in PCS — tagging cannot invent descriptions you never wrote.

Item	Requirement	Where it lives
Figure alt text	Describes the information content, not the pixels; complements rather than repeats the caption	`\Description{}` in source + PCS field
Tables	Real table markup with marked header rows — never a screenshot of a table	Source
Color	No claim readable only through color; check contrast	Figures
Math	Real math markup, not inline images	Source
Links	Meaningful link text, not raw URLs mid-sentence	Source
Video captions	Closed captions (SRT/SBV/VTT) on every video file	PCS upload

latex

% Every figure needs a Description; acmart warns, TAPS and PCS expect it.
\begin{figure}
  \includegraphics[width=\linewidth]{study-setup.pdf}
  \Description{Participant seated at a desk wearing the haptic glove, with the
    stimulus screen 60 cm away showing a 3-by-3 target grid.}
  \caption{Study apparatus.}
\end{figure}

bash

# Find figures still missing descriptions before the TAPS upload
grep -L '\\Description' $(grep -rl 'includegraphics' sections/) 2>/dev/null
grep -c '\\Description' main.tex sections/*.tex

Write alt text as if explaining the figure over the phone to a colleague who will act on it. "Bar chart of results" fails; "Bar chart: error rate halves from 12% with the baseline to 6% with our technique, consistent across all three tasks" succeeds.

Show full SKILL.md (318 more words)Show less

Open access and rights

ACM's publication model changed decisively for this generation of CHI: from January 1, 2026 all ACM publications are open access in the Digital Library. Costs are covered either by your institution's ACM Open agreement (over 2,600 institutions; the majority of ACM conference papers) or by an APC; ACM posted discounted transitional APC rates ($250 member / $350 non-member) for conferences during 2026 — the exact arrangements applying to CHI 2027 authors are cycle-specific (待核实 via the e-rights form and acm.org/publications/openaccess). Complete the ACM e-rights form as soon as it arrives; TAPS will not finalize without it. Fill CCS concepts and keywords thoughtfully — they drive DL discovery permanently.

The February and March deliverables

The publication-ready deadline (2027-02-18) is when PCS wants the TAPS-approved paper plus final supplementary materials: the video figure with captions, any datasets/appendix files, and the optional 30-second video preview that appears beside the DL record and in conference programs. The March 4 deadline pairs registration with the presentation video. Practical notes:

The video preview is optional but cheap leverage: it is often the only part of the paper a conference attendee sees before choosing sessions. One idea, one visual, spoken captions-checked audio — not a compressed talk.
Registration rules for publication (who must register, at what rate, in-person versus remote presentation) are posted per cycle and were 待核实 at check time; confirm before assuming a remote option exists.

Sequence for a calm January–March

Week of acceptance: e-rights form, ORCID collection, owner per deliverable.
Early January: TAPS compile attempt #1; fix class errors; alt-text sweep done.
Jan 14: TAPS source in. Respond to TAPS validation quickly — the queue slows near the deadline.
Early February: proof the TAPS PDF and HTML rendering; check every figure, table, and math block survived.
Feb 18: PCS publication-ready package: final PDF sign-off, supplements, captions, video preview.
Mar 4: registration confirmed, presentation video uploaded.

Output format

text

[Pipeline] e-rights ✓/✗ · TAPS compiled ✓/✗ · alt text <n>/<n figures> ·
           supplements ✓/✗ · preview ✓/✗ · registered ✓/✗
[Next deadline] <date> — <deliverable> — owner: <name>
[Accessibility gaps] <figures/tables/math still failing>
[OA route] ACM Open institution / APC (rate 待核实 for the cycle)

Files

Just SKILL.md in CHI-Skills/skills/chi-camera-ready of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Chi 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.

Chi Camera Ready compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Chi Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.5k	Automated safety check: Pass	MIT	12 days ago
Md Reviewborghei/Claude-Skills	886	—	~3.8k	Automated safety check: Pass	MIT	2 days ago
Epub AccessibilityCommunity-Access/accessibility-agents	423	—	~1.1k	Automated safety check: Pass	MIT	16 days ago
Markdown ScannerCommunity-Access/accessibility-agents	423	—	~1.6k	Automated safety check: Pass	MIT	16 days ago
Office Scan ConfigCommunity-Access/accessibility-agents	423	—	~1.4k	Automated safety check: Pass	MIT	16 days ago
PDF Scan ConfigCommunity-Access/accessibility-agents	423	—	~1k	Automated safety check: Pass	MIT	16 days ago

Similar skills

Md Review
borghei/Claude-Skills
Pre-publication quality gate for authored Markdown — heading structure, on-disk link resolution, readability, accessibility, terminology.
886 GitHub stars~3.8k tokensUpdated 2 days ago
Frontend & DesignAuto-check passed
Epub Accessibility
Community-Access/accessibility-agents
Scan and fix .epub files: EPUB Accessibility 1.1, reading order, nav.
423 GitHub stars~1.1k tokensUpdated 16 days ago
Frontend & DesignAuto-check passed
Markdown Scanner
Community-Access/accessibility-agents
Internal helper: scan one markdown file across all nine domains.
423 GitHub stars~1.6k tokensUpdated 16 days ago
Frontend & DesignAuto-check passed
Office Scan Config
Community-Access/accessibility-agents
Internal helper: manage .a11y-office-config.json scan settings.
423 GitHub stars~1.4k tokensUpdated 16 days ago
Frontend & DesignAuto-check passed
PDF Scan Config
Community-Access/accessibility-agents
Internal helper: manage .a11y-pdf-config.json scan settings.
423 GitHub stars~1k tokensUpdated 16 days ago
Frontend & DesignAuto-check passed
Epub Scan Config
Community-Access/accessibility-agents
Internal helper: manage .a11y-epub-config.json scan settings.
423 GitHub stars~899 tokensUpdated 16 days ago
Frontend & DesignAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 12 days ago
Auto-check passed

Questions about Chi Camera Ready

What does Chi Camera Ready do?

A skill your agent uses when preparing an accepted ACM CHI paper for publication — the TAPS source upload, the PCS publication-ready package, mandatory accessibility work (alt text…. Chi Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ACM CHI paper for publication — the TAPS source upload, the PCS publication-ready package, mandatory accessibility work (alt text, screen-reader-friendly PDFs, table headers), video previews, ACM's open-access model, e-rights, and registration deadlines.

When should I use Chi Camera Ready?

Chi Camera Ready fits situations like: preparing an accepted ACM CHI paper for publication — the TAPS source upload; the PCS publication-ready package; mandatory accessibility work (alt text; screen-reader-friendly PDFs.

How do I install Chi Camera Ready in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-camera-ready -a claude-code`. Or copy the skill folder (CHI-Skills/skills/chi-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/chi-camera-ready in your project. Claude Code loads it when a task matches its description.

How do I install Chi Camera Ready in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-camera-ready -a codex`. Or copy the skill folder (CHI-Skills/skills/chi-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/chi-camera-ready in your project. Codex loads it when a task matches its description.

Can I use Chi 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 chi-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/chi-camera-ready, .gemini/skills/chi-camera-ready, .github/skills/chi-camera-ready and .opencode/skills/chi-camera-ready in your project.

What does Chi Camera Ready need to run?

SKILL.md names no scripts, command-line tools or credentials: Chi Camera Ready is instructions for the agent only.

Does Chi 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 Chi 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 Chi Camera Ready use?

Chi 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 Chi Camera Ready use?

About 1.5k tokens (SKILL.md is roughly 6k 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 Chi Camera Ready?

Skills that share tags, products or a category with Chi Camera Ready: Md Review (borghei/Claude-Skills, 886 stars), Epub Accessibility (Community-Access/accessibility-agents, 423 stars), Markdown Scanner (Community-Access/accessibility-agents, 423 stars) and Office Scan Config (Community-Access/accessibility-agents, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chi 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.

Install Chi Camera Ready

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

CHI Camera-Ready

TAPS is a compiler, not a dropbox

The accessibility pass is required work

Open access and rights

The February and March deliverables

Sequence for a calm January–March

Output format

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Related

Questions about Chi Camera Ready