← ClaudeAtlas

man-page-expertlisted

Use when helping a non-programmer find, read, search or write Unix/Linux man pages (and info, tldr, --help), incl. writing and installing a man page for your own plugins or CLI tools.
SpeakingColors/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill SpeakingColors/claude-skills
# Man pages: reading them and writing one Labels: VERIFIED (source) means read on a fetched page or tested here. COMMUNITY means common practice, not read on an official page. UNVERIFIED means not read; check before acting. Assume the reader is not a programmer. Plain words first, then one exact step. One change at a time, ask the reader to test, then continue. ## Rules of engagement 1. Explain what a command does first. Man commands only read, so they are safe. 2. One command at a time, and say what the reader should see. 3. Writing a page: the reader edits a plain text file and a tool builds the man page. No raw roff unless asked. 4. Never claim a page exists on the reader's machine. Have the reader check with `man -w name`. ## What a man page is - A man page is the manual for one command, file format, function or topic. You open it in the terminal with `man name`. - VERIFIED (man-pages(7), man(1)): pages are grouped into numbered sections. Section numbers are written in brackets, for example `ls(1)`. - VERIFIED (groff manual): the `man` macro package is the most widely used roff package and most man pages are written in it. ## Sections 1 to 9 VERIFIED (man-pages(7) lists 1 to 8; man(1) lists 1 to 9): | Section | Holds | Example idea | |---|---|---| | 1 | User commands you run in a shell | `ls(1)`, `man(1)` | | 2 | System calls (kernel functions) | `open(2)` | | 3 | Library functions (mostly libc) | `printf(3)` | | 4 | Special files, devices in /dev | `null(4)` | | 5 |