Back to Skills

Writing Mentor

lyndonkl
Updated Today
20 views
5
5
View on GitHub
Designmcpdesign

About

Writing Mentor is a Claude skill that guides users through the entire writing process, from initial planning to final polish. It helps with drafting new pieces, revising existing drafts, planning structure, and applying techniques from expert writers to improve organization and memorability. Developers can integrate this skill to provide comprehensive writing assistance within their applications.

Documentation

Writing Mentor

Table of Contents

Start Here

Workflows

Understand the Situation

Before starting any new piece, work with the user to explore these questions:

  • What are you writing? (genre, length, purpose)
  • Who is your primary audience?
  • What is your reader's state of mind? (what do they know? what do they expect?)
  • What is your core promise in ≤12 words?
  • What must the reader remember if they forget everything else?
  • What's at stake emotionally for the reader?
  • What's at stake practically for the reader?
  • What is your commander's intent? (the single essential goal)
  • Why should the reader care?

Work together to document the intent brief before proceeding.

Full Writing Process (New Piece)

For: User starting from scratch

Copy this checklist and track your progress:

Full Writing Process:
- [ ] Step 1: Plan structural architecture
- [ ] Step 2: Draft with discipline
- [ ] Step 3: Revise in three passes
- [ ] Step 4: Enhance stickiness
- [ ] Step 5: Pre-publishing check

Step 1: Plan structural architecture

Work with user to select and diagram the appropriate structure type (List, Chronological, Circular, Pyramid, etc.). See resources/structure-types.md for complete workflow with 8 structure types, diagrams, and selection criteria.

Step 2: Draft with discipline

Review intent brief and structure diagram together. Remind user that shitty first drafts are good (Lamott)—write without editing. Guide to favor concrete nouns, strong verbs, sensory detail (King), and short declarative sentences (Klinkenborg). Encourage flow—don't stop to perfect, just get words on paper.

Step 3: Revise in three passes

Apply systematic revision: Pass 1 cuts clutter (Zinsser/King), Pass 2 reduces cognitive load (Pinker), Pass 3 improves rhythm (Clark). See resources/revision-guide.md for complete three-pass workflow with specific techniques for each pass.

Step 4: Enhance stickiness

Apply SUCCESs framework (Simple, Unexpected, Concrete, Credible, Emotional, Stories) to make message memorable. See resources/success-model.md for complete workflow, stickiness scorecard (0-18 points), and before/after examples.

Step 5: Pre-publishing check

Run through comprehensive checklist covering content, structure, clarity, style, polish, and final tests. See Pre-Publishing Checklist below for all items before sharing or publishing.

Revision & Polish (Existing Draft)

For: User has draft, needs improvement

Copy this checklist and track your progress:

Revision & Polish:
- [ ] Step 1: Three-pass revision
- [ ] Step 2: Enhance stickiness (optional)

Step 1: Three-pass revision

Apply systematic revision in three passes: Pass 1 cuts clutter (Zinsser/King) by removing weak constructions and cutting 10-25%; Pass 2 reduces cognitive load (Pinker) by fixing garden-paths and improving readability; Pass 3 improves rhythm (Clark) by varying sentences, adding gold-coins, and enhancing flow. See resources/revision-guide.md for complete workflow with specific techniques for each pass.

Step 2: Enhance stickiness (optional)

Apply SUCCESs framework (Simple, Unexpected, Concrete, Credible, Emotional, Stories) to make message more memorable. See resources/success-model.md for complete workflow, stickiness scorecard, and before/after examples.

Structure Planning

For: User has ideas but unsure how to organize

Copy this checklist and track your progress:

Structure Planning:
- [ ] Step 1: Select appropriate structure type
- [ ] Step 2: Create structure diagram
- [ ] Step 3: Place gold-coins strategically

Step 1: Select appropriate structure type

