Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when drafting or revising a SenSys paper's abstract, introduction, and system sections — building the sensing-pain to mechanism to measured-behavior arc inside the…
Install Sensys Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-writing-style .claude/skills/sensys-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 "sensys-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-writing-style into .claude/skills/sensys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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/SenSys-Skills/skills/sensys-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 sensys-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-writing-style .agents/skills/sensys-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 "sensys-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-writing-style into .agents/skills/sensys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-writing-style .cursor/skills/sensys-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 "sensys-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-writing-style into .cursor/skills/sensys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 SenSys-Skills/skills/sensys-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 sensys-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-writing-style .gemini/skills/sensys-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 "sensys-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-writing-style into .gemini/skills/sensys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-writing-style .github/skills/sensys-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 "sensys-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-writing-style into .github/skills/sensys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-writing-style .opencode/skills/sensys-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 "sensys-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-writing-style into .opencode/skills/sensys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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
sensys-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 516 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting or revising a SenSys paper's abstract, introduction, and system sections — building the sensing-pain to mechanism to measured-behavior arc inside the…
- Works in 4 steps: The sensing/deployment pain — the… → Why existing systems fail — each prior… → The mechanism — what you built, in one… → …
- Revising a SenSys papers abstract
- SKILL.md covers The first-page arc, Numbers, not adjectives, Claim → measurement pairing and Structure inside the…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sensys Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising a SenSys paper's abstract, introduction, and system sections — building the sensing-pain to mechanism to measured-behavior arc inside the double-column limit, putting the buildable system on the first page, reporting energy and latency as numbers not adjectives, and pairing every claim with a measurement.
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 a SenSys papers abstract
- System sections — building the sensing-pain to mechanism to measured-behavior arc inside the double-column limit
- Putting the buildable system on the first page
- Reporting energy and latency as numbers not adjectives
Example prompts
- “/sensys-writing-style”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- The sensing/deployment pain — the physical problem, stated so a systems reader feels it.
- Why existing systems fail — each prior approach's failure named specifically, in embedded
- The mechanism — what you built, in one or two sentences, with the constraint it respects.
- The measured behavior — the headline numbers (energy, latency, accuracy under real
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
Sensys Writing Style loads about 1.3k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 516 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). 516 words, ~1,320 tokens.
Download SKILL.mdSave it as
.claude/skills/sensys-writing-style/SKILL.md (or your agent's skills folder).- name
- sensys-writing-style
- description
- Use when drafting or revising a SenSys paper's abstract, introduction, and system sections — building the sensing-pain to mechanism to measured-behavior arc inside the double-column limit, putting the buildable system on the first page, reporting energy and latency as numbers not adjectives, and pairing every claim with a measurement.
SenSys Writing Style
A SenSys paper reads as an engineer's argument: here is a sensing or embedded problem that hurts in a specific way, here is why existing systems fail on constrained hardware, here is the mechanism I built, and here is its measured behavior. The house style rewards concreteness — energy in joules, latency in a distribution, uptime in days — and penalizes the adjective ("lightweight," "efficient") that stands in for a measurement.
The first-page arc
Put the system on the first page. The abstract and opening paragraph should already carry:
- The sensing/deployment pain — the physical problem, stated so a systems reader feels it.
- Why existing systems fail — each prior approach's failure named specifically, in embedded terms (dies mid-inference, exhausts the energy budget, needs an unavailable radio).
- The mechanism — what you built, in one or two sentences, with the constraint it respects.
- The measured behavior — the headline numbers (energy, latency, accuracy under real conditions), each tied to how it was measured.
The worked example in ../../resources/worked-examples/01-introduction.md
walks a before→after of exactly this arc for a batteryless classifier.
Numbers, not adjectives
The single highest-leverage edit in a SenSys draft is replacing evaluative adjectives with measured quantities.
| Weak (adjective) | Strong (SenSys) |
|---|---|
| "Our system is low-power." | "Draws 42 µA average at a 1% duty cycle, measured with a shunt at 10 kHz." |
| "Inference is fast on-device." | "Median 8 ms, 95th-percentile 21 ms, on the target Cortex-M4." |
| "The model is small." | "Quantized to 61 kB, peaking at 18 kB RAM on the MCU." |
| "We deployed for a long time." | "12 nodes over 47 days; two failed on day 9 (battery)." |
| "Accuracy is high." | "F1 0.9x against reference-instrument ground truth (App. A)." |
Claim → measurement pairing
Every quantitative claim should point to the figure, table, or method that backs it. A reviewer should never meet a number they cannot trace. Keep a running map as you write:
Claim → Evidence
"survives power failures" → Fig. 3 (termination across N brownouts)
"bounded end-to-end latency" → Table 2 (latency CDF under harvest trace)
"matches wired accuracy" → Table 3 (paired, same audio, App. A truth)
"projected 2-year lifetime" → §4.3 (measured draw + battery spec, not datasheet)If a claim has no evidence pointer, either measure it or soften it to what you can show.
Show full SKILL.md (184 more words)Show less
Structure inside the double-column cap
The body (≤ 12 pages full / ≤ 6 short) holds the core logic; references and appendices are
unlimited and outside the cap, so the body earns its space by carrying the argument, not the
exhaustive protocol. Typical shape: motivation and system overview early; the mechanism and its
constraint model in the middle; evaluation organized by the measurement axes
(sensys-experiments) — energy, latency, accuracy, deployment — each answering a claim from the
intro. Push full protocols, extra plots, and derivations to appendices (sensys-supplementary).
System-paper discipline
- Overview figure early. A systems reader wants the block diagram before the details; one clear architecture figure repays its page cost.
- Design decisions with their alternatives. State what you chose and what you rejected and why — SenSys reviewers read for whether you understood the design space.
- Honesty about limits. A named limitation (works only above a harvest threshold; degrades past N nodes) reads as competence; a paper with no limits reads as under-evaluated.
- No overclaiming. "Matches the baseline at lower energy" with error bars beats "outperforms" with none. Under-report and let the measurements carry it.
Revision checklist
[ ] The system is on the first page: pain → gap → mechanism → measured behavior.
[ ] Every "low-power / fast / small / accurate" replaced by a measured quantity.
[ ] Every quantitative claim has a figure/table/method pointer.
[ ] Energy and latency reported with method; latency as a distribution.
[ ] An architecture/overview figure appears before the mechanism details.
[ ] Design choices state their rejected alternatives.
[ ] Limitations named honestly; no unqualified "outperforms."
[ ] Body carries the argument; protocols and extra plots in the appendix.Output format
[Arc] first-page arc present? which of the four beats is missing
[Adjectives] list of adjective→measurement edits still needed
[Claims] claims lacking an evidence pointer
[Energy] energy/latency reported with method and distribution? pass/gap
[Open] the one revision that would most raise the paper's systems credibility© 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 SenSys-Skills/skills/sensys-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sensys 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 |
|---|---|---|---|---|---|---|
| Sensys 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 Sensys Writing Style
What does Sensys Writing Style do?
A skill your agent uses when drafting or revising a SenSys paper's abstract, introduction, and system sections — building the sensing-pain to mechanism to measured-behavior arc inside the…. Sensys Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising a SenSys paper's abstract, introduction, and system sections — building the sensing-pain to mechanism to measured-behavior arc inside the double-column limit, putting the buildable system on the first page, reporting energy and latency as numbers not adjectives, and pairing every claim with a measurement.
When should I use Sensys Writing Style?
Sensys Writing Style fits situations like: revising a SenSys papers abstract; system sections — building the sensing-pain to mechanism to measured-behavior arc inside the double-column limit; putting the buildable system on the first page; reporting energy and latency as numbers not adjectives.
How do I install Sensys Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-writing-style -a claude-code`. Or copy the skill folder (SenSys-Skills/skills/sensys-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sensys-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Sensys Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-writing-style -a codex`. Or copy the skill folder (SenSys-Skills/skills/sensys-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sensys-writing-style in your project. Codex loads it when a task matches its description.
Can I use Sensys 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 sensys-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/sensys-writing-style, .gemini/skills/sensys-writing-style, .github/skills/sensys-writing-style and .opencode/skills/sensys-writing-style in your project.
What does Sensys Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Sensys Writing Style is instructions for the agent only.
Does Sensys 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 Sensys 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 Sensys Writing Style use?
Sensys 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 Sensys 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 Sensys Writing Style?
Skills that share tags, products or a category with Sensys 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 Sensys 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.