User Documentation
Create, review and validate software onboarding, task guides, UI help, FAQs and troubleshooting for non-technical end users. Use when people need to learn how to use a product or dashboard from verified interface evidence; route developer, API and administrator documentation to technical-writer.
Install
npx skills add jscraik/Agent-Skills --skill user-documentationgit clone --depth 1 https://github.com/jscraik/Agent-Skills.git /tmp/Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Agent-Skills/Skills/agent-ops/user-documentation ~/.claude/skills/user-documentationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# User Documentation ## When To Use - Non-technical users need onboarding or instructions for using software. - Product quick starts, task guides, in-product help, user FAQs, troubleshooting, dashboard guidance or end-user training need creation, correction or review. - An assessment requires user documentation for the software actually built. Do not use for API references, developer setup, SQL, deployment, system administration or maintenance runbooks: those belong to `technical-writer`. Split mixed deliverables by reader job, not by file format. Do not assume a non-technical reader lacks knowledge of their own profession. ## Inputs Requested mode, guide target, user task and starting knowledge, product/version, ordinary-user access, available UI evidence, required format and existing source. Start by reading the supplied guide or product evidence and locating the authoritative editable target. Infer routine choices; ask one concise question only when an essential missing fact would change the instructions or authority. ## Outputs Create or edit: completed user instructions plus separate editorial gaps. Review: prioritised located findings with user impact and a practical correction. Validate: checks, environment/role, results and untested steps. Report proposed, applied, saved, rendered and published states separately. ## Execution Boundaries Selecting this skill without a requested action means review, not rewriting.
Details
- Skill name
user-documentation- Repository
- jscraik/Agent-Skills
- Path
Skills/agent-ops/user-documentation/SKILL.md- License
- Apache-2.0
- Repo updated
- 16 November 2026
FAQ
What does the User Documentation skill do?
Create, review and validate software onboarding, task guides, UI help, FAQs and troubleshooting for non-technical end users. Use when people need to learn how to use a product or dashboard from verified interface evidence; route developer, API and administrator documentation to technical-writer.
How do I install the User Documentation skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jscraik/Agent-Skills --skill user-documentation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is User Documentation popular?
It lives in jscraik/Agent-Skills, which has 9 GitHub stars and 4 forks.
Related skills
1password
9jscraik/Agent-Skills
Plan, diagnose, and validate 1Password CLI workflows. Use when tasks need op CLI sign-in, secret references, op run, op inject, item reads, env injection, or service-account secret access.
Agentation
9jscraik/Agent-Skills
Audit, validate, and troubleshoot Agentation integrations in frontend apps. Use when annotations, MCP registration, endpoint sync, webhook delivery, or watch mode readiness are failing.
Agents Md
9jscraik/Agent-Skills
Use when reviewing, creating, shrinking, or refactoring AGENTS.md and directly linked instruction guidance for stale or conflicting rules against current model documentation, scoped routing, deduplication, or progressive disclosure.
Visual Explainer
9jscraik/Agent-Skills
Create self-contained HTML visual explainers from technical material. Use this skill when diagrams, matrices, timelines, or browser artifacts beat plain text.
Technical Writer
9jscraik/Agent-Skills
Audit, rewrite, and validate developer, administrator, and operator documentation—including API/OpenAPI references—against live repository evidence. Use when these documents need proof-backed correction, reader-focused review, generated-document ownership, public-access checks, or legacy docs-expert routing; route product end-user documentation to the separate User Documentation skill.
Pilot Content Marketing Pipeline Setup
9TeoSlayer/pilot-skills
Deploy a content marketing pipeline with 3 agents. Use this skill when: 1. User wants to set up an automated content production pipeline 2. User is configuring an agent as part of a content marketing workflow 3. User asks about automating research-to-publication content workflows Do NOT use this skill when: - User wants to share a single file (use pilot-share instead) - User wants a one-off webhook notification (use pilot-webhook-bridge instead)
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.