skills.rest
alexeyshishin
alexeyshishinCOMMUNITY
Explore all skills by this author →
GitHub

content-documentation

Generates structured technical tutorial skeletons with numbered steps, verification checks, and troubleshooting sections.

4|Updated Aug 8, 2026
Search Tags:#documentation#markdown#troubleshooting#technical writing#tutorial#step-by-step#how-to guide
One-click install
npx skills add https://github.com/alexeyshishin/as-skill --skill content-documentation-alexeyshishin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: content-documentation
Source: https://github.com/alexeyshishin/as-skill/tree/main/domains/content/skills/content-documentation
Command: npx skills add https://github.com/alexeyshishin/as-skill --skill content-documentation-alexeyshishin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing technical tutorials from scratch often produces vague, unverifiable instructions with missing prerequisites, unexplained placeholders, and no troubleshooting guidance. This Skill enforces a reproducible tutorial structure so readers can follow steps and verify each one works. ## Core Features & Use Cases - Scope Definition: Narrows vague requests ("a tutorial on k8s") into a concrete goal with a defined starting state, final state, and platform versions. - Skeleton Generation: Produces a Markdown skeleton with prerequisites, numbered verb-first steps, copy-pasteable commands, per-step checks, troubleshooting, cleanup, and next-step links. - Iterative Review: Shows the structure first for approval, then fills in steps, and offers options to expand, compress, or add sections. - Use Case: Ask for a deployment guide for a stateless API on minikube, and receive a step-by-step tutorial skeleton where every command has a verification check and a rollback section. ## Quick Start Write a step-by-step tutorial skeleton for deploying a Postgres cluster with replication, including prerequisites, verification checks, troubleshooting, and cleanup.

Frequently Asked Questions about content-documentation

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

FAQPage Schema
How do I write a technical tutorial with verifiable steps?▼

Define the goal as "after reading, the reader can do X", then break the path into numbered steps where each has a command and a check confirming it worked. Add troubleshooting and cleanup sections so readers can recover from failures and roll back changes.

What structure should a how-to guide or deployment tutorial follow?▼

A solid tutorial includes a goal statement, prerequisites with versions, numbered verb-first steps with commands and checks, an end-to-end verification section, troubleshooting with symptom-cause-fix entries, cleanup commands, and links to further reading.

Does this Skill write the full tutorial text for me?▼

No, it intentionally produces a correct skeleton rather than full prose. The author fills in details, because a verified skeleton is more trustworthy than polished text containing invented commands.

Why should every tutorial step include a verification check?▼

Without a check, readers cannot tell where they went wrong when the final result fails. A check after each step—an expected output or confirming command—is what distinguishes a reproducible tutorial from a blog post.

When should I not use a single tutorial for a topic?▼

Avoid cramming everything into one article: tutorials exceeding roughly 50 minutes of reading should be split into multiple parts. Also avoid writing tutorials for scenarios never actually walked through, since made-up commands destroy reader trust.

Related Skills

Explore More Content & Communication Skills→
X-School-AcademyX-School-Academy
19

terminal-exec-command

Execute shell commands on local or SSH targets and capture output.

Official
Intermediate
RomainGRAS42RomainGRAS42

content-repurposing

Convert long-form content into threads, carousels, blogs, and quotes.

Community
Intermediate
miolamiomiolamio
28

en-ru-translator-adv

Translate English technical and marketing texts into idiomatic Russian.

Community
Advanced
ruskicoderruskicoder
3

documentation

Write technical documentation including READMEs, API docs, runbooks, and onboarding guides.

Community
Basic