ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

improve-doc

Analyze and improve existing documentation using Diataxis principles

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/anderskev/improve-doc
Or

Improve Doc

Analyze an existing markdown document, classify sections by Diataxis type, identify issues, and interactively refine each section.

Arguments

  • Path: Path to the markdown document to improve (required)

Workflow Overview

/beagle-docs:improve-doc docs/guides/getting-started.md

The command runs in two phases:

  1. Analysis Phase: Parse document, classify sections, identify issues
  2. Refinement Phase: Interactive loop to improve each section

Gates

Hard sequencing — advance only when the pass condition is met (artifact or explicit user input, not assumed).

Before Phase 2 (refinement):

  1. Read — Full contents of the file at Path are loaded.
    • Pass: Enumerated sections (from # / ## / ### headings) cover every heading in the file; titles match the source.
  2. Core skillbeagle-docs:docs-style is loaded (or its path read) before classification.
    • Pass: Analysis output reflects at least one concrete principle from that skill (name it or quote briefly).
  3. Handoff — User saw an analysis summary (template in Step 5 or equivalent) and entered start to begin refinement, or abort to exit.
    • Pass: If abort, no writes to Path. If start, proceed to Phase 2.

Before overwriting the file (Phase 2, Step 4):

  1. Choices — Every section with open issues has a terminal outcome: applied yes, unchanged skip, or modify loop finished with yes or skip.
    • Pass: No section left in a pending modify state unless the user aborted the whole session (then do not write).
  2. Skips — Content for every skip matches the original section text (copy preserved, not paraphrased).
    • Pass: Full block equality check against the initial read (line-for-line, including whitespace).
  3. Write — Only after the above.
    • Pass: Single save to Path; completion report notes backup or major restructure if applicable (Rules).

Ambiguous Diataxis type — If classification is uncertain, do not edit that section until the user answers the clarifying fork (Step 2b) or explicitly confirms your stated default.

Phase 1: Analysis

Step 1: Read Document

Read the target markdown file and parse into sections based on headings:

  • Each #, ##, ### heading starts a new section
  • Capture heading level, title, and content
  • Preserve hierarchy for context

Step 2: Load Core Skill

Load beagle-docs:docs-style for core writing principles that apply to all documentation types.

Step 3: Classify Each Section

For each section, determine the Diataxis type using these indicators:

Metadata

Author@anderskev
Stars4473
Views0
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-anderskev-improve-doc": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.