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 IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather…
Install Percom Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-writing-style .claude/skills/percom-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 "percom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-writing-style into .claude/skills/percom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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/PerCom-Skills/skills/percom-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 percom-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-writing-style .agents/skills/percom-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 "percom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-writing-style into .agents/skills/percom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-writing-style .cursor/skills/percom-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 "percom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-writing-style into .cursor/skills/percom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 PerCom-Skills/skills/percom-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 percom-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-writing-style .gemini/skills/percom-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 "percom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-writing-style into .gemini/skills/percom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-writing-style .github/skills/percom-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 "percom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-writing-style into .github/skills/percom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-writing-style .opencode/skills/percom-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 "percom-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-writing-style into .opencode/skills/percom-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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
percom-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 565 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 IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather…
- Revising an IEEE PerCom paper for a pervasive-computing contribution on the first page
- SKILL.md covers Revision rules, Ubicomp paper skeleton, Sentence-level rewrites and Cross-subject and metric…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Cross-subject claims stated precisely
What it does
Percom Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather than recites, evidence proportional to the claim, double-blind wording, and disciplined use of the tight IEEEtran 9-page budget.
Its SKILL.md is about 1.3k 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 IEEE PerCom paper for a pervasive-computing contribution on the first page
- Cross-subject claims stated precisely
- A limitations section that argues rather than recites
- Evidence proportional to the claim
Example prompts
- “/percom-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
Percom Writing Style loads about 1.3k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 565 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). 565 words, ~1,337 tokens.
Download SKILL.mdSave it as
.claude/skills/percom-writing-style/SKILL.md (or your agent's skills folder).- name
- percom-writing-style
- description
- Use when revising an IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather than recites, evidence proportional to the claim, double-blind wording, and disciplined use of the tight IEEEtran 9-page budget.
PerCom Writing Style
Use this when revising the main paper. PerCom papers are IEEE Xplore proceedings read by ubicomp reviewers, so they need a pervasive-computing contribution stated in the first page and evidence a reviewer trusts on people they did not train on. The failure this skill prevents is a technically fine paper that reads like an ML result with a wearable title glued on, or a systems demo with no human at its center.
Revision rules
- Lead with the ubicomp contribution: the problem a real user or deployment faces, why current sensing is inadequate, the contribution (system and/or finding), the evidence, and what changes for pervasive computing.
- State claims at the right granularity. A recognition claim must say cross-subject or within-subject, on what population, with which metric. "97% accuracy" without a split or a class balance is a red flag to a PerCom reviewer, not a headline.
- Pair every claim with proportional evidence — real subjects, a fair baseline, F1 with confidence intervals on realistic class balance, deployment realism — not adjectives.
- Argue limitations; do not recite them. Name the external, construct, and generalization limits that actually bite this study (subject diversity, ground-truth quality, lab vs. free-living), and say what you did to bound each. A boilerplate limitations paragraph tells a reviewer you have not stressed your own claims.
- Respect the 9-page budget as a design constraint, not a formatting afterthought — IEEEtran two-column is tight, and a study that only fits by shrinking the evaluation or limitations is over-scoped. Recover space editorially, never by touching the template.
- Maintain double-blindness in self-citations (third person), testbed and system names, dataset links, acknowledgements, and funding.
Ubicomp paper skeleton
| Section | Job it must do | Common failure |
|---|---|---|
| Intro | Problem, inadequacy, contribution, evidence preview, ubicomp payoff — first page | Leads with a technology trend, not a real-use problem |
| Background/Motivation | Why a user or deployment needs this now | Motivation by assertion, no grounding in practice |
| System / Study design | The technique or the study + sensing protocol, reproducibly | Method or sensor setup described too thinly to re-run |
| Evaluation | Each claim answered with cross-subject, proportional evidence | Within-subject or pooled-accuracy metrics that flatter the result |
| Limitations | The limits that bite, each bounded | Generic list untethered from this study's subjects/sensors |
| Related work | Delta-first positioning against the ubicomp literature | Catalog of citations with no contrast |
Show full SKILL.md (185 more words)Show less
Sentence-level rewrites
| Draft pattern | PerCom-safe rewrite |
|---|---|
| "Our system achieves 97% accuracy." | "leave-one-subject-out F1 of 0.xx (95% CI ...) on <N> participants" |
| "We evaluate on a large dataset." | "We evaluate on <N> participants over <duration> of free-living data, released as a dataset" |
| "Results show our approach works well." | "cross-subject F1 improves by X over <baseline>; per-subject variance in Fig. 3" |
| "State-of-the-art performance." | Claim scoped to the subjects, sensors, and setting actually tested |
| "The model recognizes activities." | "the recognizer reaches F1 0.xx on held-out subjects for <activity set>" |
Cross-subject and metric discipline
[Split] state within-subject vs. leave-one-subject-out (or session-out); PerCom default is cross-subject
[Balance] report class balance; on imbalanced activities use F1 (macro + per-class), not raw accuracy
[Event vs frame] say whether metrics are frame-level or event-level; they can differ sharply
[Realism] lab vs. free-living; scripted vs. spontaneous behavior -- name which you tested
-> for each: state the choice next to the number so a reviewer is not left guessingVignette: compressing an over-length study into 9 pages
A draft with three activity classes, nine figures, and a sprawling background: keep the cross-subject headline result, the two figures that carry it, a per-class F1 table, and a limitations subsection tied to subject diversity and ground truth; move per-subject breakdowns and extra ablations to the dataset with explicit forward references; cut background to what the argument needs. The test of a good cut: a reviewer should be able to answer "does it work on a new person, and what threatens that?" from the body alone.
Output format
[Writing diagnosis] clear / under-motivated / over-claimed / within-subject-only / over-scoped
[First-page fix] <new framing leading with the pervasive-computing contribution>
[Claim audit] <claim -> split (LOSO?) -> metric (F1?) -> where answered -> proportional? yes/no>
[Limitations fix] <limit that bites -> bounding to add, placed by the result>
[Anonymity edits] <system names / self-citations / dataset links 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 PerCom-Skills/skills/percom-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Percom 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 |
|---|---|---|---|---|---|---|
| Percom Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | 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 Percom Writing Style
What does Percom Writing Style do?
A skill your agent uses when revising an IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather…. Percom Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather than recites, evidence proportional to the claim, double-blind wording, and disciplined use of the tight IEEEtran 9-page budget.
When should I use Percom Writing Style?
Percom Writing Style fits situations like: revising an IEEE PerCom paper for a pervasive-computing contribution on the first page; cross-subject claims stated precisely; A limitations section that argues rather than recites; evidence proportional to the claim.
How do I install Percom Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-writing-style -a claude-code`. Or copy the skill folder (PerCom-Skills/skills/percom-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/percom-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Percom Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-writing-style -a codex`. Or copy the skill folder (PerCom-Skills/skills/percom-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/percom-writing-style in your project. Codex loads it when a task matches its description.
Can I use Percom 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 percom-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/percom-writing-style, .gemini/skills/percom-writing-style, .github/skills/percom-writing-style and .opencode/skills/percom-writing-style in your project.
What does Percom Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Percom Writing Style is instructions for the agent only.
Does Percom 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 Percom 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 Percom Writing Style use?
Percom 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 Percom Writing Style use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Percom Writing Style?
Skills that share tags, products or a category with Percom 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 Percom 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.