Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
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
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Writing Assistant

ASecurity

Use AI writing assistants effectively: prompting, drafting, editing, and keeping your voice. Use when writing faster without producing generic AI-sounding text.

2 stars
0 votes
0 copies
1 views
Added 9/29/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill writing-assistant --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Writing Assistant?

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

Security grade badge for Writing Assistant
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-writing-assistant/badge)](https://www.skillsdirectory.com/skills/aicodedecode-writing-assistant)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: writing-assistant
description: Use AI writing assistants effectively: prompting, drafting, editing, and keeping your voice. Use when writing faster without producing generic AI-sounding text.
category: productivity
---

# Writing Assistant

## Overview

AI writing assistants accelerate drafting, editing, and ideation — but default output is generic, verbose, and voiceless.

Effective use: you supply the thinking (ideas, structure, voice examples); the assistant supplies speed (drafts, variations, edits).

The skill is in prompting well, editing ruthlessly, and never publishing unexamined output.

## When to use

- Drafting emails, docs, posts, and reports faster
- Overcoming blank-page paralysis
- Editing and tightening your own drafts
- Brainstorming angles, outlines, and headlines
- Adapting tone for different audiences

## Core concepts

- **You think, it types.**
  Never outsource the thinking: provide the ideas, examples, and structure. Ask for execution help, not opinions to publish as yours.
- **Voice calibration.**
  Feed it 2-3 samples of your writing and ask it to match the voice. Generic output comes from generic prompts.
- **Outline-first.**
  Have it expand your outline, not invent the piece. Structure is thinking; keep that job.
- **Iterative refinement.**
  Draft -> critique -> revise cycles. Ask it to criticize its own draft against your criteria, then fix. Two passes minimum.
- **Targeted edits.**
  'Tighten this paragraph by 30%,' 'make this more direct,' 'add a concrete example here.' Specific edit requests beat 'make it better.'
- **Fact-check everything.**
  AI assistants confidently invent facts, quotes, and citations. Verify every factual claim independently before publishing.
- **De-genericizing.**
  Default output is verbose and hedged. Edit for: cut throat-clearing, add specifics, vary sentence length, insert your stories.
- **Disclosure norms.**
  Know your context's rules on AI assistance (academic, journalistic, corporate). When in doubt, disclose.

## Practical workflow

1. **Define the piece.**
   Before prompting: audience, purpose, key points, desired length and tone. Vague brief = generic output.
2. **Provide raw material.**
   Your outline, notes, examples, data, voice samples. The assistant assembles; you supply the substance.
3. **Generate the draft.**
   Ask for a draft from your outline. Expect 60-70% usable — that's the point; you're editing, not transcribing.
4. **Critique and revise.**
   Have it critique the draft (clarity, structure, voice match), then revise. Or critique it yourself — your judgment is the product.
5. **De-genericize.**
   Cut filler phrases, add concrete details and stories, sharpen the opening, vary rhythm. This pass is where voice appears.
6. **Fact-check.**
   Verify every claim, number, quote, and citation. Independently. No exceptions.
7. **Final human read.**
   Read aloud for flow. Check voice: does it sound like you on your best day? If not, rewrite the flat parts yourself.
8. **Learn the patterns.**
   Notice what you always fix — bake those into future prompts ('no throat-clearing openers, concrete examples, short paragraphs').

## Common pitfalls

- **Publishing raw output.**
  Unedited AI text is recognizable: hedged, verbose, generic. Always edit; your name is on it.
- **Outsourcing thinking.**
  Asking for opinions/arguments to publish as yours. The assistant is a writing tool, not a thought leader.
- **No voice calibration.**
  Generic prompts produce generic voice. Samples + explicit voice direction, or it won't sound like you.
- **Skipping fact-checks.**
  Confident fabrications in published work. Verify everything — the assistant doesn't know what it doesn't know.
- **Prompting once.**
  One prompt, one draft, done. Iteration (critique -> revise -> tighten) is where quality comes from.
- **Ignoring disclosure rules.**
  Academic/corporate policies on AI use exist. Violating them accidentally is still violating them.
- **Over-formatting.**
  Accepting the default emoji-headers-and-bullets style. Match formatting to your context's conventions.
- **Losing your voice.**
  Heavy assistant use converging your writing to the mean. Regular unassisted writing keeps your voice alive.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
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

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 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', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 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.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, 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.

741 votes
View all in ai-agents →