Create Quick Start Guides That Get Users to Value Fast

This skill turns an agent into a quick-start-guide writer that optimizes for time-to-value rather than comprehensive education. It targets a 5-15 minute completion window, leads with the most useful feature, and defers advanced concepts and edge cases in favor of a single meaningful outcome. It follows a progressive-disclosure structure: stated prerequisites, numbered steps that build in complexity, and escape hatches to deeper documentation for readers who want more.

Every guide it produces is validation-driven - each major section ends with a verification step showing the expected output, common failure points get a troubleshooting note, and the guide closes on a clear success indicator (for example, opening a local URL and seeing a specific JSON response). The included template covers a full worked example: a "Before You Begin" prerequisites block, numbered action steps with complete runnable code (an Express.js server, a docker-compose file with an nginx and Postgres service, a FastAPI app with requirements.txt pins), expected-output blocks, a troubleshooting section for issues like "command not found" or a port conflict, and a "Next Steps" section linking to deeper tutorials and API docs.

Use this skill when writing onboarding documentation for a product, CLI tool, API, or library where the goal is getting a new user to a first working result fast. It is not for comprehensive reference documentation - the skill explicitly avoids explaining every parameter, listing multiple configuration alternatives, or giving comprehensive feature overviews, favoring one single path to success with working defaults instead. It also flags vague instructions ("configure your environment") and code snippets without file locations or expected outcomes as anti-patterns to avoid.

Input: a product, CLI, API, or library name and its target first-run outcome. Output: a complete quick-start guide following the template - prerequisites, numbered steps with complete runnable code and expected-output blocks, a troubleshooting section, and next-step links - written in active voice and imperative mood at an eighth-grade reading level, with sentences kept under 20 words.

The worked examples cover CLI tools (installation verification, init/dev commands), REST APIs (a fetch call with headers and error handling), and framework libraries (a complete FastAPI app with requirements.txt and a uvicorn run command), plus a Node/Express web-server example and a docker-compose setup with nginx and Postgres services.

Developers, technical writers, and DevRel teams producing onboarding docs for a new product, CLI, API, or library who need a guide optimized for a fast first win rather than exhaustive coverage - and a maintenance discipline (monthly re-testing, keeping version numbers current) for keeping it working.