New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Writing User Docs

by fullsend-ai in fullsend-ai/fullsend

A skill your agent uses when writing, editing, or adding documentation under docs/guides/.

Apache-2.0Auto-check passedWriting & Content

Install Writing User Docs

skills CLI
$ npx skills add fullsend-ai/fullsend --skill writing-user-docs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fullsend-ai/fullsend writing-user-docs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fullsend-ai/fullsend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing-user-docs .claude/skills/writing-user-docs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
writing-user-docs
GitHub stars
147
Token cost
~816 tokens
SKILL.md length
277 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when writing, editing, or adding documentation under docs/guides/.

  • Works in 6 steps: One audience, one task. Each guide… → Prerequisites first. State what the… → Steps, not prose. Numbered steps for… → …
  • Adding documentation under docs/guides/
  • SKILL.md covers Overview, Directory Layout, Writing Rules and Effective Writing, plus 2 more sections
  • Calls make

What it does

Writing User Docs is an agent skill from fullsend-ai/fullsend. Use when writing, editing, or adding documentation under docs/guides/. Use when creating getting-started or infrastructure guides (install, configure, operate), user guides (workflows, interactions, interventions), or dev guides (developing and testing fullsend itself).

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Technical writing. The repository describes itself as: On the path to fully autonomous agentic engineering. The licence is Apache-2.0.

