Writing Pre Publish Checklist

Runs a comprehensive six-section quality checklist (content, structure, clarity, style, polish, final tests) before writing is shared or published, catching issues that revision and stickiness enhancement might miss. Use when performing final quality checks before sharing, publishing, or submitting writing, or when user mentions pre-publish, final check, ready to publish, last review, quality check, or about to share.

200 stars 25 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill writing-pre-publish-checklist
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/writing-pre-publish-checklist ~/.claude/skills/writing-pre-publish-checklist

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Writing Pre-Publishing Checklist

## Table of Contents

- [Core Principles](#core-principles)
- [Workflow](#workflow)
- [Check Details](#check-details)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)

**Related skills:** Use `writing-structure-planner` for planning structure, `writing-revision` for deep prose revision, `writing-stickiness` for memorable messaging.

## Core Principles

1. **Systematic, not subjective**: Follow the checklist completely, don't skip sections
2. **Fresh eyes perspective**: Read as if seeing the piece for the first time
3. **Binary decisions**: Each check item is pass/fail, not "sort of"
4. **Flag, don't fix**: Identify issues and present to user rather than silently fixing
5. **Final gate, not revision**: This catches remaining issues, not does deep rewriting

## Workflow

Copy this checklist and track your progress:

```
Pre-Publishing Checklist:
- [ ] Section 1: Content check
- [ ] Section 2: Structure check
- [ ] Section 3: Clarity check
- [ ] Section 4: Style check
- [ ] Section 5: Polish check
- [ ] Section 6: Final tests
```

**Before starting:** This is a systematic pass through the complete piece. Read the entire document first to understand context, then work through each section.

### Section 1: Content Check

Step 1.1: Read the entire piece. Identify the core message. Verify core message is crystal clear - could a reader state it back in one sentence?
Read the full skill on GitHub

Details

Skill name
writing-pre-publish-checklist
Path
skills/writing-pre-publish-checklist/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Writing Pre Publish Checklist skill do?

Runs a comprehensive six-section quality checklist (content, structure, clarity, style, polish, final tests) before writing is shared or published, catching issues that revision and stickiness enhancement might miss. Use when performing final quality checks before sharing, publishing, or submitting writing, or when user mentions pre-publish, final check, ready to publish, last review, quality check, or about to share.

How do I install the Writing Pre Publish Checklist skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Writing Pre Publish Checklist popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Writing Revision

200

lyndonkl/claude

Applies a systematic three-pass revision system (Zinsser, King, Pinker, Clark) to existing drafts — Pass 1 cuts clutter, Pass 2 reduces cognitive load, Pass 3 improves rhythm. Use when revising, editing, or polishing drafts, cutting word count, tightening prose, improving readability, or fixing flow, or when user mentions revision, editing, cut clutter, too wordy, improve readability, fix the flow, reduce word count.

Writing & Content25

Write Weekly Report

200

lyndonkl/claude

Composes the substacker final ops/growth-analyst/YYYY-WW-report.md from ingest + baseline + attribute + per-section + public-page outputs. Enforces 400-800 word budget, YAML frontmatter schema, seven-section body structure. Truncates weakest sections first when over budget. Injects data-caveats from any degraded-mode flags upstream. Use as the final compose step of the weekly pipeline. Trigger keywords — weekly report, compose report, growth report, Monday report.

Writing & Content25

Writing Stickiness

200

lyndonkl/claude

Applies the Heath brothers' SUCCESs model (Simple, Unexpected, Concrete, Credible, Emotional, Stories) to make messages memorable and persuasive, with systematic analysis, targeted improvements, and scoring (0-18 stickiness scorecard). Use when making messages more memorable or compelling, preparing presentations, crafting pitches or campaigns, or when user mentions stickiness, making ideas stick, persuasion, SUCCESs framework, or Heath brothers.

Writing & Content25

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.