Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
A skill your agent uses when auditing a CIKM submission for EasyChair readiness across the five tracks, covering page budgets with appendices counted inside, the mandatory GenAI Usage Disclosure…
Install Cikm Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-submission --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-submission .claude/skills/cikm-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-submission into .claude/skills/cikm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-submission --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-submission .agents/skills/cikm-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-submission into .agents/skills/cikm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-submission --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-submission .cursor/skills/cikm-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-submission into .cursor/skills/cikm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-submission --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-submission .gemini/skills/cikm-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-submission into .gemini/skills/cikm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/cikm-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-submission into .github/skills/cikm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-submission", 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-submission -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-submission --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-submission .opencode/skills/cikm-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-submission into .opencode/skills/cikm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 750 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing a CIKM submission for EasyChair readiness across the five tracks, covering page budgets with appendices counted inside, the mandatory GenAI Usage Disclosure…
- Auditing a CIKM submission for EasyChair readiness across the five tracks
- SKILL.md covers Per-track budget card (2026), The EasyChair form is part of…, GenAI Usage Disclosure section and Anonymity sweep, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering page budgets with appendices counted inside
What it does
Cikm Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a CIKM submission for EasyChair readiness across the five tracks, covering page budgets with appendices counted inside, the mandatory GenAI Usage Disclosure section, author-reviewer nomination, double-blind rules with arXiv declaration, the abstract-gate authorship freeze, and desk-reject triggers.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Academic paper search. It works with arXiv. 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
- Auditing a CIKM submission for EasyChair readiness across the five tracks
- Covering page budgets with appendices counted inside
- The mandatory GenAI Usage Disclosure section
- Author-reviewer nomination
Example prompts
- “/cikm-submission”
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 Submission loads about 1.6k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 750 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). 750 words, ~1,647 tokens.
Download SKILL.mdSave it as
.claude/skills/cikm-submission/SKILL.md (or your agent's skills folder).- name
- cikm-submission
- description
- Use when auditing a CIKM submission for EasyChair readiness across the five tracks, covering page budgets with appendices counted inside, the mandatory GenAI Usage Disclosure section, author-reviewer nomination, double-blind rules with arXiv declaration, the abstract-gate authorship freeze, and desk-reject triggers.
CIKM Submission
A CIKM submission clears three gates that generic conference checklists miss: an EasyChair form with consequences (track selection, reviewer nomination, arXiv declaration), a page budget that counts appendices inside it, and a named GenAI Usage Disclosure section that must physically exist in the PDF. All specifics below are the verified CIKM 2026 rules (source map, 2026-07-08); reopen the current track call and policies page before certifying anything.
Per-track budget card (2026)
| Track | Budget | Outside the budget |
|---|---|---|
| Full Research | 10 pages incl. figures, tables, appendices | up to 2 pages of references + GenAI disclosure |
| Short Research | 4 pages incl. appendix | references + GenAI disclosure |
| Applied Research | 7 pages incl. appendix | references + GenAI disclosure |
| Resource | 4 pages incl. appendices and acknowledgments | references + GenAI disclosure |
| Demonstration | 4 pages incl. appendices and acknowledgments | references + GenAI disclosure |
All tracks: ACM proceedings template (two-column), English, PDF. Applied Research additionally requires practical-application evidence — a system launch, data release, or equivalent — as part of the claim, not as decoration.
The EasyChair form is part of the submission
- Track selection. Each track has a named EasyChair choice (e.g., "CIKM 2026 Full Research Track"); a paper filed under the wrong track competes under the wrong budget and criteria.
- Author-reviewer nomination. Every submission must nominate at least one of its authors to review for the conference, set inside EasyChair at submission time. CIKM 2026 states plainly that failure to nominate leads to desk rejection — treat the nomination as a required field, assign the most senior eligible author, and record who was named.
- arXiv declaration. If a non-anonymized version is online, or will go online before notification, that must be declared on the form. Not disclosing an existing public version is itself a desk-reject trigger — the risk is the silence, not the preprint.
GenAI Usage Disclosure section
Every CIKM 2026 submission includes a section titled for GenAI usage disclosure, placed after the main content and appendix and before the references, uncounted. It must cover generative-AI use in all stages — research design, code, data, and writing. Write it factually and specifically ("code assistants used for evaluation scripts; no generated text in the manuscript" beats boilerplate), because the conference reserves the right to run automated compliance checks against the ACM AI policy. A missing section is a compliance failure on an explicitly stated rule.
Anonymity sweep
Third-person self-citations; no author names, affiliations, acknowledgments, or grant numbers; no identifying repository URLs, dataset host paths, or PDF metadata; screenshots and demo figures scrubbed of usernames and org names. For Applied Research papers this is the hard case — "deployed at our company" phrasing must stay, but the company must not be inferable from logos, product names, or traffic numbers only one operator could have.
Show full SKILL.md (303 more words)Show less
Abstract-gate week (the underestimated deadline)
The full-track abstract deadline sits one week before the paper deadline (May 16 vs May 23 in 2026) and does more than reserve a slot:
- Authorship freezes there. The ACM authorship policy plus CIKM's explicit no-changes rule mean a collaborator not listed at the abstract gate cannot be added later — settle authorship debates the week before, not the night of.
- The track choice is effectively made there, since the abstract enters one track's EasyChair queue. Re-routing later means withdrawing and resubmitting, feasible only before the paper gate.
- Title and abstract feed reviewer bidding. In an EasyChair pool spanning three communities, a vague abstract draws the wrong lane's reviewers. Name the task, the data type, and the mechanism family so the right specialists bid — this is the cheapest review-quality lever the authors control.
Template pitfalls specific to this stack
- Use the current ACM template configured for anonymous review; stale copies from a co-author's previous ACM paper are the usual source of format drift.
\authornote, running headers, and PDF creator metadata leak identity even when the title block is clean — check document properties, not just the rendered page.- The GenAI Usage Disclosure and references must appear in that order after the appendix; a disclosure section placed after the references technically violates the stated placement.
- ACM class options change what counts as a page; measure the budget in the exact submission configuration, since the camera-ready configuration differs.
Sequenced final check
1. Track call reopened; budget and template confirmed for THIS track
2. Page count measured with appendices in — trim to budget, not to hope
3. GenAI Usage Disclosure section present, specific, correctly placed
4. Anonymization pass: text, figures, metadata, links
5. EasyChair: correct track selected; reviewer nomination completed and logged
6. arXiv/public-version status declared truthfully
7. Abstract gate met a week early — title/abstract/authors frozen there
8. No concurrent submission of this work anywhere else (hard ban)Desk-reject ledger
| Trigger | Why it fires at CIKM |
|---|---|
| Missing reviewer nomination | Explicitly stated 2026 consequence |
| Undeclared public non-anonymized version | Explicitly stated 2026 consequence |
| Over budget once appendices are counted | Budget includes appendices by rule |
| Identity leakage in PDF or metadata | Double-blind policy |
| Concurrent submission elsewhere | Originality policy, no exceptions |
| Missing/hollow GenAI disclosure section | ACM AI-policy compliance, automated checks reserved |
Output format
[Verdict] submit / fix first / do not submit
[Track + budget] <track, measured pages vs limit>
[Form items] nomination: done? / arXiv declared? / track label correct?
[Compliance] GenAI section / anonymity / dual-submission
[Ordered fixes] <shortest path to a clean upload>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cikm Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Read arXiv Paperkarpathy/nanochat | 59k | 1 repos | ~494 | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Openalex Databaseneflibata-feng/MyArxiv-Agent | 126 | 12 repos | ~3k | Automated safety check: Pass | Custom licence | |
| Citation ManagementK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.9k | Automated safety check: Notes | MIT | |
| Citation Managementneflibata-feng/MyArxiv-Agent | 126 | 19 repos | ~8.1k | Automated safety check: Notes | MIT |
Similar skills
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
Citation Management
K-Dense-AI/claude-scientific-writer
Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.
Citation Management
neflibata-feng/MyArxiv-Agent
Comprehensive citation management for academic research. An agent skill from neflibata-feng/MyArxiv-Agent.
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
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
Works with
Categories
Questions about Cikm Submission
What does Cikm Submission do?
A skill your agent uses when auditing a CIKM submission for EasyChair readiness across the five tracks, covering page budgets with appendices counted inside, the mandatory GenAI Usage Disclosure…. Cikm Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a CIKM submission for EasyChair readiness across the five tracks, covering page budgets with appendices counted inside, the mandatory GenAI Usage Disclosure section, author-reviewer nomination, double-blind rules with arXiv declaration, the abstract-gate authorship freeze, and desk-reject triggers.
When should I use Cikm Submission?
Cikm Submission fits situations like: auditing a CIKM submission for EasyChair readiness across the five tracks; covering page budgets with appendices counted inside; the mandatory GenAI Usage Disclosure section; author-reviewer nomination.
How do I install Cikm Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-submission -a claude-code`. Or copy the skill folder (CIKM-Skills/skills/cikm-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cikm-submission in your project. Claude Code loads it when a task matches its description.
How do I install Cikm Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-submission -a codex`. Or copy the skill folder (CIKM-Skills/skills/cikm-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cikm-submission in your project. Codex loads it when a task matches its description.
Can I use Cikm Submission 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-submission -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-submission, .gemini/skills/cikm-submission, .github/skills/cikm-submission and .opencode/skills/cikm-submission in your project.
What does Cikm Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Cikm Submission is instructions for the agent only.
Does Cikm Submission 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 Submission 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 Submission use?
Cikm Submission 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 Submission use?
About 1.6k tokens (SKILL.md is roughly 6.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 Cikm Submission?
Skills that share tags, products or a category with Cikm Submission: Read arXiv Paper (karpathy/nanochat, 59k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Openalex Database (neflibata-feng/MyArxiv-Agent, 126 stars) and Citation Management (K-Dense-AI/claude-scientific-writer, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cikm Submission?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.