When your agent uses it

  • Adding documentation under docs/guides/
  • Creating getting-started
  • Infrastructure guides (install
  • User guides (workflows

Example prompts

  • “/writing-user-docs”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. One audience, one task. Each guide targets a single audience.
  2. Prerequisites first. State what the reader needs before step 1.
  3. Steps, not prose. Numbered steps for procedures. Command first, then
  4. Link, don't restate. Point to ADRs, normative specs, and
  5. Mark planned features. Use a blockquote callout referencing the issue
  6. No jargon without definition. Link to docs/glossary.md or define

What it can do on your machine

Read from SKILL.md and the folder at commit 87bf615. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Writing User Docs loads about 816 tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 277 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~816

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fullsend-ai/fullsend at commit 87bf615, republished under its Apache-2.0 licence (© fullsend-ai). 277 words, ~816 tokens.

Download SKILL.mdSave it as .claude/skills/writing-user-docs/SKILL.md (or your agent's skills folder).
name
writing-user-docs
description
Use when writing, editing, or adding documentation under docs/guides/. Use when creating getting-started or infrastructure guides (install, configure, operate), user guides (workflows, interactions, interventions), or dev guides (developing and testing fullsend itself).

Writing User Documentation

Overview

User docs are task-oriented guides organized by audience: org maintainers who onboard organizations, platform operators who deploy and manage the GCP infrastructure, developers who work in enrolled repos, and contributors working on fullsend itself. Structure and rules are decided in ADR 0023.

Directory Layout

docs/guides/
├── README.md              # Index — update when adding guides
├── getting-started/       # Org maintainers onboarding orgs and repos
│   └── configuring-github.md
├── infrastructure/        # Platform operators managing GCP infra (mint, WIF)
│   └── mint-administration.md
├── user/                  # Developers in enrolled repos
│   └── bugfix-workflow.md
└── dev/                   # Contributors developing fullsend itself
    └── e2e-testing.md

Layout per ADR 0023's Revision (2026-05), which split the original admin/ directory into getting-started/ and infrastructure/. See docs/guides/README.md for the full index.

Writing Rules

  1. One audience, one task. Each guide targets a single audience.

  2. Prerequisites first. State what the reader needs before step 1.

  3. Steps, not prose. Numbered steps for procedures. Command first, then explain — not the reverse.

  4. Link, don't restate. Point to ADRs, normative specs, and docs/architecture.md for architectural context.

  5. Mark planned features. Use a blockquote callout referencing the issue:

    markdown
    > **Planned:** The **fix agent** ([#197](...)) will handle ...

  6. No jargon without definition. Link to docs/glossary.md or define inline on first use.

Effective Writing

Use the elements-of-style:writing-clearly-and-concisely skill when drafting or editing guides. Key principles:

  • Active voice, positive form, concrete language
  • Omit needless words — every sentence should earn its place
  • Parallel structure in lists and steps

Checklist

  • File is in the correct directory (getting-started/, infrastructure/, user/, or dev/)
  • Prerequisites section exists and is complete
  • Procedures use numbered steps
  • Commands appear before their explanations
  • Planned features use > **Planned:** callouts with issue links
  • All internal links resolve (ADRs, specs, other guides)
  • docs/guides/README.md index is updated
  • Changes staged and make lint passes

Common Mistakes

MistakeFix
Mixing content for different audiencesSplit into separate guides
Explaining architecture inlineLink to docs/architecture.md
Documenting planned features as currentAdd > **Planned:** callout
Forgetting to update the indexEdit docs/guides/README.md
Prose paragraphs for proceduresConvert to numbered steps

© fullsend-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/writing-user-docs of fullsend-ai/fullsend.

Open the folder on GitHubat commit 87bf615

Compare with similar skills

Writing User Docs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Writing User Docs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Writing User Docs this skillfullsend-ai/fullsend147—~816Automated safety check: PassApache-2.0
Beads Documentation Style Guidegastownhall/beads28k—~3.2kAutomated safety check: PassMIT
Technical Writing Standardcursor/plugins10k10 repos~2.4kAutomated safety check: PassNone
Heym Documentation Articlesheymrun/heym1.4k—~780Automated safety check: PassCustom licence
Chinese Technical Writingleter/zh-tech-writing334—~656Automated safety check: PassMIT
Nbj Write Clearlydaniel-p-green/nbj-write-clearly117—~1.1kAutomated safety check: PassMIT

Similar skills

  • Beads Documentation Style Guide

    gastownhall/beads

    Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.

    28k GitHub stars~3.2k tokensUpdated today
    Writing & ContentAuto-check passed

  • Technical Writing Standard

    cursor/plugins

    Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    10k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed

  • Heym Documentation Articles

    heymrun/heym

    Creates and updates documentation articles for the Heym platform: category choice, manifest entry, markdown file and cross-links from existing pages.

    1.4k GitHub stars~780 tokensUpdated today
    Writing & ContentAuto-check passed

  • Chinese Technical Writing

    leter/zh-tech-writing

    Sets writing rules for Chinese technical docs: short plain sentences, consistent typography and a checklist for removing AI-sounding filler.

    334 GitHub stars~656 tokensUpdated 14 days ago
    Writing & ContentAuto-check passed

  • Nbj Write Clearly

    daniel-p-green/nbj-write-clearly

    Drafts, revises, and audits reader-first technical and product documentation.

    117 GitHub stars~1.1k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • Developer Docs Technical Writer

    vercel-labs/github-tools

    Official

    Writes, reviews and edits developer documentation for SDKs, libraries and frameworks, from getting-started guides and API references to migration guides.

    131 GitHub stars~3.9k tokensUpdated yesterday
    Writing & ContentAuto-check passed

More from fullsend-ai/fullsend

All 15 skills in this repo

  • Cutting Releases

    fullsend-ai/fullsend

    A skill your agent uses when the user wants to tag a release, cut a release candidate, or ship a new version.

    147 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Topissues

    fullsend-ai/fullsend

    Build a merged RICE priority table: top unassigned backlog issues plus issues assigned to the current user.

    147 GitHub stars~523 tokensUpdated today
    Auto-check passed

  • User Forum Whats New

    fullsend-ai/fullsend

    A skill your agent uses when preparing the Fullsend user forum "What's New" agenda, a Tuesday-to-Tuesday recap, forum-host talk-track notes, or copy-paste HTML of shipped changes for users.

    147 GitHub stars~4k tokensUpdated today
    Auto-check passed

  • Adr Corner

    fullsend-ai/fullsend

    Find open GitHub pull requests that add or change Architecture Decision Records and report attribution, summaries, discussion points, and dates.

    147 GitHub stars~654 tokensUpdated today
    Auto-check passed

  • Nextwork

    fullsend-ai/fullsend

    Build a readiness-oriented queue of open issues/PRs — assigned work plus their open GitHub blockers — and recommend the next action for each.

    147 GitHub stars~5.3k tokensUpdated today
    Auto-check passed

  • Analyze Transcript

    fullsend-ai/fullsend

    Analyze fullsend agent run transcripts from GitHub Actions artifacts.

    147 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Writing User Docs

What does Writing User Docs do?

A skill your agent uses when writing, editing, or adding documentation under docs/guides/. Writing User Docs is an agent skill from fullsend-ai/fullsend. Use when writing, editing, or adding documentation under docs/guides/.

When should I use Writing User Docs?

Writing User Docs fits situations like: adding documentation under docs/guides/; creating getting-started; infrastructure guides (install; user guides (workflows.

How do I install Writing User Docs in Claude Code?

Run `npx skills add fullsend-ai/fullsend --skill writing-user-docs -a claude-code`. Or copy the skill folder (skills/writing-user-docs in fullsend-ai/fullsend) into .claude/skills/writing-user-docs in your project. Claude Code loads it when a task matches its description.

How do I install Writing User Docs in Codex?

Run `npx skills add fullsend-ai/fullsend --skill writing-user-docs -a codex`. Or copy the skill folder (skills/writing-user-docs in fullsend-ai/fullsend) into .agents/skills/writing-user-docs in your project. Codex loads it when a task matches its description.

Can I use Writing User Docs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fullsend-ai/fullsend --skill writing-user-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-user-docs, .gemini/skills/writing-user-docs, .github/skills/writing-user-docs and .opencode/skills/writing-user-docs in your project.

What does Writing User Docs need to run?

Going by SKILL.md and its folder, Writing User Docs needs the command-line tools its instructions call (make).

Does Writing User Docs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Writing User Docs safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Writing User Docs use?

Writing User Docs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Writing User Docs use?

About 816 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Writing User Docs?

Skills that share tags, products or a category with Writing User Docs: Beads Documentation Style Guide (gastownhall/beads, 28k stars), Technical Writing Standard (cursor/plugins, 10k stars), Heym Documentation Articles (heymrun/heym, 1.4k stars) and Chinese Technical Writing (leter/zh-tech-writing, 334 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Writing User Docs?

fullsend-ai (a GitHub organization) maintains it in fullsend-ai/fullsend, which has 147 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 8, 2026.

Source: fullsend-ai/fullsend on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.