How do I install the User Docs skill?

Run npx skillmds@latest add stacklok/user-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is User Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with User Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is User Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published User Docs?

stacklok (@stacklok) published this skill. Their other Agent Skills are listed on their SkillMD profile.

User Docs by stacklok — Agent Skill

Name: User Docs
Author: stacklok

User Docs

Authors or updates Mecatl's public user documentation. Use when a change affects user-docs/, the Docusaurus site content, or a user-facing behavior that needs documentation. It follows the repository's lightweight authoring contract.

stacklok 89e31bc 1.6 KB Updated Sep 17, 2026

File contents

User documentation

Use this skill for public documentation in user-docs/, not for internal architecture records, ADRs, or implementation plans.

Workflow

Read user-docs/_README.md. It is the repository-owned authoring and information-architecture contract.
Decide whether the change belongs in user-docs/, then find the existing page that answers the reader's question. Extend that page before adding a new one.
Verify every behavioral claim against the shipped code and public configuration. Read the relevant docs/architecture/ and docs/adr/ material named by the contract, then verify the deployed surface. docs/usage/ contains historical compatibility pointers and is not a source. A port or constructor does not establish availability.
Follow the contract for placement, front matter, links, prose, and deployment boundaries. If the shared tech-writer skill is available, it can provide additional editorial guidance, but it is not required.
Run task site:build from the repository root. Report any claim that could not be verified instead of guessing.

For Docusaurus infrastructure and commands, consult website/AGENTS.md. Keep this skill short: the authoring contract is its single source of repository-specific rules.

Frequently asked questions