New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Writing Style

by umputun in umputun/cc-thingz

A skill your agent uses for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages.

MITAuto-check passedDevelopment

Install Writing Style

skills CLI
$ npx skills add umputun/cc-thingz --skill writing-style -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install umputun/cc-thingz writing-style --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/umputun/cc-thingz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/review/skills/writing-style .claude/skills/writing-style && rm -rf skills-src

Use ~/.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/

Facts

Skill name
writing-style
GitHub stars
485
Token cost
~1.3k tokens
SKILL.md length
659 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages.

  • Works in 2 steps: Check CLAUDE.md files (project-level and… → Check if the user has a custom…
  • Technical communication - GitHub/GitLab tickets
  • SKILL.md covers User Override Check, Exceptions - Use proper…, Brevity and Directness and Honest and Direct Feedback, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Writing Style is an agent skill from umputun/cc-thingz. Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Brand voice and tone, Commit messages and Blog and article writing. It works with GitHub and GitLab. The repository describes itself as: various things for claude code. The licence is MIT.

When your agent uses it

  • Technical communication - GitHub/GitLab tickets
  • PR/MR descriptions
  • Code review comments
  • Commit messages

Example prompts

  • “/writing-style”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Check CLAUDE.md files (project-level and user-level) for writing style sections (look for "writing style", "communication style", "tone"…
  2. Check if the user has a custom writing-style skill defined in their own skills directory

What it can do on your machine

Read from SKILL.md and the folder at commit 99e1c8d. 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 58 tokens; SKILL.md has 659 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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 umputun/cc-thingz at commit 99e1c8d, republished under its MIT licence (© umputun). 659 words, ~1,338 tokens.

Download SKILL.mdSave it as .claude/skills/writing-style/SKILL.md (or your agent's skills folder).
name
writing-style
description
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.

Technical Communication Style Guide

User Override Check

Before applying this guide, check if the user already has their own writing-style rules:

  1. Check CLAUDE.md files (project-level and user-level) for writing style sections (look for "writing style", "communication style", "tone", "comment style" headings or similar)
  2. Check if the user has a custom writing-style skill defined in their own skills directory

If user-defined writing rules exist: defer to those rules entirely. Do not apply this guide. Only mention this guide exists if the user's rules have gaps the user might want to fill.

If no user-defined rules exist: apply this guide as the default.

USE THIS STYLE FOR:

  • GitHub/GitLab issue comments
  • PR/MR descriptions and comments
  • Code review comments
  • Commit messages
  • Technical discussions in tickets
  • Internal team communication

Exceptions - Use proper English instead for:

  • README.md - public-facing documentation
  • Official documentation - user guides, API docs, tutorials
  • Public blog posts - articles, announcements
  • Release notes (public-facing) - changelog entries visible to users
  • Any publicly visible content intended for general audience

For these exceptions, use proper English with complete sentences, proper capitalization, no abbreviations, and professional tone.

Core Principles

Brevity and Directness

  • Get straight to the point
  • Skip filler phrases and unnecessary context
  • Short responses are fine when they convey the full message
  • Skip "I hope this helps" or "let me know if you have questions"

Honest and Direct Feedback

  • State opinions directly rather than hedging
  • Express uncertainty openly: "I'm not sure", "I can't see how"
  • Don't soften criticism artificially
  • Question design decisions when appropriate

Problem-Solution Structure

  • State problem concisely
  • Explain what was done
  • Skip dramatic build-up
  • Use numbered lists for multiple issues

Format:

[brief problem statement]

[what was changed/fixed]

Technical Precision

  • Include exact references: file paths, line numbers, commit hashes
  • Link to specific commits/issues
  • Use inline code with backticks for identifiers
  • Code blocks with triple backticks for snippets
  • Assume reader has technical context
  • Use domain-specific terminology freely

Code Review Comments

  • Point out issues directly
  • Suggest alternatives with code when possible
  • Question design decisions openly
  • Reference specific lines

Questions and Answers

  • Direct yes/no when possible
  • Brief explanation after
  • Don't restate the question
Show full SKILL.md (321 more words)Show less

AI-Typical Language to Avoid

AI-generated text has recognizable patterns. Avoid these to sound natural:

Filler phrases (delete entirely):

  • "It's important to note that..."
  • "It's worth mentioning..."
  • "In order to..." - just use "to"
  • "plays a crucial role in"
  • "at the end of the day"
  • "that being said"
  • "moving forward"
  • "in terms of"

Overused AI words (use simpler alternatives):

  • "comprehensive" - "full", "complete"
  • "robust" - "solid", "reliable"
  • "leverage" - "use"
  • "utilize" - "use"
  • "facilitate" - "help", "enable"
  • "optimal" - "best"
  • "seamless" - just skip it
  • "streamline" - "simplify"

Abstract nouns (convert to verbs):

  • "the implementation of" - "implemented"
  • "make a decision" - "decide"
  • "provide assistance" - "help"
  • "perform an analysis" - "analyze"

Hedging phrases (be direct instead):

  • "I think maybe we could consider..." - state opinion directly
  • "It would seem that..." - state the fact
  • "Perhaps it might be worth..." - suggest directly

Excessive transitions (use sparingly):

  • "Furthermore..." - "also" or just continue
  • "Additionally..." - "also" or skip
  • "Moreover..." - usually unnecessary
  • "In conclusion..." - just conclude

Meta-commentary (delete):

  • "This approach works by..." - just describe what it does
  • "The benefit of this is..." - state the benefit directly
  • "What this means is..." - just say it

What NOT to Do

Don't use:

  • "Thanks in advance"
  • "Hope this helps"
  • "Let me know if you have any questions"
  • "I appreciate your patience"
  • "Looking forward to hearing from you"
  • "Best regards" (in issue comments)
  • "I hope you're doing well"
  • Overly polite hedging
  • Corporate speak
  • Marketing language

Markdown Formatting

  • Inline code: like this
  • Code blocks: ```language
  • Links: text
  • Bold: text for emphasis
  • Italic: text for side notes
  • Lists with - or 1.

Application Summary

  1. Be concise - fewer words is better
  2. Be direct - no hedging unless genuinely uncertain
  3. Be honest - say when you don't know or disagree
  4. Be precise - reference commits, files, lines
  5. Avoid AI-speak - no "comprehensive", "leverage", "facilitate", "in order to"
  6. Skip boilerplate - no pleasantries, no sign-offs in technical comments

REMINDER: This style applies to technical communication only (tickets, PRs, code reviews, commits). Use proper English for README.md, public docs, and blog posts.

© umputun, 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 plugins/review/skills/writing-style of umputun/cc-thingz.

Open the folder on GitHubat commit 99e1c8d

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.

Writing Style compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Writing Style this skillumputun/cc-thingz485—~1.3kAutomated safety check: PassMIT
Writewaynesutton/markdown-site627—~3kAutomated safety check: PassMIT
Writerrileyhilliard/claude-essentials130—~2kAutomated safety check: PassMIT
Agent Stylepchalasani/claude-code-tools2k—~1.4kAutomated safety check: PassMIT
No TropesOutThisLife/brooklyn-skills199—~455Automated safety check: PassMIT
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Write

    waynesutton/markdown-site

    Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation.

    627 GitHub stars~3k tokensUpdated 4 mo ago
    Writing & ContentAuto-check passed

  • Writer

    rileyhilliard/claude-essentials

    Writing style and tone guide for human-sounding content. An agent skill from rileyhilliard/claude-essentials.

    130 GitHub stars~2k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • Agent Style

    pchalasani/claude-code-tools

    Literature-backed English technical-prose writing rules (agent-style, 21 rules).

    2k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • No Tropes

    OutThisLife/brooklyn-skills

    Detect and eliminate common AI writing tropes from generated text.

    199 GitHub stars~455 tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Debate Review

    amElnagdy/review-skills

    Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed.

    132 GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

More from umputun/cc-thingz

All 16 skills in this repo

  • Exec

    umputun/cc-thingz

    Execute plan tasks sequentially using subagents. An agent skill from umputun/cc-thingz.

    485 GitHub stars~8k tokensUpdated 4 days ago
    Auto-check passed

  • New

    umputun/cc-thingz

    A skill your agent uses when user asks to create a release, cut a release, or publish a version.

    485 GitHub stars~1.9k tokensUpdated 4 days ago
    Auto-check: notes

  • Root Cause Investigator

    umputun/cc-thingz

    Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology.

    485 GitHub stars~879 tokensUpdated 4 days ago
    Auto-check passed

  • Ask Codex

    umputun/cc-thingz

    Consult OpenAI Codex for investigation, debugging, or code review.

    485 GitHub stars~2.6k tokensUpdated 4 days ago
    Auto-check: notes

  • Backlog

    umputun/cc-thingz

    Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item.

    485 GitHub stars~3.4k tokensUpdated 4 days ago
    Auto-check: notes

  • Brainstorm

    umputun/cc-thingz

    Use before any creative work or significant changes. An agent skill from umputun/cc-thingz.

    485 GitHub stars~1.7k tokensUpdated 4 days ago
    Auto-check: notes

Works with

Categories

Questions about Writing Style

What does Writing Style do?

A skill your agent uses for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Writing Style is an agent skill from umputun/cc-thingz. Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages.

When should I use Writing Style?

Writing Style fits situations like: technical communication - GitHub/GitLab tickets; PR/MR descriptions; code review comments; commit messages.

How do I install Writing Style in Claude Code?

Run `npx skills add umputun/cc-thingz --skill writing-style -a claude-code`. Or copy the skill folder (plugins/review/skills/writing-style in umputun/cc-thingz) 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 umputun/cc-thingz --skill writing-style -a codex`. Or copy the skill folder (plugins/review/skills/writing-style in umputun/cc-thingz) 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 umputun/cc-thingz --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 MIT 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: Write (waynesutton/markdown-site, 627 stars), Writer (rileyhilliard/claude-essentials, 130 stars), Agent Style (pchalasani/claude-code-tools, 2k stars) and No Tropes (OutThisLife/brooklyn-skills, 199 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Writing Style?

umputun (a GitHub user) maintains it in umputun/cc-thingz, which has 485 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 5, 2026.

Source: umputun/cc-thingz on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.