Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when revising a CIKM manuscript for the tri-community readership — writing an opening that lands with IR, data-mining, and knowledge-management reviewers simultaneously…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-writing-style --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-writing-style .claude/skills/cikm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-writing-style into .claude/skills/cikm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-writing-style", 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-writing-styleType 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-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-writing-style --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-writing-style .agents/skills/cikm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-writing-style into .agents/skills/cikm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-writing-style", 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-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-writing-style --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-writing-style .cursor/skills/cikm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-writing-style into .cursor/skills/cikm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-writing-style", 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-writing-style--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-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-writing-style --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-writing-style .gemini/skills/cikm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-writing-style into .gemini/skills/cikm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-writing-style", 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-writing-styleInstalls 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-writing-style -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-writing-style .github/skills/cikm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-writing-style into .github/skills/cikm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-writing-style", 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-writing-style -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-writing-style --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-writing-style .opencode/skills/cikm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-writing-style into .opencode/skills/cikm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-writing-style", 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.
cikm-writing-styleA skill your agent uses when revising a CIKM manuscript for the tri-community readership — writing an opening that lands with IR, data-mining, and knowledge-management reviewers simultaneously…
Cikm Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a CIKM manuscript for the tri-community readership — writing an opening that lands with IR, data-mining, and knowledge-management reviewers simultaneously, compressing into appendix-inclusive page budgets, keeping claims inside the evidence, and maintaining double-blind and disclosure-compliant prose.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Brand voice and tone. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cikm Writing Style loads about 1.7k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 792 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 792 words, ~1,675 tokens.
.claude/skills/cikm-writing-style/SKILL.md (or your agent's skills folder).A CIKM paper is read in three accents at once. The IR reviewer scans for the task and the evaluation; the mining reviewer scans for the mechanism and its delta; the KM/database reviewer scans for the data reality — schemas, scale, heterogeneity, noise. Style at this venue means making all three scans succeed in the first page, inside a budget where appendices offer no escape (10 pages including them for 2026 full papers).
Order the opening so each lane hits its anchor early:
If the paper cannot state point 2, it is a single-lane paper and
cikm-topic-selection should re-run before more polishing.
Cross-community words are where CIKM drafts leak credibility. Terms with lane- specific meanings — entity, knowledge, relevance, scalable, online — must be pinned at first use. A table of rewrites that recur in CIKM drafts:
| Draft habit | Lane it annoys | Repair |
|---|---|---|
| "our knowledge-aware model" (never defined) | KM-DB | Name the structure: "a model conditioned on a curated product KG (2.1M triples)" |
| "significantly better" without a test | IR | Reserve the word for tested significance; else give the margin |
| "scales to large graphs" | mining | Give the size, hardware, and growth curve actually measured |
| "real-world dataset" | all three | Name the source, size, license, and collection window |
| "state-of-the-art baseline" | mining + IR | Cite venue + year; stale SOTA claims are checked at review |
Because appendices count inside the 2026 budgets, the compression question is not "what moves to the appendix" but "what leaves the PDF." Priority order for cuts: redundant pipeline diagrams; per-dataset tables that repeat one pattern (keep the pattern statement plus the fullest table); hyperparameter grids (→ the cited artifact); derivations of standard results (→ cite). What must stay: everything a reviewer needs to not trust you — evaluation protocol, baseline tuning parity, and the one ablation that isolates the mechanism.
Double-blind style at CIKM includes third-person self-citation ("Cao et al. proposed", even when Cao is an author) and de-identified system prose for applied papers — the deployment must stay describable without becoming attributable. The GenAI Usage Disclosure section is also prose: write it in the same factual register as the experiments ("evaluation scripts drafted with a code assistant, reviewed and tested by the authors; manuscript text human-written"), not as legal boilerplate.
A load-bearing default under the appendix-inclusive budget (adjust, don't worship):
1.0 pp Introduction — the four-step tri-lane opening
0.75 pp Related work — three fronts + the boundary-work paragraph
2.5 pp Method — problem formulation, mechanism, complexity note
3.0 pp Experiments — protocol ¶, main results, decisive ablation, robustness
0.5 pp Deployment/resource specifics (track-dependent)
0.5 pp Limitations + conclusion
1.75 pp Appendix (counts!) — only review-critical overflow
— GenAI Usage Disclosure + references (uncounted)The commonest imbalance in CIKM drafts is a method section eating four-plus pages while the evaluation protocol gets one paragraph; the blended panel reads the protocol paragraph first.
Title and abstract are consumed twice before any human reads page 2: by EasyChair bidding (which lane's reviewers self-select) and later by ACM DL search. A CIKM title should carry the task, the data structure, and — when honest — the setting: "Freshness-Aware Entity Linking for Enterprise Search" routes correctly; "Towards Better Knowledge Utilization" routes randomly. In the abstract, spend one sentence per lane anchor, and put the one number you want remembered in the final sentence — that sentence is what shows in search snippets.
Draft: "With the explosion of information, knowledge graphs have attracted much attention. We propose a novel framework, XYZ, which significantly outperforms state-of-the-art methods."
Rewritten for the tri-lane scan: "Product search at catalog scale fails on queries whose intent lives in relations the index never sees — compatibility, succession, bundling. We link the query to a 2.1M-triple product KG at retrieval time and propagate relevance along typed edges; on two public benchmarks and one industrial log this lifts nDCG@10 by 4-6 points over the strongest KG-free ranker, with the gain concentrated exactly on relation-dependent queries." Problem, boundary, mechanism, calibrated evidence — one breath each.
A limitations paragraph that works at CIKM scopes rather than confesses: state the regime the evidence covers (data types, scale, languages, graph density), name the adjacent regime it does not, and say what would be needed to extend — three sentences, no adjectives of apology. The blended panel treats a well-scoped limitation as expertise and an unscoped one ("may not generalize") as either evasion or, worse, an invitation to imagine failures the authors never tested.
[Three-scan check] IR anchor / mining anchor / KM-DB anchor — found on page 1?
[Pinned terms] <cross-lane words defined at first use>
[Claim-evidence gaps] <sentences promising more than the tables hold>
[Cut list] <what leaves the PDF to make the appendix-inclusive budget>
[Compliance prose] <self-citation person, deployment de-identification, GenAI section tone>© 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
Just SKILL.md in CIKM-Skills/skills/cikm-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Cikm Writing Style 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 Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 518 | — | ~1.7k | Automated safety check: Pass | MIT |
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
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…
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…
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…
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…
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…
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…
Categories
A skill your agent uses when revising a CIKM manuscript for the tri-community readership — writing an opening that lands with IR, data-mining, and knowledge-management reviewers simultaneously…. Cikm Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a CIKM manuscript for the tri-community readership — writing an opening that lands with IR, data-mining, and knowledge-management reviewers simultaneously, compressing into appendix-inclusive page budgets, keeping claims inside the evidence, and maintaining double-blind and disclosure-compliant prose.
Cikm Writing Style fits situations like: revising a CIKM manuscript for the tri-community readership — writing an opening that lands with IR; knowledge-management reviewers simultaneously; compressing into appendix-inclusive page budgets; keeping claims inside the evidence.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-writing-style -a claude-code`. Or copy the skill folder (CIKM-Skills/skills/cikm-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cikm-writing-style in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-writing-style -a codex`. Or copy the skill folder (CIKM-Skills/skills/cikm-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cikm-writing-style in your project. Codex loads it when a task matches its description.
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-writing-style -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-writing-style, .gemini/skills/cikm-writing-style, .github/skills/cikm-writing-style and .opencode/skills/cikm-writing-style in your project.
SKILL.md names no scripts, command-line tools or credentials: Cikm Writing Style is instructions for the agent only.
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.
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.
Cikm Writing Style is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cikm Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.