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 USENIX FAST paper for a storage contribution on the first page, a design/mechanism narrative a storage reviewer can follow, an evaluation framed as the…
Install Fast Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-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/FAST-Skills/skills/fast-writing-style .claude/skills/fast-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 "fast-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-writing-style into .claude/skills/fast-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-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/FAST-Skills/skills/fast-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 fast-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-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/FAST-Skills/skills/fast-writing-style .agents/skills/fast-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 "fast-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-writing-style into .agents/skills/fast-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-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 fast-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-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/FAST-Skills/skills/fast-writing-style .cursor/skills/fast-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 "fast-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-writing-style into .cursor/skills/fast-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-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 FAST-Skills/skills/fast-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 fast-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-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/FAST-Skills/skills/fast-writing-style .gemini/skills/fast-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 "fast-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-writing-style into .gemini/skills/fast-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-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 fast-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 fast-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/FAST-Skills/skills/fast-writing-style .github/skills/fast-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 "fast-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-writing-style into .github/skills/fast-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-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 fast-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 fast-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/FAST-Skills/skills/fast-writing-style .opencode/skills/fast-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 "fast-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-writing-style into .opencode/skills/fast-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-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
fast-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 583 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when revising a USENIX FAST paper for a storage contribution on the first page, a design/mechanism narrative a storage reviewer can follow, an evaluation framed as the…
- Revising a USENIX FAST paper for a storage contribution on the first page
- SKILL.md covers Revision rules, Storage paper skeleton, Sentence-level rewrites and Storage-metric discipline, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A design/mechanism narrative a storage reviewer can follow
What it does
Fast Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a USENIX FAST paper for a storage contribution on the first page, a design/mechanism narrative a storage reviewer can follow, an evaluation framed as the storage cost it changes (write amplification, tail latency, endurance, crash consistency), double-blind wording, and disciplined use of the USENIX two-column page budget.
Its SKILL.md is about 1.4k 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 a USENIX FAST paper for a storage contribution on the first page
- A design/mechanism narrative a storage reviewer can follow
- An evaluation framed as the storage cost it changes (write amplification
- Crash consistency)
Example prompts
- “/fast-writing-style”
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
Fast Writing Style loads about 1.4k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 583 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). 583 words, ~1,374 tokens.
Download SKILL.mdSave it as
.claude/skills/fast-writing-style/SKILL.md (or your agent's skills folder).- name
- fast-writing-style
- description
- Use when revising a USENIX FAST paper for a storage contribution on the first page, a design/mechanism narrative a storage reviewer can follow, an evaluation framed as the storage cost it changes (write amplification, tail latency, endurance, crash consistency), double-blind wording, and disciplined use of the USENIX two-column page budget.
FAST Writing Style
Use this when revising the main paper. FAST papers are read by storage systems people, so they need a storage contribution stated on the first page and an evaluation a storage reviewer trusts. The failure this skill prevents is a technically fine paper that reads like a general systems demo or a throughput-bar benchmark with "storage" in the title.
Revision rules
- Lead with the storage contribution: the storage problem a practitioner recognizes, the storage cost current designs pay (write amplification, tail latency, endurance, space, or a consistency gap), your design or finding, real-device evidence, and what changes for storage systems.
- Frame the evaluation as a cost you change, not a speed you win. State up front which storage quantity the paper moves; a reader should know by the end of the intro whether the headline is bytes-written, p99 latency, drive lifetime, or recovery correctness.
- Pair every claim with proportional, real-device evidence — named drives and firmware, standard workloads/traces, a distribution not just a mean, a device counter not an estimate — not adjectives.
- Make the device reality visible early. A storage reviewer wants to know the hardware and its state; a testbed table and a sentence on preconditioning/aging belong near the evaluation's start, not buried.
- Protect the invariant. If the design defers, batches, or reorders writes, say early that you verify crash consistency/durability still holds; do not let the reader wonder.
- Respect the USENIX page budget (FAST '27: ≤12 pages long / ≤6 short, references excluded) as a design constraint. It is a firm two-column limit; recover space editorially, never by shrinking the evaluation or the durability discussion.
- Maintain double-blind in self-citations (third person), system/tool names, acknowledgements, funding, datacenter names, and trace-hosting URLs.
Storage paper skeleton
| Section | Job it must do | Common failure |
|---|---|---|
| Intro | Storage problem, the cost paid, contribution, evidence preview, storage payoff — first page | Leads with a technology trend, not a storage cost |
| Background | The device/media/workload reality the design exploits | Generic background not tied to the mechanism |
| Design / Study | The mechanism or the study protocol, reproducibly | Design described too thinly to rebuild |
| Evaluation | Each claim answered with the right storage metric on real devices | Throughput bar standing in for the claimed cost |
| Consistency/durability | The invariant the change risks, tested | Consistency asserted, never crash-tested |
| Related work | Delta-first positioning against storage literature | Citation catalog with no contrast |
Show full SKILL.md (196 more words)Show less
Sentence-level rewrites
| Draft pattern | FAST-safe rewrite |
|---|---|
| "Our system is much faster." | "cuts write amplification from X to Y on <SSD model, firmware> at steady state" |
| "We evaluate on an SSD." | "on <model/capacity/firmware>, preconditioned to steady state, fill Z%, TRIM on" |
| "Low latency." | "p99.9 read latency of ... under <workload>; full distribution in Fig. N" |
| "It is reliable / consistent." | "recovers a consistent state at all <K> injected crash points (§6)" |
| "State-of-the-art throughput." | Claim scoped to the devices, workloads, and state actually tested |
| "We reduce writes by ~2x." | "bytes-written from device counters fell 2.1x (95% CI ...), vs. the tuned baseline" |
Storage-metric discipline
[Endurance] report bytes-written / P/E cycles from device counters, not estimates
[Latency] report the distribution (p50/p99/p99.9) under load, not the mean
[Amplification] separate read vs. write amplification; say how each is measured
[Space] on-media footprint, including metadata/GC overhead
[Durability] the crash-consistency invariant and the test that checks it
-> lead each result with the metric that matches the claim; put device+state beside itVignette: compressing a design-plus-study paper
A draft with a new cache design, six microbenchmarks, and a sprawling background: keep the design, the two experiments that carry the headline (miss-ratio-vs-cost and tail latency on real traces), and a crash-consistency check; move secondary microbenchmarks and full parameter sweeps to the artifact with forward references; cut background to the media/workload facts the mechanism needs. The test of a good cut: a reviewer should be able to answer "what storage cost does this change, by how much, on what hardware, and does it stay correct?" from the body alone.
Output format
[Writing diagnosis] clear / under-motivated / wrong-metric / device-reality-missing / over-scoped
[First-page fix] <new framing leading with the storage cost the paper changes>
[Metric audit] <claim -> storage metric -> measured on real devices? yes/no>
[Durability check placement] <where the crash-consistency/invariant test is stated>
[Anonymity edits] <system names / self-citations / trace URLs / datacenter names to rewrite>© 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 FAST-Skills/skills/fast-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fast 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 |
|---|---|---|---|---|---|---|
| Fast Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | 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 Fast Writing Style
What does Fast Writing Style do?
A skill your agent uses when revising a USENIX FAST paper for a storage contribution on the first page, a design/mechanism narrative a storage reviewer can follow, an evaluation framed as the…. Fast Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a USENIX FAST paper for a storage contribution on the first page, a design/mechanism narrative a storage reviewer can follow, an evaluation framed as the storage cost it changes (write amplification, tail latency, endurance, crash consistency), double-blind wording, and disciplined use of the USENIX two-column page budget.
When should I use Fast Writing Style?
Fast Writing Style fits situations like: revising a USENIX FAST paper for a storage contribution on the first page; A design/mechanism narrative a storage reviewer can follow; an evaluation framed as the storage cost it changes (write amplification; crash consistency).
How do I install Fast Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-writing-style -a claude-code`. Or copy the skill folder (FAST-Skills/skills/fast-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fast-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Fast Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-writing-style -a codex`. Or copy the skill folder (FAST-Skills/skills/fast-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fast-writing-style in your project. Codex loads it when a task matches its description.
Can I use Fast 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 fast-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/fast-writing-style, .gemini/skills/fast-writing-style, .github/skills/fast-writing-style and .opencode/skills/fast-writing-style in your project.
What does Fast Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Fast Writing Style is instructions for the agent only.
Does Fast 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 Fast 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 Fast Writing Style use?
Fast 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 Fast Writing Style use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 Fast Writing Style?
Skills that share tags, products or a category with Fast 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 Fast 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.