writing-style

Write or edit long-form content in the practitioner's blog voice.

11|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill writing-style-thrawn01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-style
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/writing-style
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill writing-style-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write or edit writing in the user's practitioner blog voice — experience-backed, conversational, story-driven, opinionated but humble. Use for blog posts, tech specs, engineering communications, and any long-form writing the user asks for. Activated when the user asks to "write a post", "draft a blog", "write up X", "edit this for style", "review this for my style", or invokes /writing-style directly.

Core Features & Use Cases

  • Maintains the author's practitioner voice derived from their published posts, suitable for long-form content including blogs and technical docs.
  • Provides explicit voice, tone, and structural guidelines (sentence length, rhythm, transitions) to guide drafting and editing.
  • Supports prompts like "write a post" or "edit this for style" and can be invoked via the /writing-style command to load its style rules.

Quick Start

Draft a blog post in the practitioner's voice about the topic you specify.

Frequently Asked Questions about writing-style

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I edit my blog post to match my practitioner voice?

To edit your blog post for your practitioner voice, apply style guidelines that enforce an experience-backed, conversational, and story-driven tone. This refines long-form content to sound opinionated yet humble.

Can I draft long-form technical specs in a conversational tone?

Yes, you can draft technical specs in a conversational tone by applying structural directives that manage sentence length and rhythm. This transforms engineering communications into story-driven, experience-backed content.

What is the best way to write a blog post with an opinionated but humble style?

The best way to write a blog post with an opinionated but humble style is to apply explicit voice rules and structural guidelines. This maintains your practitioner tone while ensuring the content remains conversational.

Does this writing style tool work for engineering communications?

Yes, this writing style tool works for engineering communications by applying voice and tone guidelines to your drafts. It adapts technical content into a conversational, story-driven format suitable for long-form writing.

How do I review my technical writing for consistent voice and sentence rhythm?

You review technical writing for consistent voice and sentence rhythm by applying structural directives that evaluate transitions and sentence length. This process aligns your engineering communications with your established practitioner blog voice.