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 an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing…
Install Isca Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-writing-style .claude/skills/isca-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 "isca-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-writing-style into .claude/skills/isca-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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/ISCA-Skills/skills/isca-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 isca-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-writing-style .agents/skills/isca-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 "isca-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-writing-style into .agents/skills/isca-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-writing-style .cursor/skills/isca-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 "isca-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-writing-style into .cursor/skills/isca-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 ISCA-Skills/skills/isca-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 isca-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-writing-style .gemini/skills/isca-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 "isca-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-writing-style into .gemini/skills/isca-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-writing-style .github/skills/isca-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 "isca-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-writing-style into .github/skills/isca-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-writing-style .opencode/skills/isca-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 "isca-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-writing-style into .opencode/skills/isca-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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
isca-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 763 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 an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing…
- Revising an ISCA papers prose — organizing 11 pages around one architectural insight
- SKILL.md covers One insight, stated as a…, The load-bearing motivation…, Mechanism description at… and Calibrated numbers, always…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Writing the motivation section from measured data
What it does
Isca Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing mechanisms at reviewer-checkable precision with figures that carry the design, and keeping quantitative claims calibrated to the instrument behind them.
Its SKILL.md is about 1.7k 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 ISCA papers prose — organizing 11 pages around one architectural insight
- Writing the motivation section from measured data
- Describing mechanisms at reviewer-checkable precision with figures that carry the design
- Keeping quantitative claims calibrated to the instrument behind them
Example prompts
- “/isca-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
Isca Writing Style loads about 1.7k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 763 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). 763 words, ~1,686 tokens.
Download SKILL.mdSave it as
.claude/skills/isca-writing-style/SKILL.md (or your agent's skills folder).- name
- isca-writing-style
- description
- Use when drafting or revising an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing mechanisms at reviewer-checkable precision with figures that carry the design, and keeping quantitative claims calibrated to the instrument behind them.
ISCA Writing Style
An ISCA paper is an argument that a piece of machine organization should exist. The prose conventions below are how the architecture community expects that argument to be laid out — learned from the venue's canon and enforced, softly but consistently, by its reviewers. Format facts (11 pages of single-spaced two-column text excluding references, IEEE-flavored template for the 2026 edition) are the verified 2026 snapshot; recheck the current guidelines page before formatting.
One insight, stated as a mechanism-behavior link
Before drafting, complete this sentence and pin it above the desk:
Because
<structural property of workloads or designs>, organizing the hardware as<mechanism>yields<behavioral consequence>, which we demonstrate by<instrument>.
Every section either supports that sentence or gets cut. Papers with two ideas do worse than either idea alone at this venue — the review form's "key contribution" box forces a choice, and reviewers make it less charitably than authors would.
The load-bearing motivation section
The distinctive ISCA move is Section 2 as a measured motivation: characterization data showing the problem exists at magnitude, on workloads the community accepts, before any proposal appears. A motivation built from citations alone reads as secondhand. Aim for two or three characterization plots whose captions alone establish (a) the bottleneck, (b) its trend across configurations or generations, and (c) why existing mechanisms cannot close it. This section frequently decides the paper's fate: it is where reviewers decide whether the problem is real.
Mechanism description at checkable precision
Reviewers must be able to mentally simulate the design. That requires:
- A block diagram naming every added structure, with sizes (entries, bits, ports).
- The walk-through: one concrete event traced end to end through the mechanism ("a load misses in L2; the tracker allocates entry E; ...").
- Every policy decision stated with its trigger and its fallback.
- A hardware-cost paragraph: storage, comparators, wiring implications, and where in the pipeline the logic sits — even a conservative estimate beats silence.
The failure pattern is prose that describes what the mechanism achieves where the reader needs what it does. "The prefetcher adapts to phase changes" is a claim; "the confidence counter decays every 4K cycles, and entries below threshold T stop issuing" is a mechanism.
Calibrated numbers, always with their instrument
Quantitative claims carry their evidence class with them. A useful internal discipline while drafting:
| Draft phrase | Rewrite that survives review |
|---|---|
| "improves performance by 34%" | "improves geomean IPC by 34% over <baseline> on <suite> in <simulator+config>" |
| "adds negligible overhead" | "adds 18.4 KB of SRAM per core and one pipeline stage on the miss path" |
| "significantly outperforms" | delete "significantly" unless a statistical test appears |
| "our design scales well" | "speedup holds within 5% from 4 to 64 cores (Fig. 9)" |
| "energy-efficient" | "reduces modeled DRAM energy 21% (tool, node, and caveats in §5.1)" |
Absolute claims from relative instruments are the venue's best-known writing sin;
isca-experiments covers the underlying methodology contract.
Show full SKILL.md (287 more words)Show less
Budgeting the 11 pages
References are unlimited (verified for 2026), so never starve the bibliography to save space. A budget that has served the venue's structure well:
1.0 Introduction: problem, insight sentence, contribution list with numbers
1.5 Motivation/characterization: measured, workload-grounded
0.5 Background only if genuinely non-standard; else fold into motivation
3.0 Design: overview figure -> mechanism detail -> walk-through -> cost
1.0 Methodology: instruments, configs, workloads, baselines (see
isca-experiments; reviewers read this section early)
3.0 Evaluation: headline -> attribution/sensitivity -> overheads -> limits
0.5 Related work (see isca-related-work) + conclusion
= 10.5 of 11, leaving slack for review-driven revision growthFigures deserve disproportionate care: at this venue the design figure and the headline results figure are what the PC remembers. Design figures should be redrawn, not screenshotted from slides; results figures need readable axes at print size and a caption that states the takeaway, not just the contents.
Sentence-level habits of accepted papers
- Present tense for the design ("the controller tracks"), past tense for experiments ("we measured").
- Name structures once and reuse the name exactly; synonyms ("the table", "the buffer", "the tracker") force reviewers to guess whether they are one structure.
- Contributions listed as falsifiable statements with pointers ("§5 shows X under Y"), not as activities ("we propose, we evaluate").
- Anticipate the obvious objection in-line, once, briefly: "unlike prior decoupled designs, no global stall is required because ...". Do not litigate every possible objection in the text; that is what the rebuttal window is for.
- Acronym hygiene: define at first use, and assume a reviewer from an adjacent subarea (a memory person reading your core paper) throughout.
Revision-friendliness is a 2026-cycle feature
Because ISCA's review process includes a revision phase (February 16 - March 6 in the 2026 cycle), write so the paper can absorb change: keep one results subsection per claim (swappable), avoid cross-references to "the previous paragraph", and keep 0.5 page of slack. A paper packed to the last line at submission has nowhere to put the experiment a reviewer asks for.
Self-edit gate before the deadline
[ ] Insight sentence appears, verbatim or nearly, in abstract and intro
[ ] Motivation section contains measured data, not only citations
[ ] Every added structure has a size; every policy has a trigger
[ ] Every headline number names baseline + workload + instrument
[ ] Figures legible printed at 100%; captions state takeaways
[ ] 0.5 page of revision slack preserved
[ ] References complete and NOT anonymized (2026 rule: never blind references)Format numbers verified 2026-07-08 against the ISCA 2026 guidelines
(../../resources/official-source-map.md); the 2027 template and limits are 待核实
until the new site posts them.
© 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 ISCA-Skills/skills/isca-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Isca 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 |
|---|---|---|---|---|---|---|
| Isca Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | 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 Isca Writing Style
What does Isca Writing Style do?
A skill your agent uses when drafting or revising an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing…. Isca Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing mechanisms at reviewer-checkable precision with figures that carry the design, and keeping quantitative claims calibrated to the instrument behind them.
When should I use Isca Writing Style?
Isca Writing Style fits situations like: revising an ISCA papers prose — organizing 11 pages around one architectural insight; writing the motivation section from measured data; describing mechanisms at reviewer-checkable precision with figures that carry the design; keeping quantitative claims calibrated to the instrument behind them.
How do I install Isca Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-writing-style -a claude-code`. Or copy the skill folder (ISCA-Skills/skills/isca-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/isca-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Isca Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-writing-style -a codex`. Or copy the skill folder (ISCA-Skills/skills/isca-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/isca-writing-style in your project. Codex loads it when a task matches its description.
Can I use Isca 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 isca-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/isca-writing-style, .gemini/skills/isca-writing-style, .github/skills/isca-writing-style and .opencode/skills/isca-writing-style in your project.
What does Isca Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Isca Writing Style is instructions for the agent only.
Does Isca 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 Isca 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 Isca Writing Style use?
Isca 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 Isca Writing Style use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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 Isca Writing Style?
Skills that share tags, products or a category with Isca 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 Isca 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.