Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Adapt Writing Voice Improve Clarity

ASecurity

Adapt to writing voice, improve clarity, and remember style preferences across sessions.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgosecurity

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill adapt-writing-voice-improve-clarity --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Adapt Writing Voice Improve Clarity?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Adapt Writing Voice Improve Clarity
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-adapt-writing-voice-improve-clarity/badge)](https://www.skillsdirectory.com/skills/rondoflow-adapt-writing-voice-improve-clarity)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: adapt-writing-voice-improve-clarity
description: "Adapt to writing voice, improve clarity, and remember style preferences across sessions."
category: "Media"
author: community
version: "1.1.0"
icon: image
---

## Setup

On first use, read `setup.md` for integration guidelines.

## When to Use

User needs writing help: drafting, editing, feedback, or style adaptation. Agent remembers their voice and preferences across sessions.

## Architecture

Writing preferences persist in `~/writing/` with tiered structure. See `memory-template.md` for setup.

```
~/writing/
├── memory.md      # HOT: voice, style, active preferences
├── projects/      # Per-project voice (blog, newsletter, book)
└── archive/       # COLD: decayed patterns
```

## Quick Reference

| Topic | File |
|-------|------|
| Setup process | `setup.md` |
| Memory setup | `memory-template.md` |
| Writing dimensions | `dimensions.md` |
| Quality criteria | `criteria.md` |

## Detection Triggers

Activate automatically when you notice these patterns:

**Help requests** → engage writing mode:
- "Can you help me write..."
- "I need to draft..."
- "How does this sound?"
- "Can you edit this?"
- "Make this clearer"
- "Fix my writing"

**Voice signals** → save to memory.md Voice:
- "I like when you write..."
- "My style is..."
- "I always write like..."
- "Never use X in my writing"
- "Too formal/casual for me"

**Format preferences** → save to memory.md Formats:
- "For my blog, I..."
- "In emails, I prefer..."
- "Academic papers need..."
- "Marketing copy should..."

**Corrections** → evaluate for memory:
- "No, that's not my voice"
- "I would never say it like that"
- "Too wordy/short/formal/casual"
- "Change X to Y — that's how I write"

## Quick Queries

| User says | Action |
|-----------|--------|
| "What's my writing style?" | Show memory.md Voice section |
| "How do I write emails?" | Check memory.md Formats for email |
| "Show my patterns" | List memory.md content |
| "Show [project] style" | Load projects/{name}.md |
| "Forget my style" | Clear memory (confirm first) |
| "Writing stats" | Show counts per section |

## Core Rules

### 1. Check Memory First
Read `~/writing/memory.md` before any writing task. Apply their documented voice, formats, and preferences.

### 2. Learn Voice from Examples
When user shares their writing:
1. Read it carefully before responding
2. Note tone, cadence, vocabulary, sentence length
3. Match these patterns in your output
4. Ask: "Does this sound like you?"

### 3. Never Impose Style
| DO | DON'T |
|----|-------|
| Match their vocabulary | Use words they never use |
| Follow their sentence rhythm | "Correct" their style |
| Preserve their personality | Make everything "proper" |
| Ask before changing voice | Assume formal is better |

### 4. Clarity Over Cleverness
- One idea per paragraph
- Simple sentences beat complex ones
- Cut words that add no meaning
- Read aloud to catch awkwardness

### 5. Context-Aware Writing
| Format | Approach |
|--------|----------|
| Email | Concise, action-oriented, clear ask |
| Blog | Engaging opener, structured, conversational |
| Academic | Formal, referenced, precise language |
| Marketing | Benefit-focused, persuasive, scannable |
| Technical | Accurate, structured, example-heavy |

### 6. Edit in Passes
| Pass | Focus |
|------|-------|
| 1. Structure | Does the flow make sense? |
| 2. Clarity | Is each sentence clear? |
| 3. Voice | Does it sound like them? |
| 4. Polish | Cut 20%, fix awkwardness |

### 7. Tiered Storage
| Tier | Location | Behavior |
|------|----------|----------|
| HOT | memory.md | Always loaded, core preferences |
| WARM | projects/ | Load when working on that project |
| COLD | archive/ | Unused 90+ days, query on demand |

### 8. Automatic Promotion/Demotion
- Preference used 3x in 7 days → promote to HOT
- Preference unused 30 days → demote to WARM
- Preference unused 90 days → archive to COLD
- Never delete without asking

### 9. Transparency
- Cite memory when applying preferences: "Using casual tone (from memory.md)"
- Explain edits when requested
- Show what you learned after sessions

## Common Traps

- **Imposing your style** → Match their voice first, always
- **Over-editing** → Preserve their personality, don't sanitize
- **Passive voice everywhere** → Use active by default unless they prefer passive
- **Ignoring context** → Email differs from blog differs from paper
- **Forgetting their preferences** → Check memory.md every time
- **Assuming formal is correct** → Their style IS correct for them

## Security & Privacy

**Data that stays local:**
- Writing preferences in `~/writing/`
- Voice patterns and style notes
- Project-specific preferences

**This skill does NOT:**
- Store written content (only preferences)
- Make network requests
- Access files outside `~/writing/`
- Share preferences externally

## Related Skills
Install with `clawhub install <slug>` if user confirms:
- `grammar` — spelling and grammar checks
- `text` — text processing and manipulation
- `content-marketing` — content strategy and creation

## Feedback

- If useful: `clawhub star writing`
- Stay updated: `clawhub sync`

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →