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 ACM FAccT paper so that a fairness/accountability/transparency contribution is legible on the first page to a mixed CS+law+social-science reviewer pool…
Install Facct Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-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/FAccT-Skills/skills/facct-writing-style .claude/skills/facct-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 "facct-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-writing-style into .claude/skills/facct-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-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/FAccT-Skills/skills/facct-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 facct-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-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/FAccT-Skills/skills/facct-writing-style .agents/skills/facct-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 "facct-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-writing-style into .agents/skills/facct-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-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 facct-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-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/FAccT-Skills/skills/facct-writing-style .cursor/skills/facct-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 "facct-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-writing-style into .cursor/skills/facct-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-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 FAccT-Skills/skills/facct-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 facct-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills facct-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/FAccT-Skills/skills/facct-writing-style .gemini/skills/facct-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 "facct-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-writing-style into .gemini/skills/facct-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-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 facct-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 facct-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/FAccT-Skills/skills/facct-writing-style .github/skills/facct-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 "facct-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-writing-style into .github/skills/facct-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-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 facct-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 facct-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/FAccT-Skills/skills/facct-writing-style .opencode/skills/facct-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 "facct-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAccT-Skills/skills/facct-writing-style into .opencode/skills/facct-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "facct-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
facct-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 652 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 ACM FAccT paper so that a fairness/accountability/transparency contribution is legible on the first page to a mixed CS+law+social-science reviewer pool…
- Claims are scoped to who is affected
- SKILL.md covers Revision rules, The FAccT paper skeleton, Sentence-level rewrites and Limitations-and-harm discipline, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Limitations and harms are argued rather than recited
What it does
Facct Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ACM FAccT paper so that a fairness/accountability/transparency contribution is legible on the first page to a mixed CS+law+social-science reviewer pool, claims are scoped to who is affected, limitations and harms are argued rather than recited, the interdisciplinary framing is native, and the acmart page budget and endmatter statements are used well.
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
- Claims are scoped to who is affected
- Limitations and harms are argued rather than recited
- The interdisciplinary framing is native
- The acmart page budget and endmatter statements are used well
Example prompts
- “/facct-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
Facct Writing Style loads about 1.5k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 652 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). 652 words, ~1,470 tokens.
Download SKILL.mdSave it as
.claude/skills/facct-writing-style/SKILL.md (or your agent's skills folder).- name
- facct-writing-style
- description
- Use when revising an ACM FAccT paper so that a fairness/accountability/transparency contribution is legible on the first page to a mixed CS+law+social-science reviewer pool, claims are scoped to who is affected, limitations and harms are argued rather than recited, the interdisciplinary framing is native, and the acmart page budget and endmatter statements are used well.
FAccT Writing Style
Use this when revising the main paper. FAccT papers are read by a deliberately mixed panel — a computer scientist, a lawyer, and a qualitative social scientist may each land on your paper — so the writing must make a fairness, accountability, or transparency contribution legible to all three and must be honest about who is affected and how. The failure this skill prevents is a paper that is excellent inside one discipline and illegible or naive to the others.
Revision rules
- Lead with the FAccT contribution. The first page names the socio-technical problem, who bears the harm or holds the accountability, why the current state is inadequate, the contribution (method, audit, framework, critique, study, or legal analysis), and what changes for people — before any model or doctrinal detail.
- Scope claims to a population, not the world. "Reduces bias" is not a FAccT claim; "reduces the false-positive-rate gap between groups A and B on dataset D, under measure M" is. Name the subgroups, the fairness/transparency construct, and the operationalization.
- Argue limitations and adverse impacts; do not recite them. State the harms, failure modes, and who could be hurt if the work is deployed or misread — and what you did about each. A boilerplate "limitations" paragraph is a tell that the author has not stressed their own claims. This is also where the Adverse Impacts endmatter statement earns its keep.
- Make the interdisciplinarity native. If you borrow a construct from law or the social sciences, use it the way that field uses it, cite its real origin, and carry it through the analysis — not as a one-line garnish.
- Respect the acmart page budget as a design constraint. FAccT 2026 allows up to 14 content pages (+1 endmatter page; 15 if Revised/accepted), references unlimited — generous but finite. A paper that only fits by shrinking its limitations or method is over-scoped.
- Preserve mutual anonymity in self-citations, system names, acknowledgements, funding, and — critically — keep the Positionality statement out of the anonymous submission entirely.
Show full SKILL.md (322 more words)Show less
The FAccT paper skeleton
| Section | Job it must do | Common failure |
|---|---|---|
| Intro | Sociotechnical problem, who is affected, contribution, what changes — first page | Leads with a model/benchmark, not a harm or accountability question |
| Background / motivation | Why this matters now, grounded across the relevant disciplines | Motivation by assertion; one-discipline framing |
| Approach / method / argument | The technique, study design + protocol, or the conceptual/legal argument | Method too thin to re-run, or critique with no engagement with the artifact |
| Findings / evaluation | Disaggregated results, coded themes, or a defended argument | Aggregate-only numbers that hide subgroup harm |
| Limitations & adverse impacts | The harms and threats that actually bite, each bounded | Generic list untethered from this work |
| Related work | Cross-disciplinary, delta-first positioning | Cites only one lane; misses the obvious neighbor in another field |
Sentence-level rewrites
| Draft pattern | FAccT-safe rewrite |
|---|---|
| "Our method is fair." | "our method equalizes <metric> across <groups> on <dataset>, within <bound>; residual gaps in §5" |
| "We improve transparency." | "we surface <what> to <whom> for <decision>, and we test whether they can act on it" |
| "The model is accurate on a large dataset." | "accuracy disaggregated by <subgroup> (Table 2); the largest error falls on <group>" |
| "This raises ethical concerns." | "this risks <specific harm> to <specific population>; we mitigate by <action>, residual risk in the Adverse Impacts statement" |
| "Prior work is limited." | "<work> measured X but not the deployment outcome Y that governs harm; we measure Y" |
Limitations-and-harm discipline
[Construct] does the fairness/transparency metric mean what you claim for the affected group?
[Population] which groups are in and out of scope; who is invisible in your data?
[Deployment] what goes wrong if this ships or is cited as license to deploy? who is hurt?
[Reflexivity] whose standpoint shaped the framing? (state it in Positionality upon acceptance)
-> for each that bites: state it, then state the mitigation, next to the affected resultVignette: compressing an audit paper
A draft auditing a commercial system, with aggregate accuracy up front and a short ethics paragraph at the end: move the disaggregated subgroup results to the first result table, put the worst-affected group in the abstract, argue the construct-validity threat (does your proxy for the protected attribute mean what you claim?) beside that table, and move method minutiae to supplementary. The test of a good cut: a mixed reviewer can answer "who is harmed, by how much, and how sure are we?" from the body alone.
Output format
[Writing diagnosis] clear / under-motivated / over-claimed / single-discipline / harm-blind / over-scoped
[First-page fix] <new framing leading with the FAccT contribution and who is affected>
[Claim audit] <claim -> population + construct + operationalization -> scoped? yes/no>
[Harm fix] <adverse impact that bites -> mitigation to add, placed by the result>
[Anonymity edits] <system names / self-citations / positionality kept out of the anonymous PDF>© 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 FAccT-Skills/skills/facct-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Facct 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 |
|---|---|---|---|---|---|---|
| Facct 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 Facct Writing Style
What does Facct Writing Style do?
A skill your agent uses when revising an ACM FAccT paper so that a fairness/accountability/transparency contribution is legible on the first page to a mixed CS+law+social-science reviewer pool…. Facct Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ACM FAccT paper so that a fairness/accountability/transparency contribution is legible on the first page to a mixed CS+law+social-science reviewer pool, claims are scoped to who is affected, limitations and harms are argued rather than recited, the interdisciplinary framing is native, and the acmart page budget and endmatter statements are used well.
When should I use Facct Writing Style?
Facct Writing Style fits situations like: claims are scoped to who is affected; limitations and harms are argued rather than recited; the interdisciplinary framing is native; the acmart page budget and endmatter statements are used well.
How do I install Facct Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-writing-style -a claude-code`. Or copy the skill folder (FAccT-Skills/skills/facct-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/facct-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Facct Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-writing-style -a codex`. Or copy the skill folder (FAccT-Skills/skills/facct-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/facct-writing-style in your project. Codex loads it when a task matches its description.
Can I use Facct 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 facct-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/facct-writing-style, .gemini/skills/facct-writing-style, .github/skills/facct-writing-style and .opencode/skills/facct-writing-style in your project.
What does Facct Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Facct Writing Style is instructions for the agent only.
Does Facct 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 Facct 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 Facct Writing Style use?
Facct 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 Facct 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 Facct Writing Style?
Skills that share tags, products or a category with Facct 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 Facct 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.