Writing Style
pydantic/monty
How to write prose that reads like human technical documentation rather than LLM output.
Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose.
Install Writing Style
$ npx skills add marin-community/marin --skill writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install marin-community/marin 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/marin-community/marin.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/marin-community/marin/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/marin-community/marin/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 marin-community/marin --skill writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install marin-community/marin writing-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marin-community/marin.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/marin-community/marin/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 marin-community/marin --skill writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install marin-community/marin writing-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marin-community/marin.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/marin-community/marin/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/marin-community/marin.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 marin-community/marin --skill writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install marin-community/marin writing-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marin-community/marin.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/marin-community/marin/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 marin-community/marin 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 marin-community/marin --skill writing-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/marin-community/marin.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/marin-community/marin/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 marin-community/marin --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 marin-community/marin writing-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marin-community/marin.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/marin-community/marin/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
- 3.9k
- Token cost
- ~549 tokens
- SKILL.md length
- 260 words
- Files
- 9
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose.
- Tasks that involve Brand voice and tone
- SKILL.md covers Read The Right File, Voice, On Voice and Evidence and scope, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Pull requests
What it does
Writing Style is an agent skill from marin-community/marin. Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose.
Its SKILL.md is about 550 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 Development, covering Brand voice and tone and Pull requests. It works with Discord. The repository describes itself as: Open-source framework for the research and development of foundation models. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Brand voice and tone
- Tasks that involve Pull requests
Example prompts
- “/writing-style”
What it can do on your machine
Read from SKILL.md and the folder at commit c468793. 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 549 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 260 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 marin-community/marin at commit c468793, republished under its Apache-2.0 licence (© marin-community). 260 words, ~549 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
- Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose.
Marin House Style
Read the medium-specific guide for the deliverable, then apply ai-writing-donts.md as the final prose pass.
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.
- If a piece spans media, use the stricter applicable rule.
Voice
Write as a rigorous open-science lab building foundation models. Treat experiments, decisions, and mistakes as part of the record. Use a sober, practical voice for technically capable peers. Be natural and direct; use specialized language when it improves precision.
On Voice
These rules are stricter for agents. Preserve harmless human flourishes when editing another person's prose.
Evidence and scope
- Lead with the result, decision, or changed behavior.
- Support claims with numbers, examples, observations, and relevant artifacts.
- State uncertainty and limitations plainly; do not imply broader evidence.
- Remove hype, product-announcement language, AGI speculation, decorative emoji, and adjectives standing in for evidence.
- Explain non-standard terms. Add detail only when it helps the reader reproduce, evaluate, or act.
Add Structure For Longer-Form Writing
Long-form pieces may need a document-level TL;DR and section takeaways. Do not force them into short media.
Before publishing, confirm the prose is factually current, sounds normal when spoken to a colleague, cites material evidence, and contains no generic filler.
© marin-community, 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 marin-community/marin.
- 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 c468793
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 skillmarin-community/marin | 3.9k | — | ~549 | Automated safety check: Pass | Apache-2.0 | |
| Writing Stylepydantic/monty | 8.6k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Maintain DisCatSharpAiko-IT-Systems/DisCatSharp | 140 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Docs ReviewMicrock/ordinary-claude-skills | 404 | 2 repos | ~1.8k | Automated safety check: Notes | Custom licence | |
| GitHub Voicetobihagemann/turbo | 408 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Writing Styleopen-thoughts/OpenThoughts-Agent | 301 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Maintain DisCatSharp
Aiko-IT-Systems/DisCatSharp
Guides changes to the DisCatSharp C# Discord library: tracing a payload field through parsing, serialization and caches, then validating across target frameworks.
Docs Review
Microck/ordinary-claude-skills
Review documentation changes for compliance with the Metabase writing style guide.
GitHub Voice
tobihagemann/turbo
Shared writing style rules for GitHub-facing output (PR comments, PR descriptions, PR titles, issues, design proposals).
Writing Style
open-thoughts/OpenThoughts-Agent
Marin house writing style. An agent skill from open-thoughts/OpenThoughts-Agent.
Writer
rileyhilliard/claude-essentials
Writing style and tone guide for human-sounding content. An agent skill from rileyhilliard/claude-essentials.
More from marin-community/marin
All 41 skills in this repoNoslop
marin-community/marin
Deslop, simplify, or review low-value tests and prose only when explicitly requested for a branch or diff.
Use Iris
marin-community/marin
Use Iris to submit, inspect, debug, monitor, or recover jobs and tasks; diagnose scheduling and federation; deploy controllers; or reserve dev GPUs and TPUs.
Launch Rl
marin-community/marin
Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.
Marina Applet
marin-community/marin
Build, validate, publish, update, inspect, query, roll back, or archive a dynamic Marina applet.
Query Finelog
marin-community/marin
Query Finelog logs and telemetry for Iris tasks, workers, profiles, training, vLLM, and cross-cluster forwarding.
Trace Pulumi Diff
marin-community/marin
Run a read-only preview for a specified Marin infra/pulumi stack and trace each pending resource change to merged pull requests since its latest successful update when that update records a clean…
Related
Works with
Categories
Questions about Writing Style
What does Writing Style do?
Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose. Writing Style is an agent skill from marin-community/marin. Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose.
When should I use Writing Style?
Writing Style fits situations like: tasks that involve Brand voice and tone; tasks that involve Pull requests.
How do I install Writing Style in Claude Code?
Run `npx skills add marin-community/marin --skill writing-style -a claude-code`. Or copy the skill folder (.agents/skills/writing-style in marin-community/marin) 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 marin-community/marin --skill writing-style -a codex`. Or copy the skill folder (.agents/skills/writing-style in marin-community/marin) 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 marin-community/marin --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 549 tokens (SKILL.md is roughly 2.2k 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 (pydantic/monty, 8.6k stars), Maintain DisCatSharp (Aiko-IT-Systems/DisCatSharp, 140 stars), Docs Review (Microck/ordinary-claude-skills, 404 stars) and GitHub Voice (tobihagemann/turbo, 408 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Style?
marin-community (a GitHub organization) maintains it in marin-community/marin, which has 3,921 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 10, 2026.
Source: marin-community/marin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.