docs

Refine technical documentation for MDX pages, READMEs, and conceptual guides.

1|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/kizlo-io/kizlo --skill docs-kizlo-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/kizlo-io/kizlo/tree/main/.claude/skills/docs
Command: npx skills add https://github.com/kizlo-io/kizlo --skill docs-kizlo-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates fluff, repetition, and inconsistent tone in technical documentation, ensuring that content is scannable, actionable, and aligned with high-quality engineering standards.

Core Features & Use Cases

  • Content Tightening: Automatically removes filler words, marketing hype, and redundant explanations to improve clarity.
  • Style Enforcement: Ensures strict adherence to house style, including the prohibition of em-dashes and the use of specific MDX conventions.
  • Use Case: Use this skill to transform a draft README or a complex technical guide into a concise, professional document that follows the project's specific Fumadocs conventions.

Quick Start

Use the docs skill to review and tighten the provided draft for the new CLI command guide.

Frequently Asked Questions about docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a strict house style for technical writing in MDX files?

To refine technical documentation, this skill removes fluff, repetition, and inconsistent tone from drafts. It enforces strict house style and optimizes content for scannability, ensuring technical guides are concise and actionable.

How do I remove redundant content and filler from a technical README?

To remove redundant content from a technical README, this skill automatically tightens drafts by eliminating filler words and marketing hype. It transforms verbose explanations into concise, professional documentation aligned with engineering standards.

Does this technical writing refinement support Fumadocs conventions for MDX pages?

To remove redundant content from a technical README, this skill automatically tightens drafts by eliminating filler words and marketing hype. It transforms verbose explanations into concise, professional documentation aligned with engineering standards.

What is the best way to optimize conceptual guides for scannability?

To remove redundant content from a technical README, this skill automatically tightens drafts by eliminating filler words and marketing hype. It transforms verbose explanations into concise, professional documentation aligned with engineering standards.

When should I avoid using em-dashes in technical documentation?

To remove redundant content from a technical README, this skill automatically tightens drafts by eliminating filler words and marketing hype. It transforms verbose explanations into concise, professional documentation aligned with engineering standards.