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 an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front, evidence sized to claim scope, honest…
Install Rss Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-writing-style .claude/skills/rss-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 "rss-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-writing-style into .claude/skills/rss-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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/RSS-Skills/skills/rss-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 rss-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-writing-style .agents/skills/rss-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 "rss-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-writing-style into .agents/skills/rss-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 rss-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-writing-style .cursor/skills/rss-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 "rss-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-writing-style into .cursor/skills/rss-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 RSS-Skills/skills/rss-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 rss-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-writing-style .gemini/skills/rss-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 "rss-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-writing-style into .gemini/skills/rss-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 rss-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 rss-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/RSS-Skills/skills/rss-writing-style .github/skills/rss-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 "rss-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-writing-style into .github/skills/rss-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 rss-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 rss-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/RSS-Skills/skills/rss-writing-style .opencode/skills/rss-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 "rss-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-writing-style into .opencode/skills/rss-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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.
Facts
- Skill name
rss-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 688 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when revising an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front, evidence sized to claim scope, honest…
- Works in 4 steps: Merge related-work prose into… → One figure that carries the causal story… → Protocol details reviewers need for… → …
- Revising an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front
- SKILL.md covers The claim-first page, Sizing prose to the claim, Pre-answering, because there… and Brevity as a scored trait, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Rss Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front, evidence sized to claim scope, honest failure reporting, concision under an 8-page ceiling that rewards brevity, and prose that pre-answers reviewers because a rebuttal may never come.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in 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.
When your agent uses it
- Revising an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front
- Evidence sized to claim scope
- Honest failure reporting
- Concision under an 8-page ceiling that rewards brevity
Example prompts
- “/rss-writing-style”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Merge related-work prose into contrastive sentences attached to your claims rather
- One figure that carries the causal story beats three that decorate it; every
- Protocol details reviewers need for belief stay in the body; details needed only
- Delete capability sentences the evaluation never touches. Each one is a free
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
Rss Writing Style loads about 1.5k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 688 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). 688 words, ~1,463 tokens.
Download SKILL.mdSave it as
.claude/skills/rss-writing-style/SKILL.md (or your agent's skills folder).- name
- rss-writing-style
- description
- Use when revising an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front, evidence sized to claim scope, honest failure reporting, concision under an 8-page ceiling that rewards brevity, and prose that pre-answers reviewers because a rebuttal may never come.
RSS Writing Style
Revise the manuscript for the venue where "the robot worked" is the beginning of a paper, not its conclusion. RSS expects a scientific claim; the writing's job is to make that claim visible, falsifiable, and already defended.
The claim-first page
By the end of page one, a reader should be able to fill in:
- Claim: what is asserted about robotics (a mechanism, a property, a bottleneck, a transferable capability) — one sentence, no system name required.
- Stakes: what the field does differently if the claim is true.
- Test: what evidence in this paper could have falsified it.
If the draft's first page instead inventories modules and integrations, it is a
systems report; either surface the insight the integration proves, or reroute
(rss-topic-selection).
Sizing prose to the claim
The cardinal RSS writing sin is claim-evidence inflation: general words resting on narrow trials. Enforce the match at sentence level:
| Sentence habit | Failure it causes | Repair |
|---|---|---|
| "robust manipulation of everyday objects" | Generality unearned by 5 objects | Name the object distribution and count |
| "significantly outperforms" | No statistics behind the adverb | Effect size + interval + trials per condition |
| "works in the real world" | One lab bench ≠ the world | State the environments actually tested |
| "can be applied to X, Y, Z" | Speculation formatted as result | Move to a labeled limitations/outlook sentence |
| "novel framework" | Novelty asserted, not located | One sentence naming the delta vs the nearest method |
Pre-answering, because there may be no rebuttal
Only above-threshold papers got a 2026 rebuttal; write as if you will not. For each major claim, plant the defense where the objection arises:
- The obvious confound → name it and point at the ablation that kills it, in the same paragraph as the result.
- The "did it just memorize the setup?" worry → the transfer/perturbation condition, cited inline.
- The cherry-picking suspicion → the sentence stating all trials are reported, including failures, with the failure table's number.
Brevity as a scored trait
The 8-page limit (excluding references, 2026) is a ceiling the CFP pointedly frames as not a floor. Compression tactics that preserve rigor:
- Merge related-work prose into contrastive sentences attached to your claims rather than a stand-alone tour.
- One figure that carries the causal story beats three that decorate it; every figure caption should state a finding, not a scene.
- Protocol details reviewers need for belief stay in the body; details needed only for replication go to the supplement — the CFP's self-containment rule drawn as a line.
- Delete capability sentences the evaluation never touches. Each one is a free objection.
Show full SKILL.md (268 more words)Show less
An 8-page budget that respects the ceiling
A workable allocation for a claim-plus-hardware paper (adjust, don't worship):
p.1 claim, stakes, falsification test, contribution list
p.2 related work as contrasts (not a tour)
p.3-4 method: the mechanism, then the system carrying it
p.5-6.5 experiments: protocol, results, ablations, failure table
p.6.5-7.5 analysis: what the failures say about the claim
p.7.5-8 limitations with scope sentences; conclusion in 4 lines
refs excluded from the count (2026 rule)Two structural rules the budget encodes: analysis gets real space (RSS reviewers reward interpretation over raw scoreboards), and limitations are body text, not a camera-ready afterthought.
Sentence-level rewrites
| Draft reflex | RSS register |
|---|---|
| "To the best of our knowledge, first to..." | Name the nearest prior and state the delta |
| "Extensive experiments demonstrate..." | "600 trials across 6 conditions show..." |
| "We leave X for future work" (for a load-bearing X) | Test X or narrow the claim now |
| "Our approach is general" | "The mechanism assumes A and B; within them..." |
| "Qualitative results are in the video" | Put the quantitative version in the body |
Honest-failure register
RSS's reviewer culture reads failure reporting as competence, not weakness. The stylistic move: report failures with the same grammatical confidence as successes. "CSD fails on high-friction fabrics (9/40 trials), consistently at the release step" is stronger writing than a defensive footnote — it demonstrates the authors know where the boundary is.
Cross-stack terminology discipline
RSS papers span perception, planning, control, and learning in eight pages, and vocabulary collisions cost belief:
- One name per object across the stack: if the policy's output is an "action" in §3, it cannot become a "command" in §5's tables.
- Define task-success vocabulary once, operationally, and reuse it verbatim in protocol, tables, and captions.
- Symbols survive the whole paper: reusing θ for joint angles and then for policy parameters is a classic cross-subfield paper wound.
- Write for the adjacent-subfield reviewer the single-track format guarantees you: each subfield's jargon gets a half-sentence gloss at first use.
Output format
[Claim sentence] <one sentence, falsifiable, system-name-free>
[Claim-evidence mismatches] <sentence -> repair>
[Unplanted defenses] <objection -> where to pre-answer it>
[Compression targets] <cut / merge / demote-to-supplement>
[Failure register] present and confident / defensive / missing© 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 RSS-Skills/skills/rss-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Rss 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 |
|---|---|---|---|---|---|---|
| Rss Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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 |
Similar skills
Brand
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
Khazix WeChat Article Writer
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.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Unslop AI Writing Cleanup
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.
UX Writing
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.
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 Rss Writing Style
What does Rss Writing Style do?
A skill your agent uses when revising an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front, evidence sized to claim scope, honest…. Rss Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front, evidence sized to claim scope, honest failure reporting, concision under an 8-page ceiling that rewards brevity, and prose that pre-answers reviewers because a rebuttal may never come.
When should I use Rss Writing Style?
Rss Writing Style fits situations like: revising an RSS (Robotics: Science and Systems) draft to meet the science-first bar — a falsifiable claim about robotics up front; evidence sized to claim scope; honest failure reporting; concision under an 8-page ceiling that rewards brevity.
How do I install Rss Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-writing-style -a claude-code`. Or copy the skill folder (RSS-Skills/skills/rss-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/rss-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Rss Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-writing-style -a codex`. Or copy the skill folder (RSS-Skills/skills/rss-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/rss-writing-style in your project. Codex loads it when a task matches its description.
Can I use Rss Writing Style 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 rss-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/rss-writing-style, .gemini/skills/rss-writing-style, .github/skills/rss-writing-style and .opencode/skills/rss-writing-style in your project.
What does Rss Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Rss Writing Style is instructions for the agent only.
Does Rss Writing Style 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 Rss Writing Style 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 Rss Writing Style use?
Rss 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.
How many tokens does Rss Writing Style use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Rss Writing Style?
Skills that share tags, products or a category with Rss 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.
Who maintains Rss Writing Style?
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.