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 turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS…
Install Cikm Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-camera-ready .claude/skills/cikm-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 "cikm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-camera-ready into .claude/skills/cikm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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/CIKM-Skills/skills/cikm-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 cikm-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-camera-ready .agents/skills/cikm-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 "cikm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-camera-ready into .agents/skills/cikm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-camera-ready .cursor/skills/cikm-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 "cikm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-camera-ready into .cursor/skills/cikm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 CIKM-Skills/skills/cikm-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 cikm-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-camera-ready .gemini/skills/cikm-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 "cikm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-camera-ready into .gemini/skills/cikm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-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 cikm-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/CIKM-Skills/skills/cikm-camera-ready .github/skills/cikm-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 "cikm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-camera-ready into .github/skills/cikm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-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 cikm-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/CIKM-Skills/skills/cikm-camera-ready .opencode/skills/cikm-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 "cikm-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-camera-ready into .opencode/skills/cikm-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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
cikm-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 907 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS…
- Works in 3 steps: Every reviewer concern from the ledger… → Every change maps back to a reviewer… → Numbers unchanged: any table value that…
- Turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window
- SKILL.md covers Thirteen-day sequence, De-anonymization is more than…, The metadata outlives the talk and Revision scope discipline, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cikm Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS pipeline into the ACM Digital Library, CCS concepts and metadata, GenAI-disclosure retention, artifact link publication, and Rome presentation 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
- Turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window
- Covering de-anonymization
- The e-rights and TAPS pipeline into the ACM Digital Library
- CCS concepts and metadata
Example prompts
- “/cikm-camera-ready”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Every reviewer concern from the ledger maps to a visible change or a
- Every change maps back to a reviewer concern, an error fix, or
- Numbers unchanged: any table value that moved needs a cause you can state
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.
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
Cikm Camera Ready loads about 1.8k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 907 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). 907 words, ~1,791 tokens.
Download SKILL.mdSave it as
.claude/skills/cikm-camera-ready/SKILL.md (or your agent's skills folder).- name
- cikm-camera-ready
- description
- Use when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS pipeline into the ACM Digital Library, CCS concepts and metadata, GenAI-disclosure retention, artifact link publication, and Rome presentation logistics.
CIKM Camera Ready
CIKM 2026 notifies on August 7 and collects camera-ready on August 20 — a thirteen-day window (source map, 2026-07-08). Because CIKM publishes through ACM's Digital Library (the CIKM '25 volume is DOI 10.1145/3746252), that window contains not just editing but ACM's production machinery: e-rights completion, then source upload through TAPS, whose validation rejects malformed LaTeX. Start the clock at notification, not when the camera-ready email arrives.
Thirteen-day sequence
| Day | Action |
|---|---|
| 0-1 | Reopen the camera-ready instructions; confirm final page allowance (待核实 whether acceptance adds pages) |
| 1-3 | De-anonymization pass; apply the concern → edit ledger from cikm-author-response |
| 3-5 | e-rights form completed by the designated author; copyright block generated |
| 5-9 | TAPS-clean source: standard acmart, no forbidden packages, rights commands in place |
| 9-11 | Metadata layer: CCS concepts, keywords, author ORCIDs, affiliations as they should appear forever |
| 11-13 | Final validated PDF; artifact links live and public; buffer for TAPS rejects |
De-anonymization is more than adding names
- Restore authors, affiliations, acknowledgments, and funding — then re-check the page budget, since these lines cost space in a two-column layout.
- Rewrite third-person self-citations into honest first-person where clarity gains ("we extend our earlier system [12]"), and un-blind any datasets or systems that were pseudonymized for review — Applied Research papers especially, where the deployment context can finally be named if the operator permits.
- Replace anonymized artifact placeholders with the real repository, license chosen, README current, and test every URL logged out.
- Keep the GenAI Usage Disclosure section. It was a submission requirement under the ACM AI policy, and quietly deleting it at camera-ready contradicts the record; update it only if tool usage changed during revision.
The metadata outlives the talk
ACM DL entries are what the paper is for the next decade of citation, indexing, and search. Spend real attention on: CCS concepts that match where readers browse (Information systems → retrieval, data mining, or knowledge representation lanes); author-name forms consistent with each author's dblp record — CIKM's tri-community audience finds papers through dblp and the DL, and a name variant forks a publication record; and an abstract whose first sentence stands alone in a DL search-result snippet.
Revision scope discipline
Camera-ready edits answer reviewer concerns and fix errors; they do not grow the contribution. A safe test per edit: would the reviewers who accepted the paper recognize it as the paper they accepted? Clarifications, added citations, scoped limitation sentences — yes. New experiments upgrading a claim — no; put those in the artifact README or the next paper.
TAPS survival notes
TAPS (The ACM Publishing System) compiles the submitted source itself, and its failures cluster predictably:
| TAPS complaint | Usual cause | Fast fix |
|---|---|---|
| Build failure | Non-whitelisted LaTeX packages | Replace with ACM-approved equivalents early, not at day 12 |
| Missing rights block | e-rights not completed before source upload | Sequence: e-rights first, then paste the generated commands |
| Figure errors | Exotic image formats, missing fonts in PDFs | Flatten to standard PDF/PNG with embedded fonts |
| Metadata mismatch | Title/authors differ between form and source | Make the e-rights form the single source of truth |
| Reference warnings | Hand-formatted bibliography | Use the ACM reference format via BibTeX, resist manual edits |
Upload a test build to TAPS as soon as credentials arrive rather than polishing locally until the deadline; the validator's opinion is the only one that counts, and its error messages take a day of turnaround to act on when accounts, uploads, and co-author availability are factored in.
Show full SKILL.md (351 more words)Show less
Proceedings-record hygiene
Small camera-ready decisions with decade-long consequences: order authors exactly as agreed at submission (the abstract-gate freeze means the set cannot change; the displayed order and name spellings still deserve a final confirmation round); use each author's canonical name form and ORCID so the DL entry merges into the right dblp profile; make the artifact link in the PDF a stable one (archival DOI or a release-tagged repository URL), because the proceedings PDF cannot be edited after publication while repositories move.
The camera-ready diff audit
Before final upload, produce an explicit diff against the reviewed PDF and audit it three ways:
- Every reviewer concern from the ledger maps to a visible change or a recorded no-change reason — the accountability pass.
- Every change maps back to a reviewer concern, an error fix, or de-anonymization — the scope-discipline pass; unprompted "improvements" are where accepted papers acquire new errors nobody reviews.
- Numbers unchanged: any table value that moved needs a cause you can state in one sentence (bug fix, seed policy correction) and, if the movement affects a claim, a flag to the chairs rather than a silent swap.
Archive the reviewed PDF, the camera-ready PDF, and the diff notes together; this bundle answers every future "what changed after review?" question, including your own two years later.
After publication
The DL record is effectively immutable, so post-publication problems route
through process, not re-upload: errata via the chairs/ACM where warranted, code
fixes via new repository releases clearly marked as post-publication (never
rewrite the proceedings-tagged release), and claim corrections — worst case — via
a note in the repository README that honestly states what the paper got wrong.
Teams that handle this transparently keep the baseline-citation afterlife
(cikm-reproducibility); teams that quietly retag releases lose it.
Rome logistics strand (parallel, not sequential)
Registration, visa lead time for Italy/Schengen, and presentation format (presenter-attendance and registration obligations for CIKM 2026 were not verifiable — 待核实, check the acceptance email) run in parallel with production. Assign the logistics strand to a different author than the TAPS strand; the thirteen days do not fit both jobs for one person.
Output format
[Days remaining] <n of the notification→camera-ready window>
[Production state] e-rights / TAPS source / validated PDF
[De-anon checklist] names / self-citations / artifacts / GenAI section retained
[Metadata state] CCS concepts / ORCID-dblp consistency / abstract snippet
[Open risks] <page overflow, TAPS reject, dead links, visa/registration>© 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 CIKM-Skills/skills/cikm-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cikm 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 |
|---|---|---|---|---|---|---|
| Cikm 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 Cikm Camera Ready
What does Cikm Camera Ready do?
A skill your agent uses when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS…. Cikm Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS pipeline into the ACM Digital Library, CCS concepts and metadata, GenAI-disclosure retention, artifact link publication, and Rome presentation logistics.
When should I use Cikm Camera Ready?
Cikm Camera Ready fits situations like: turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window; covering de-anonymization; the e-rights and TAPS pipeline into the ACM Digital Library; CCS concepts and metadata.
How do I install Cikm Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-camera-ready -a claude-code`. Or copy the skill folder (CIKM-Skills/skills/cikm-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cikm-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Cikm Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-camera-ready -a codex`. Or copy the skill folder (CIKM-Skills/skills/cikm-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cikm-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Cikm 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 cikm-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/cikm-camera-ready, .gemini/skills/cikm-camera-ready, .github/skills/cikm-camera-ready and .opencode/skills/cikm-camera-ready in your project.
What does Cikm Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Cikm Camera Ready is instructions for the agent only.
Does Cikm 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 Cikm 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 Cikm Camera Ready use?
Cikm 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 Cikm Camera Ready use?
About 1.8k tokens (SKILL.md is roughly 7.2k 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 Cikm Camera Ready?
Skills that share tags, products or a category with Cikm 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 Cikm 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.