write-docs

Optimize user-facing documentation with reading-funnel principles and usability rules.

Updated Jun 12, 2026

Search Tags:#documentation #technical writing #copywriting #usability #content audit #reading funnel

Ready to run

npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill write-docs-ambrovia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-docs
Source: https://github.com/ambrovia/agent-skills-pipeline/tree/main/skills/write-docs
Command: npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill write-docs-ambrovia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of ineffective, high-bounce-rate documentation by transforming technical writing into a structured reading funnel that captures attention and drives user action.

Core Features & Use Cases

Reading Funnel Optimization: Applies empirical eye-tracking and cognitive load research to ensure readers reach the activation stage.
Voice & Anti-Slop Auditing: Removes filler language and promotional fluff while preserving the author's unique voice and technical precision.
Use Case: Use this skill when drafting a new feature guide or auditing existing product documentation to ensure the content is scannable, evidence-backed, and task-oriented.

Quick Start

Use the write-docs skill to audit the current feature documentation against the 10-point rubric and suggest specific structural improvements.

Frequently Asked Questions about write-docs

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

FAQPage Schema

How do I optimize technical documentation for reader retention?▼

Apply reading-funnel principles and empirical usability rules to optimize technical documentation, structuring content to reduce cognitive load and increase reader retention. This transforms high-bounce-rate text into a task-oriented conversion funnel.

What is a reading funnel in technical writing?▼

A reading funnel in technical writing applies eye-tracking and cognitive load research to guide readers from initial scanning to activation. It structures user-facing guides to capture attention, manage cognitive load, and drive task completion.

How do I audit existing product documentation for scannability and accuracy?▼

Audit existing product documentation by evaluating content against a 10-point rubric focused on scannability, evidence-based technical accuracy, and cognitive load. This identifies filler language and suggests structural improvements to optimize the reading funnel.

Does this documentation optimization approach work for feature guides and product pages?▼

Yes, this approach works for feature guides, product pages, and technical documentation by applying voice and anti-slop auditing. It removes promotional fluff while preserving technical precision and the author's unique voice across multi-agent pipelines.

When should I not use a reading funnel approach for content?▼

Avoid using a reading funnel approach for content requiring exploratory or non-task-oriented reading, as it optimizes user-facing documentation specifically for conversion and activation. It targets scannable, evidence-backed technical guides rather than narrative texts.