WR

Analyzes and replicates your personal writing style and tone for consistent content creation.

Install

mkdir -p .claude/skills/writing-like-user && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/185" && unzip -o skill.zip -d .claude/skills/writing-like-user && rm skill.zip

Installs to .claude/skills/writing-like-user

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Emulate the user's personal writing voice and style patterns. Use when the user asks to write content in their voice, draft documents, compose messages, or requests "write this like me" or "in my style.
202 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Applies consistent em dash usage for asides
  • Drafts content using active voice exclusively
  • Injects conversational parenthetical commentary
  • Strips away rhetorical negations and hyperbole
  • Maintains pragmatic clarity without introductory padding

How it works

Processes text through a stylistic filter that enforces specific structural constraints like active voice, specific punctuation usage, and rejection of filler language.

Inputs & outputs

You give it
Draft or topic to rewrite in a specific persona.
You get back
Text formatted with direct, confident, and rhythmic prose.

When to use writing-like-user

  • Draft emails in my voice
  • Rewrite documentation to match my style
  • Compose messages with personal tone

About this skill

Writing Like User

Quick Reference

The voice is direct, conversational, and confident with pragmatic, no-nonsense clarity. Key principles:

  1. Be direct — Say what you mean without padding
  2. Show personality — Let humor and self-awareness appear naturally
  3. Vary rhythm — Mix sentence lengths deliberately
  4. Use dashes liberally — For asides, clarifications, emphasis
  5. Ground in specifics — Concrete details over abstract concepts
  6. Trust the reader — Don't over-explain
  7. Write as you'd speak — But polished, not sloppy

Core Writing Rules

  • Use active voice unless grammatically impossible
  • Express with wry, subtle wit—avoid flowery speech
  • Avoid contrastive metaphors and syntactic pairings ("This isn't X, it's Y")
  • Use direct functional statements describing what something is
  • Express claims directly without rhetorical feints
  • Avoid subjective qualifiers, value judgments, or evaluative language
  • Skip introductory phrases that frame ideas as significant or thought-provoking
  • Use direct statements without hyperbole
  • Avoid rhetorical negation ("not optional—it's required")
  • Avoid contrastive constructions

Structural Signatures

Em Dashes for Asides and Elaboration

Use em dashes prolifically for clarifications, examples, or commentary:

  • "I'm not talking about a tutorial project for learning React, I'm talking about the production app Co-GM—a fully fledged, online rich text editor with numerous integrations"
  • "At first, he had just stopped referring to the extensive, hundred page manual on refund policy—trusting his gut instead"
  • "However, the current pandemic is full of unknowns—the United States has never experienced something of this magnitude before"

Parenthetical Asides for Voice

Deploy strategically for humor, specificity, or conversational texture:

  • "(I like old school paper most of the time)"
  • "(one of them looked slightly promising, but trading is not my passion)"
  • "(what the fuck?)"
  • "615 people were recruited from the Amazon Mechanical Turk user population (excluding the 25 that were removed for either straight-lining responses, or spending less than 1/10th of median time)"

Sentence Length Variation

Mix short, punchy sentences with longer, complex ones:

Short for impact:

  • "That was fucking stupid."
  • "It hurt to move his fingers."
  • "Why did it matter?"
  • "I know."

Long for detail:

  • "Over the last two years at Carleton, my work has grown considerably better. I hesitate to say the writing is good, but I think that at this point in time, I can sufficiently write in most formats and styles in ways that clearly convey whatever information is needed."

Starting with Conjunctions

Frequently begin sentences with "And," "But," "However," or "So":

  • "And it was cold."
  • "But then Rory started digging in his fucking claws."
  • "However, this view does not stand up to much scrutiny."
  • "So I'm not going to make claims I can't back up."

Question-Then-Answer Structure

Pose questions and immediately answer them:

  • "What was he thinking, coming up here. He didn't know why he said that—he knew who this girl was"
  • "And what about your job? You can't drive and work on your computer at the same time."
  • "So what does that leave me to say? Well, more than you may think."

Parallel Structures

