Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
A skill your agent uses when converting an accepted ISCA paper into its published form — de-anonymizing authors, acknowledgments, and artifact links; satisfying the edition's publisher workflow…
Install Isca Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-camera-ready .claude/skills/isca-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 "isca-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-camera-ready into .claude/skills/isca-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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/ISCA-Skills/skills/isca-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 isca-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-camera-ready .agents/skills/isca-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 "isca-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-camera-ready into .agents/skills/isca-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-camera-ready .cursor/skills/isca-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 "isca-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-camera-ready into .cursor/skills/isca-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 ISCA-Skills/skills/isca-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 isca-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-camera-ready .gemini/skills/isca-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 "isca-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-camera-ready into .gemini/skills/isca-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-camera-ready .github/skills/isca-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 "isca-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-camera-ready into .github/skills/isca-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-camera-ready .opencode/skills/isca-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 "isca-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-camera-ready into .opencode/skills/isca-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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
isca-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 734 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 accepted ISCA paper into its published form — de-anonymizing authors, acknowledgments, and artifact links; satisfying the edition's publisher workflow…
- Works in 4 steps: Registration — whether a specific… → Talk — the community's norm is… → Poster/lightning collateral if the… → …
- Converting an accepted ISCA paper into its published form — de-anonymizing authors
- SKILL.md covers The publisher variable unique…, De-anonymization is a…, Shepherds and required changes and Content changes: repair, don't…, plus 4 more sections
- Calls pdftotext
What it does
Isca Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an accepted ISCA paper into its published form — de-anonymizing authors, acknowledgments, and artifact links; satisfying the edition's publisher workflow under the alternating ACM/IEEE arrangement; integrating shepherd requirements and badges; and preparing the June talk and attendance logistics.
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.
It sits in Documents & Office. 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 accepted ISCA paper into its published form — de-anonymizing authors
- Acknowledgments
- Satisfying the editions publisher workflow under the alternating ACM/IEEE arrangement
- Integrating shepherd requirements and badges
Example prompts
- “/isca-camera-ready”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Registration — whether a specific author-registration category is
- Talk — the community's norm is mechanism-forward: motivate with your
- Poster/lightning collateral if the edition uses them — 待核实.
- Publicity — once the proceedings version exists: update the arXiv record
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
Isca Camera Ready loads about 1.8k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 734 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). 734 words, ~1,770 tokens.
Download SKILL.mdSave it as
.claude/skills/isca-camera-ready/SKILL.md (or your agent's skills folder).- name
- isca-camera-ready
- description
- Use when converting an accepted ISCA paper into its published form — de-anonymizing authors, acknowledgments, and artifact links; satisfying the edition's publisher workflow under the alternating ACM/IEEE arrangement; integrating shepherd requirements and badges; and preparing the June talk and attendance logistics.
ISCA Camera-Ready
Acceptance starts a second, administrative project with real failure modes:
papers have appeared with anonymization stubs intact, dead artifact links, and
acknowledgments naming the wrong grant. The 2026 edition maintained a dedicated
camera-ready guidelines page (iscaconf.org/isca2026/submit/cameraready.php —
its detailed contents were not directly fetchable at verification time, so the
specific instructions below marked practice are community-standard rather than
quoted rules; the page itself is the authority — 待核实 per edition).
The publisher variable unique to ISCA
ISCA's ACM SIGARCH + IEEE-CS TCCA co-sponsorship shows up concretely at camera-ready: the publishing arrangement varies by edition (the 52nd edition's proceedings were ACM-published; the 2026 edition carried IEEE branding and pointed LaTeX users at an IEEE template). Everything downstream — rights forms, copyright blocks, final template, DOI issuer, submission portal for finals — follows the edition's publisher. Rule one of ISCA camera-ready: identify this edition's publisher workflow before touching the LaTeX, and expect it to differ from the last ISCA you published at.
De-anonymization is a checklist, not a mood
Work from the submission's blinding actions and invert each one deliberately:
| Was blinded at submission | Camera-ready action |
|---|---|
| Author block absent | Full names, affiliations, emails — order confirmed by all coauthors in writing before upload |
| PDF metadata scrubbed | Regenerate with true metadata; verify with pdfinfo |
| Artifact links anonymized | Swap in canonical repo + archival DOI (isca-artifact-evaluation); click every link from the final PDF |
| Third-person self-citations | Recast where the prose reads absurdly; keep where fine |
| Acknowledgments omitted | Add funders with exact grant numbers, contributors, and any disclosure the publisher's policy requires |
| Neutralized cluster/trace names | Restore real names where licenses permit |
# Final-PDF de-anonymization verification (inverse of the submission sweep)
pdfinfo final.pdf | grep -i author # now SHOULD list authors
pdftotext final.pdf - | grep -ci 'anonym' # expect 0
pdftotext final.pdf - | grep -nE 'blind review|under submission' # expect none
pdftotext final.pdf - | grep -oE 'https?://[^ )]+' | sort -u > links.txt
while read -r u; do curl -s -o /dev/null -w '%{http_code} %s\n' "$u" "$u"; \
done < links.txt | grep -v '^200' # every link in the paper resolvesShepherds and required changes
If the acceptance carries a shepherd or a mandatory-revisions list, that list is a condition, not a suggestion. Practice that keeps this smooth: send the shepherd a change memo (item → what changed → where) with the revised draft, early enough for one round of disagreement; where you believe a requested change is wrong, negotiate in the memo — never silently skip an item and hope.
Content changes: repair, don't remodel
Camera-ready is for review-driven repairs and accuracy fixes. If numbers changed (a bug found post-acceptance, a rerun under the fixed seed), correct them and ensure abstract/intro claims still match the tables — publishing known- stale numbers because "it was accepted with them" is how errata happen. Do not add new contributions; the version of record should be the reviewed paper, healed. Any camera-ready page allowance beyond the submission's 11 text pages is edition-specific and was not verified — 待核实 before planning to grow.
Show full SKILL.md (321 more words)Show less
Badges, statements, and the artifact block
Coordinate with the AE track (isca-artifact-evaluation): earned badges are
applied to the published paper under the ACM badging framework, and the
camera-ready typically carries an artifact-availability statement with the
archival DOI. Get the DOI before the camera-ready deadline by depositing the
evaluated snapshot early; retrofitting a DOI after the proceedings freeze is
somewhere between painful and impossible.
The June obligations
The 2026 conference ran June 27 - July 1 in Raleigh. Between camera-ready and the conference, in rough order of deadline pressure:
- Registration — whether a specific author-registration category is mandatory per paper was not verified (待核实, and commonly true at flagship venues); resolve it the week of acceptance, with visa lead times in mind for international authors.
- Talk — the community's norm is mechanism-forward: motivate with your
measured data, spend the middle on how the design works (the walk-through
from
isca-writing-styletranslates directly to slides), end on the honest limits. Rehearse against the session's time slot, not a guess at it. - Poster/lightning collateral if the edition uses them — 待核实.
- Publicity — once the proceedings version exists: update the arXiv record if one exists, the lab page, and the repo README to cite the canonical DOI, so the version of record accretes the citations.
Sequence for the six-or-so weeks
Week 0 Read THIS edition's camera-ready page top to bottom; identify
publisher, template, rights form, portal, true deadline (AoE?).
Week 1 Shepherd memo (if any) + content repairs; coauthor sign-off on
author order and affiliations.
Week 2 De-anonymization checklist; acknowledgments with grant numbers;
artifact DOI deposited.
Week 3 Publisher template pass; rights form executed by the authorized
author; metadata (title case, abstract, keywords) entered exactly.
Week 4 Link check + verification script above on the actual final PDF;
upload; download back and re-verify what the portal stored.
Buffer Publisher back-and-forth (format rejections are routine, not
emergencies) + registration + talk drafting.Final gate before upload
- Publisher, template, and rights form identified from THIS edition's pages
- Author block, order, and affiliations signed off by every coauthor
- De-anonymization checklist fully inverted; verification script clean
- Shepherd/mandatory items all addressed with a change memo
- Artifact DOI live; badge coordination confirmed with AE chairs
- Acknowledgments carry exact grant numbers and required disclosures
- Portal's stored PDF downloaded back and re-verified
- Registration done; talk slot known; travel and visa in motion
Verified anchors (dates, sponsorship, AE arrangement, 2026 template flavor):
../../resources/official-source-map.md, checked 2026-07-08. The camera-ready
page contents, page allowance, rights workflow, and attendance rules for the
target edition are the controlling sources once posted.
© 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 ISCA-Skills/skills/isca-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Isca 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 |
|---|---|---|---|---|---|---|
| Isca Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Markdown Article FormatterJimLiu/baoyu-skills | 26k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 782 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Gzh Designisjiamu/gzh-design-skill | 3.9k | 1 repos | ~2.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
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…
Related
Categories
Questions about Isca Camera Ready
What does Isca Camera Ready do?
A skill your agent uses when converting an accepted ISCA paper into its published form — de-anonymizing authors, acknowledgments, and artifact links; satisfying the edition's publisher workflow…. Isca Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an accepted ISCA paper into its published form — de-anonymizing authors, acknowledgments, and artifact links; satisfying the edition's publisher workflow under the alternating ACM/IEEE arrangement; integrating shepherd requirements and badges; and preparing the June talk and attendance logistics.
When should I use Isca Camera Ready?
Isca Camera Ready fits situations like: converting an accepted ISCA paper into its published form — de-anonymizing authors; acknowledgments; satisfying the editions publisher workflow under the alternating ACM/IEEE arrangement; integrating shepherd requirements and badges.
How do I install Isca Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-camera-ready -a claude-code`. Or copy the skill folder (ISCA-Skills/skills/isca-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/isca-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Isca Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-camera-ready -a codex`. Or copy the skill folder (ISCA-Skills/skills/isca-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/isca-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Isca 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 isca-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/isca-camera-ready, .gemini/skills/isca-camera-ready, .github/skills/isca-camera-ready and .opencode/skills/isca-camera-ready in your project.
What does Isca Camera Ready need to run?
Going by SKILL.md and its folder, Isca Camera Ready needs the command-line tools its instructions call (pdftotext).
Does Isca 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 Isca 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 Isca Camera Ready use?
Isca 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 Isca Camera Ready use?
About 1.8k tokens (SKILL.md is roughly 7.1k 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 Isca Camera Ready?
Skills that share tags, products or a category with Isca Camera Ready: Markdown Article Formatter (JimLiu/baoyu-skills, 26k stars), Markitdown (ImCa0/just-laws, 782 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Isca 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.