Writing Style
umputun/cc-thingz
A skill your agent uses for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages.
Marin house writing style. An agent skill from open-thoughts/OpenThoughts-Agent.
Install Writing Style
$ npx skills add open-thoughts/OpenThoughts-Agent --skill writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install open-thoughts/OpenThoughts-Agent 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/open-thoughts/OpenThoughts-Agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-style .claude/skills/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 "writing-style" agent skill from https://github.com/open-thoughts/OpenThoughts-Agent/tree/main/.agents/skills/writing-style into .claude/skills/writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/open-thoughts/OpenThoughts-Agent/tree/main/.agents/skills/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 open-thoughts/OpenThoughts-Agent --skill writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install open-thoughts/OpenThoughts-Agent writing-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-thoughts/OpenThoughts-Agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/writing-style .agents/skills/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 "writing-style" agent skill from https://github.com/open-thoughts/OpenThoughts-Agent/tree/main/.agents/skills/writing-style into .agents/skills/writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 open-thoughts/OpenThoughts-Agent --skill writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install open-thoughts/OpenThoughts-Agent writing-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-thoughts/OpenThoughts-Agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/writing-style .cursor/skills/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 "writing-style" agent skill from https://github.com/open-thoughts/OpenThoughts-Agent/tree/main/.agents/skills/writing-style into .cursor/skills/writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/open-thoughts/OpenThoughts-Agent.git --path .agents/skills/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 open-thoughts/OpenThoughts-Agent --skill writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install open-thoughts/OpenThoughts-Agent writing-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-thoughts/OpenThoughts-Agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/writing-style .gemini/skills/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 "writing-style" agent skill from https://github.com/open-thoughts/OpenThoughts-Agent/tree/main/.agents/skills/writing-style into .gemini/skills/writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 open-thoughts/OpenThoughts-Agent 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 open-thoughts/OpenThoughts-Agent --skill writing-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/open-thoughts/OpenThoughts-Agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/writing-style .github/skills/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 "writing-style" agent skill from https://github.com/open-thoughts/OpenThoughts-Agent/tree/main/.agents/skills/writing-style into .github/skills/writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 open-thoughts/OpenThoughts-Agent --skill 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 open-thoughts/OpenThoughts-Agent writing-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-thoughts/OpenThoughts-Agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/writing-style .opencode/skills/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 "writing-style" agent skill from https://github.com/open-thoughts/OpenThoughts-Agent/tree/main/.agents/skills/writing-style into .opencode/skills/writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
writing-style- GitHub stars
- 301
- Token cost
- ~1.3k tokens
- SKILL.md length
- 709 words
- Files
- 9
- Skills in repo
- 44
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Marin house writing style. An agent skill from open-thoughts/OpenThoughts-Agent.
- Revising Marin-authored prose
- SKILL.md covers Read The Right File, Hold The Marin Positioning, Keep The Core Vibe and On Voice, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Including commit messages and GitHub PR
What it does
Writing Style is an agent skill from open-thoughts/OpenThoughts-Agent. Marin house writing style. Use when drafting or revising Marin-authored prose, including commit messages and GitHub PR, issue, or comment text.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `ai-writing-donts.md`, `blog-posts.md` and `discord.md`).
It sits in Writing & Content, covering Brand voice and tone and Commit messages. It works with GitHub and Discord. The repository describes itself as: Data recipes and robust infrastructure for training AI agents. The licence is Apache-2.0.
When your agent uses it
- Revising Marin-authored prose
- Including commit messages and GitHub PR
Example prompts
- “/writing-style”
What it can do on your machine
Read from SKILL.md and the folder at commit 3bd1917. 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
Writing Style loads about 1.3k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 709 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 open-thoughts/OpenThoughts-Agent at commit 3bd1917, republished under its Apache-2.0 licence (© open-thoughts). 709 words, ~1,340 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-style/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- writing-style
- description
- Marin house writing style. Use when drafting or revising Marin-authored prose, including commit messages and GitHub PR, issue, or comment text.
<!-- Vendored from marin-community/marin-style v0.3.0 — do not edit; re-run `marin-style sync`. -->Marin House Style
Start here for any non-trivial Marin-authored text. This file is the common layer; then read the medium-specific file that matches the deliverable.
Read The Right File
- Read blog-posts.md for public explainers and blog posts.
- Read reports.md for technical reports aimed at peer researchers outside Marin.
- Read tutorials.md for learning-oriented documentation that introduces Marin.
- Read reference-docs.md for precise usage docs aimed at readers who already know Marin.
- Read issues.md for standard OSS issues and experiment issues.
- Read pull-requests.md for commit messages and PR titles and bodies.
- Read discord.md for Discord summaries and tactical replies.
- Read ai-writing-donts.md for the final prose-only review pass that strips generic AI-writing patterns.
- Apply this file first, then apply the medium-specific file. If a piece spans multiple media, keep the stricter rule.
Hold The Marin Positioning
- Write from the stance of a rigorous, open-science lab building frontier-level foundation models.
- Treat process as part of the work. Experiments, decisions, and mistakes all belong in the record.
- Let the work speak. Do not substitute tone for evidence.
Keep The Core Vibe
- Be sober, not flashy.
- Project quiet confidence.
- Keep an open door, not a megaphone.
- Stay practical and hands-on.
- Aim to be helpful and respectful.
- Assume a baseline familiarity with ML systems.
- Don’t dilute discussions to accommodate every level of experience. (Different media will be intended for different levels of experience.)
- Don’t be overly formal; write like a technical peer, not an academic paper or a product blog.
- Use technical language where it helps, but keep the tone natural and direct.
On Voice
The above defines the default voice; we allow some flexibility by author. These rules are stricter for agent-written text than for human-written text.
Researchers need not suppress their own voice. Some personality is fine, especially in retrospectives, blog posts, and narrative writeups, as long as the writing stays concrete, honest, and technically disciplined.
Agents should err toward more discipline. When reviewing human prose, allow deviations and flourishes that do not conflict with core Marin values.
Enforce Hard Rules
- Remove hype, marketing copy, and launch-tweet energy.
- Use emoji very sparingly: for communication, not flair.
- Remove grand claims that outrun the evidence.
- Avoid AGI rhetoric and speculation.
- Avoid adjectives that try to do the work of numbers.
- If a sentence sounds like a product announcement, rewrite it.
Show full SKILL.md (327 more words)Show less
Follow The Writing Principles
- Show results instead of claiming them. Prefer concrete numbers, examples, and observed behavior.
- Prefer the simplest framing that is still correct.
- State uncertainty plainly. Use phrases like
we think,preliminary results suggest, orthis seems to break down when...when warranted. - Treat the reader as a capable collaborator. Do not condescend or over-explain basics.
- Default to transparency. Include what worked, what failed, what surprised you, and what you would try next.
- Cite the relevant prior work and artifacts. This includes Marin experiments, reports, issues, PRs, papers, and other external work when they materially inform the piece.
Add Structure For Longer-Form Writing
For longer-form writing, include an easy-to-scan doc-level TL;DR near the top.
For longer-form writing, add section-level takeaway lines or short TL;DRs where they help readers navigate.
Do not force these patterns into short-form media that do not benefit from them.
Set Audience By Default
- Assume the reader works in ML or LLMs unless the medium says otherwise.
- Do not assume deep specialization by default.
- Introduce non-standard terms before using them heavily.
- Add detail only when it helps the reader reproduce, evaluate, or act.
Use Sentence-Level Defaults
- Prefer short, direct sentences.
- Lead with the result or takeaway.
- Follow with method or explanation.
- End with caveats, limits, or open questions when needed.
- Prefer phrases like
we found,this suggests,in practice, andone limitation is. - Avoid phrases like
clearly,obviously,groundbreaking, andstate-of-the-artunless you define and defend them.
Review For AI-Writing Tells
Do one editing pass that looks only for generic, over-smoothed, LLM-sounding prose. Then apply ai-writing-donts.md as the detailed checklist for what to remove or rewrite.
Run A Quick Self-Check
- Did you include concrete evidence?
- Did you remove hype language?
- Would this sound normal spoken aloud to a colleague?
- Did you overstate certainty or scope?
- Did you remove generic AI-writing templates and filler?
Keep The One-Line Summary
Write clearly, honestly, and with enough evidence for the work to stand on its own.
© open-thoughts, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files in .agents/skills/writing-style of open-thoughts/OpenThoughts-Agent.
- SKILL.md
- ai-writing-donts.md
- blog-posts.md
- discord.md
- issues.md
- pull-requests.md
- reference-docs.md
- reports.md
- tutorials.md
Open the folder on GitHubat commit 3bd1917
Compare with similar skills
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 |
|---|---|---|---|---|---|---|
| Writing Style this skillopen-thoughts/OpenThoughts-Agent | 301 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Writing Styleumputun/cc-thingz | 484 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Subwave Discord Releaseperminder-klair/subwave | 1.4k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Agent Journal and Issue Repliesyologdev/yoyo-evolve | 1.9k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Writewaynesutton/markdown-site | 628 | — | ~3k | Automated safety check: Pass | MIT | |
| Writerrileyhilliard/claude-essentials | 130 | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Subwave Discord Release
perminder-klair/subwave
Draft a Discord release announcement for SUB/WAVE from a release PR, tag, or version number.
Agent Journal and Issue Replies
yologdev/yoyo-evolve
Sets a warm, plain-spoken voice for an agent's journal entries and GitHub issue replies, with rules on openings, jargon, honesty and endings.
Write
waynesutton/markdown-site
Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation.
Writer
rileyhilliard/claude-essentials
Writing style and tone guide for human-sounding content. An agent skill from rileyhilliard/claude-essentials.
Agent Style
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
More from open-thoughts/OpenThoughts-Agent
All 44 skills in this repoAnalyze Dataset Token Length
open-thoughts/OpenThoughts-Agent
Analyze the token length of an OT-Agent conversation-format (ShareGPT-style) dataset — the per-trace distribution (median/p90/max) and/or counts under a token threshold + a metadata predicate (e.g.
Analyze Id Eval Ranking
open-thoughts/OpenThoughts-Agent
Given a list of models (HF name stubs) that have valid agentic ID eval scores in Supabase, build a ranking table: raw per-benchmark accuracy on the 3 ID benchmarks (SWE-Bench-100…
Analyze Job History Iris
open-thoughts/OpenThoughts-Agent
Run the Iris harbor job-history analyzer (scripts/iris/analyzeirisharborjob.py) on a datagen/eval job and read its JSON sidecar for trustworthy throughput / preemption / productive-trial stats.
Analyze Rl Behavior
open-thoughts/OpenThoughts-Agent
Run the full RL behavioral-analysis pipeline (scripts/analysis/analyzerlbehavior.py) on a trained RL model to understand WHAT changed vs its pre-RL baseline, WHY, whether it PERSISTS, and its EVAL…
Analyze Training Run Iris
open-thoughts/OpenThoughts-Agent
Detailed health check for a Levanter/executor TRAINING run on the marin Iris cluster (e.g.
Code Create Staged Plan
open-thoughts/OpenThoughts-Agent
DESIGN a non-trivial codebase change (Harbor / MarinSkyRL / vLLM / OT-Agent / LLaMA-Factory) as a dependency-ordered STAGED PLAN before writing code — a feature port, a multi-step fix with parity…
Related
Categories
Questions about Writing Style
What does Writing Style do?
Marin house writing style. An agent skill from open-thoughts/OpenThoughts-Agent. Writing Style is an agent skill from open-thoughts/OpenThoughts-Agent. Marin house writing style.
When should I use Writing Style?
Writing Style fits situations like: revising Marin-authored prose; including commit messages and GitHub PR.
How do I install Writing Style in Claude Code?
Run `npx skills add open-thoughts/OpenThoughts-Agent --skill writing-style -a claude-code`. Or copy the skill folder (.agents/skills/writing-style in open-thoughts/OpenThoughts-Agent) into .claude/skills/writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Writing Style in Codex?
Run `npx skills add open-thoughts/OpenThoughts-Agent --skill writing-style -a codex`. Or copy the skill folder (.agents/skills/writing-style in open-thoughts/OpenThoughts-Agent) into .agents/skills/writing-style in your project. Codex loads it when a task matches its description.
Can I use 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 open-thoughts/OpenThoughts-Agent --skill 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/writing-style, .gemini/skills/writing-style, .github/skills/writing-style and .opencode/skills/writing-style in your project.
What does Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Style is instructions for the agent only.
Does 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 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 Writing Style use?
Writing Style is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Writing Style use?
About 1.3k tokens (SKILL.md is roughly 5.4k 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 Writing Style?
Skills that share tags, products or a category with Writing Style: Writing Style (umputun/cc-thingz, 484 stars), Subwave Discord Release (perminder-klair/subwave, 1.4k stars), Agent Journal and Issue Replies (yologdev/yoyo-evolve, 1.9k stars) and Write (waynesutton/markdown-site, 628 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Style?
open-thoughts (a GitHub organization) maintains it in open-thoughts/OpenThoughts-Agent, which has 301 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on September 28, 2026.
Source: open-thoughts/OpenThoughts-Agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.