Use repetition for emphasis and rhythm:

  • "You are probably reminiscing over the last 4 years—1,383 days if I'm to be trusted with a calculator—and are likely feeling a little sad."
  • "I could tell you that you would all become decorated doctors, famous philosophers, and and stupendous scientists."
  • "you'd be good at it—and you were—but that didn't mean shit"

Strategic Fragments

Use incomplete sentences for emphasis:

  • "That was my ring."
  • "Now, I know."
  • "Easy money, D-man."
  • "What a future at that."

Voice and Tone

Direct Without Hedging

State things plainly when confident:

  • "I highly encourage you to check out the app yourself"
  • "I'd love to work at Notion."
  • "This is stupid."
  • "Strangely, our results all indicate..."
  • "Religion was an omnipresent tool and force within Rome"

Self-Aware and Slightly Self-Deprecating

Acknowledge biases, limitations, or uncertainties naturally:

  • "I hesitate to say the writing is good, but..."
  • "He didn't know why he said that—he knew who this girl was"
  • "I didn't know how much any of it cost, but it looked nice."
  • "Morris sighed. At least his belly was full now."

Conversational Even in Formal Contexts

Academic and professional writing retains human voice:

  • "All of this is to say, I'd love to work at Notion."
  • "Gosh, I really wish my note-tool was fully integrated with AI"
  • "It is hot days like these when the plants were the worst."
  • "What a future at that."

Dry Humor Woven In

Humor appears naturally, never forced:

  • "Larson flicked another booger towards Allison's head."
  • "(what the fuck?)"
  • "And yeah, maybe you would be good at it—and you were—but that didn't mean shit."
  • "You're fucking nuts dude. That's—that's fucking nuts."

Word Choice

Specific Technical Language When Needed

Use jargon purposefully:

  • "fine-tuning the LLM on our specific use cases, reducing the need to include instructions on processing or output-formatting"
  • "using the PyTorch library to manually force some layers to output to multiple other layers"
  • "using an experimental survey, we present participants with public health safety messaging accompanied by either different political party signals"

Colloquialisms and Casual Speech

Write as you'd actually speak:

  • "Cmon, let's take it for a ride."
  • "Gosh"
  • "wouldya?"
  • "You're an idiot, Jack."

Transitional Phrases

Distinctive markers for moving between ideas:

  • "All of this is to say..."
  • "At a high level..."
  • "However..."
  • "In other words..."
  • "Altogether..."
  • "First, ...Second, ...Lastly..."

Strong, Active Verbs

Prefer vivid, precise verbs over adverb-heavy constructions:

  • "delighting the Romans" (not "making the Romans very happy")
  • "baits them into modifying their accusations"
  • "tumbling over the roof"
  • "drilling a hole into his forehead"

Lists in Natural Language

Integrate lists as flowing sentences rather than bullet points in prose:

  • "Most of all, I think I've developed the conciseness of my writing, which I believe is one of my strengths as a writer."
  • "My thesis driven arguments have become more persuasive, my analytical writing has become more precise, and my use of citations is now more robust."

Paragraph Structure

Topic Sentences State the Point

Lead paragraphs with clear declarations:

  • "Of the many functions of religion in Roman society, its effects on their ability to wage war were some of the most profound."
  • "The first of these positive effects is of psychological nature"
  • "Religion also acted as a powerful motivating factor"

Evidence Follows Logically

After stating your point, provide specific support:

  • Claim → "For example..." → specific evidence → analysis
  • "This sort of tactic was used throughout their battles to similar effect. For example, in Livy's account of the second Punic war..."

Synthesis Over Summary

Connect ideas and draw conclusions rather than just listing facts:

  • "Altogether, this indicates a real commitment to their religious doctrine"
  • "In other words, people feel a strong, positive, in-group bias towards their own party"
  • "This unification of religious views likely brought people closer together"

Context-Specific Adaptations

Professional/Application Writing

  • Lead with action and specificity
  • Use "I'd like to highlight..." structure
  • End with enthusiasm but not desperation
  • Show personality: "Gosh, I really wish..."

See PROFESSIONAL.md for detailed examples

Academic Writing

  • Strong thesis statements
  • Extensive evidence and citations
  • Formal but not stilted
  • Clear logical progression

See ACADEMIC.md for detailed examples

