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.
A skill your agent uses when revising an ICLR manuscript for learning-representation framing, OpenReview readability, contribution clarity, limitations, ethics, and reviewer navigation.
Install Iclr Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-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/ICLR-Skills/skills/iclr-writing-style .claude/skills/iclr-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 "iclr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-writing-style into .claude/skills/iclr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-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/ICLR-Skills/skills/iclr-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 iclr-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-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/ICLR-Skills/skills/iclr-writing-style .agents/skills/iclr-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 "iclr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-writing-style into .agents/skills/iclr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-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 iclr-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-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/ICLR-Skills/skills/iclr-writing-style .cursor/skills/iclr-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 "iclr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-writing-style into .cursor/skills/iclr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-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 ICLR-Skills/skills/iclr-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 iclr-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iclr-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/ICLR-Skills/skills/iclr-writing-style .gemini/skills/iclr-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 "iclr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-writing-style into .gemini/skills/iclr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-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 iclr-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 iclr-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/ICLR-Skills/skills/iclr-writing-style .github/skills/iclr-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 "iclr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-writing-style into .github/skills/iclr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-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 iclr-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 iclr-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/ICLR-Skills/skills/iclr-writing-style .opencode/skills/iclr-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 "iclr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICLR-Skills/skills/iclr-writing-style into .opencode/skills/iclr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iclr-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
iclr-writing-style- GitHub stars
- 1.2k
- Token cost
- ~907 tokens
- SKILL.md length
- 400 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 ICLR manuscript for learning-representation framing, OpenReview readability, contribution clarity, limitations, ethics, and reviewer navigation.
- Revising an ICLR manuscript for learning-representation framing
- SKILL.md covers ICLR framing, Reviewer navigation, Framing that survives public… and Worked vignette, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- OpenReview readability
What it does
Iclr Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ICLR manuscript for learning-representation framing, OpenReview readability, contribution clarity, limitations, ethics, and reviewer navigation. Use when the core representation insight is buried, when an abstract must read well as an OpenReview snippet, or when adding a "what to verify" path so reviewers can confirm the claim under permanent public review.
Its SKILL.md is about 910 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 and Plain language and style rules. 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 ICLR manuscript for learning-representation framing
- OpenReview readability
- Contribution clarity
- Reviewer navigation
Example prompts
- “what to verify”
- “/iclr-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
Iclr Writing Style loads about 907 tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 400 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). 400 words, ~907 tokens.
Download SKILL.mdSave it as
.claude/skills/iclr-writing-style/SKILL.md (or your agent's skills folder).- name
- iclr-writing-style
- description
- Use when revising an ICLR manuscript for learning-representation framing, OpenReview readability, contribution clarity, limitations, ethics, and reviewer navigation. Use when the core representation insight is buried, when an abstract must read well as an OpenReview snippet, or when adding a "what to verify" path so reviewers can confirm the claim under permanent public review.
ICLR Writing Style
Use this to turn a technically correct draft into an ICLR-readable paper. The style should make the learning-representation contribution easy to evaluate under public review.
ICLR framing
- State the representation, learning problem, or model-behavior insight in the first page.
- Make clear whether the contribution is method, theory, benchmark, analysis, dataset, evaluation, systems support, or application-driven ML.
- Explain why the result changes how the community should train, evaluate, understand, or deploy learning systems.
- Avoid hiding the core idea behind implementation detail or benchmark trivia.
- Connect limitations to real deployment, robustness, safety, fairness, or data constraints when those issues are relevant.
Reviewer navigation
- Give reviewers a short "what to verify" path: main theorem, key ablation, benchmark setting, reproducibility artifact, or appendix section.
- Use figure captions as mini-arguments, not labels.
- Keep notation local and consistent; ICLR reviewers span subfields.
- Use the appendix to answer predictable objections, but do not move decisive evidence out of the main narrative.
- Write the abstract and introduction so the paper still makes sense when read through OpenReview snippets and search.
Framing that survives public skimming
On OpenReview a reader meets your paper as a title, a TL;DR, and an abstract snippet before opening the PDF, and the discussion thread is attached forever. The first page must carry the representation insight unaided.
| Prose risk | ICLR-tuned rewrite | Why it matters under public review |
|---|---|---|
| Insight hidden behind setup | Lead with what changes about representations | Snippet readers never reach page 3 |
| Vague contribution type | Name it: method/theory/analysis/benchmark | Reviewers route papers by type |
| Overclaimed generality | Scope to the tested regime | Public thread will surface the gap |
| Caption as label | Caption as a mini-argument | Reviewers read figures before text |
Show full SKILL.md (122 more words)Show less
Worked vignette
A draft on a new optimizer opens with three paragraphs of background before stating that the method reduces gradient variance in deep nets. Rewritten, the first sentence names the phenomenon and the fix, the introduction labels the contribution as "optimization analysis plus method," and a "what to verify" line points reviewers to the variance-reduction ablation in Section 4. The abstract is trimmed so its first 40 words stand alone as an OpenReview TL;DR.
Reviewer-pushback patterns
- "I cannot find the contribution." Put the representation insight in sentence one of the abstract.
- "Claim is broader than the evidence." Scope the wording; the public thread punishes overclaims.
- "Notation is inconsistent." Keep it local; ICLR reviewers span subfields and will flag drift.
Output format
[ICLR fit sentence] <one sentence>
[First-page problem] <what is hard or missing>
[Contribution type] method / theory / benchmark / analysis / data / systems / application
[Navigation fixes] <intro, figures, claims, appendix map>
[Risky prose] <overclaim, unclear novelty, unsupported generalization>© 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 ICLR-Skills/skills/iclr-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iclr 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 |
|---|---|---|---|---|---|---|
| Iclr Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~907 | Automated safety check: Pass | MIT | |
| UX Writingcontent-designer/ux-writing-skill | 224 | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Blog PersonaAgriciDaniel/claude-blog | 2.3k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Writing Style ReviewArmDeveloperEcosystem/arm-learning-paths | 154 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Readability Guidancetestdouble/han | 281 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Writing StyleOpenLAIR/dr-claw | 1.2k | — | ~2.4k | Automated safety check: Pass | CC-BY-4.0 |
Similar skills
Blog Persona
AgriciDaniel/claude-blog
Create and manage writing personas with NNGroup 4-dimension tone framework (Funny-Serious, Formal-Casual, Respectful-Irreverent, Enthusiastic-Matter-of-fact).
Writing Style Review
ArmDeveloperEcosystem/arm-learning-paths
Review and improve writing style, voice, tone, readability, inclusive language, Arm terminology, heading style, word choice, and AI-sounding prose in Arm Learning Paths and install guides.
Readability Guidance
testdouble/han
Surfaces Han's shared Human-Readable Output Standard — the readability rule and the writing-voice profile — into the calling skill's own context, so the caller drafts in voice and runs its…
Writing Style
OpenLAIR/dr-claw
Apply the 21 prose rules from "The Elements of Agent Style" — 12 canonical rules (Strunk, Orwell, Pinker) plus 9 field-observed AI-output patterns.
Ahr Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of an American Historical Review (AHR) manuscript so it reads with clarity and authority for historians across all fields.
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 Iclr Writing Style
What does Iclr Writing Style do?
A skill your agent uses when revising an ICLR manuscript for learning-representation framing, OpenReview readability, contribution clarity, limitations, ethics, and reviewer navigation. Iclr Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ICLR manuscript for learning-representation framing, OpenReview readability, contribution clarity, limitations, ethics, and reviewer navigation.
When should I use Iclr Writing Style?
Iclr Writing Style fits situations like: revising an ICLR manuscript for learning-representation framing; openReview readability; contribution clarity; reviewer navigation.
How do I install Iclr Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-writing-style -a claude-code`. Or copy the skill folder (ICLR-Skills/skills/iclr-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iclr-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Iclr Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-writing-style -a codex`. Or copy the skill folder (ICLR-Skills/skills/iclr-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iclr-writing-style in your project. Codex loads it when a task matches its description.
Can I use Iclr 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 iclr-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/iclr-writing-style, .gemini/skills/iclr-writing-style, .github/skills/iclr-writing-style and .opencode/skills/iclr-writing-style in your project.
What does Iclr Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Iclr Writing Style is instructions for the agent only.
Does Iclr 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 Iclr 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 Iclr Writing Style use?
Iclr 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 Iclr Writing Style use?
About 907 tokens (SKILL.md is roughly 3.6k 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 Iclr Writing Style?
Skills that share tags, products or a category with Iclr Writing Style: UX Writing (content-designer/ux-writing-skill, 224 stars), Blog Persona (AgriciDaniel/claude-blog, 2.3k stars), Writing Style Review (ArmDeveloperEcosystem/arm-learning-paths, 154 stars) and Readability Guidance (testdouble/han, 281 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iclr 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.