Work with user to understand their content and choose from 8 structure types (List, Chronological, Circular, Dual Profile, Pyramid, Parallel Narratives, etc.). See resources/structure-types.md for philosophy, structure selection criteria, and diagrams for each type.

Step 2: Create structure diagram

Follow the 5-step process to diagram the chosen structure with user's specific content. See Creating Your Own Structure Diagram for step-by-step guidance.

Step 3: Place gold-coins strategically

Identify where to place narrative rewards (gold-coins) to maintain reader engagement, especially in middle sections. See Gold-Coin Placement Strategy for techniques.

Stickiness Enhancement

For: User wants message to be more memorable

Copy this checklist and track your progress:

Stickiness Enhancement:
- [ ] Step 1: Rate current stickiness
- [ ] Step 2: Apply SUCCESs framework
- [ ] Step 3: Re-rate and refine

Step 1: Rate current stickiness

Use the stickiness scorecard to rate the current message on 6 dimensions (0-18 points total). This establishes baseline. See resources/success-model.md for complete scorecard and rating guidance.

Step 2: Apply SUCCESs framework

Work through all 6 principles systematically: Simple (find core), Unexpected (break schemas), Concrete (sensory details), Credible (testable claims), Emotional (make people care), Stories (simulate experience). See detailed guidance on all 6 principles for specific techniques.

Step 3: Re-rate and refine

Score the revised message using the same scorecard. Aim for 12+ points for good stickiness. See before/after examples for transformation patterns.

Pre-Publishing Checklist

Use before sharing or publishing.

Content

  • Core message is crystal clear
  • All facts checked for accuracy
  • Examples are relevant and appropriate
  • Arguments are sound and complete
  • No missing information

Structure

  • Opening hooks readers
  • Flow is logical and smooth
  • Transitions work smoothly
  • Middle section has gold coins
  • Conclusion satisfies

Clarity

  • No jargon (or all jargon explained)
  • No ambiguous pronouns
  • No garden-path sentences
  • Technical accuracy maintained
  • Appropriate for target audience

Style

  • Tone is consistent
  • Voice is appropriate
  • Sentence variety is good (score 7+/10)
  • No clutter remains
  • Active voice predominates

Polish

  • Spelling checked
  • Grammar correct
  • Punctuation proper
  • Formatting consistent
  • Links work (if applicable)

Final Tests

  • Read aloud - does it sound good?
  • Fresh eyes review (if possible)
  • Achieves stated intent
  • Satisfies target audience needs
  • You're proud of it

Quick Install

/plugin add https://github.com/lyndonkl/claude/tree/main/writer

Copy and paste this command in Claude Code to install this skill

GitHub 仓库

lyndonkl/claude
Path: skills/writer

Related Skills

langchain

Meta

LangChain is a framework for building LLM applications using agents, chains, and RAG pipelines. It supports multiple LLM providers, offers 500+ integrations, and includes features like tool calling and memory management. Use it for rapid prototyping and deploying production systems like chatbots, autonomous agents, and question-answering services.

View skill

Algorithmic Art Generation

Meta

This skill helps developers create algorithmic art using p5.js, focusing on generative art, computational aesthetics, and interactive visualizations. It automatically activates for topics like "generative art" or "p5.js visualization" and guides you through creating unique algorithms with features like seeded randomness, flow fields, and particle systems. Use it when you need to build reproducible, code-driven artistic patterns.

View skill

webapp-testing

Testing

This Claude Skill provides a Playwright-based toolkit for testing local web applications through Python scripts. It enables frontend verification, UI debugging, screenshot capture, and log viewing while managing server lifecycles. Use it for browser automation tasks but run scripts directly rather than reading their source code to avoid context pollution.

View skill

requesting-code-review

Design

This skill dispatches a code-reviewer subagent to analyze code changes against requirements before proceeding. It should be used after completing tasks, implementing major features, or before merging to main. The review helps catch issues early by comparing the current implementation with the original plan.

View skill