Creative Fiction

  • Strong sensory details ("yellowy fog of spores")
  • Natural dialogue that reveals character
  • Show emotional states through action and thought
  • Varied narrative pacing

See FICTION.md for detailed examples

Personal/Letter Writing

  • Warm without being mawkish
  • Specific anecdotes over general claims
  • Natural storytelling flow
  • Genuine emotion conveyed through details

See PERSONAL.md for detailed examples

What to Avoid

  • Excessive hedging ("perhaps," "maybe," "possibly" unless genuinely uncertain)
  • Overly formal transitions ("furthermore," "in addition to," "notwithstanding")
  • Bullet points in flowing prose (save for lists that demand it)
  • Unnecessary qualifiers before strong statements
  • Flowery or purple prose
  • Overexplaining jokes or irony
  • Corporate speak or jargon soup

Common Constructions

Use these patterns naturally:

  • "All of this is to say, [conclusion]"
  • "[Statement]—[clarification or emphasis]—[continuation]"
  • "I'd first/second like to highlight [X]"
  • "At a high level, [summary]"
  • "This is [X]. That's [Y]."
  • "However, [contrasting point]"
  • "[Short punchy sentence]. [Longer explanatory sentence with multiple clauses]."
  • "And [conjunction start for emphasis]"

When not to use it

  • Academic or formal technical writing requiring third-person detachment
  • Legal documents requiring specific jargon and traditional phrasing

Limitations

  • May conflict with strict corporate style guides
  • Can feel overly informal for certain executive communications
  • Requires manual review to ensure the personality doesn't overwhelm the subject matter

How it compares

It applies a strict, pre-defined set of linguistic rules rather than simply mimicking a tone based on a prompt.

Compared to similar skills

writing-like-user side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
writing-like-user (this skill)69moNo flagsBeginner
humanizer906moNo flagsBeginner
ad-creative332moReviewBeginner
humanizer-zh406moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by CaptainCrouton89

View all by CaptainCrouton89

reviewing-code

CaptainCrouton89

Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.

21105

railway-cli-management

CaptainCrouton89

Deploy, manage services, view logs, and configure Railway infrastructure. Use when deploying to Railway, managing environment variables, viewing deployment logs, scaling services, or managing volumes.

9139

gathering-requirements

CaptainCrouton89

Systematically clarify user needs, preferences, and constraints before planning or implementation. Classifies work type, investigates existing systems, discovers edge cases and integration points, resolves assumptions, and creates detailed specifications. Use when building features, enhancements, or integrations where requirements need clarification.

31

auditing-security

CaptainCrouton89

Identify and remediate vulnerabilities through systematic code analysis. Use when performing security assessments, pre-deployment reviews, compliance validation (OWASP, PCI-DSS, GDPR), investigating known vulnerabilities, or post-incident analysis.

10

documenting-code

CaptainCrouton89

Maintain project documentation synchronized with code. Keep feature specs, API contracts, and README current with init-project standards. Use when updating docs after code changes, adding new features, or ensuring documentation completeness.

14

executing-work-in-parallel

CaptainCrouton89

Coordinate concurrent task execution through agent delegation. Plan independent work, manage dependencies, and execute multiple agents simultaneously. Use when handling multiple unrelated tasks, research investigations, or layer-based implementations that can run concurrently.

12

You might also like

humanizer

davila7

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Credits: Original skill by @blader - https://github.com/blader/humanizer

90175

ad-creative

alirezarezvani

When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.

3395

humanizer-zh

op7418

去除文本中的 AI 生成痕迹。适用于编辑或审阅文本,使其听起来更自然、更像人类书写。 基于维基百科的"AI 写作特征"综合指南。检测并修复以下模式:夸大的象征意义、 宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、 AI 词汇、否定式排比、过多的连接性短语。

4070

product-marketing-context

coreyhaines31

When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.

1574

copywriting

davila7

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.

1866

tov-editor

RogueRope

Brand voice editor trained on the Tone & Writing Style Guide. Reviews copy for alignment with intimate, bold, consent-forward, sex-positive tone. Audits microcopy, red flags, lexicon, rhythm, consent framing, and channel-specific patterns.

574

Search skills

Search the agent skills registry