handbook-page
Write the handbook page that ends the repeated explanation — the answer-shaped structure (task-first, context second), the ownership and freshness header, and the write-once-point-forever discipline that turns tribal knowledge into infrastructure. Use when asked document how we do X, write the wiki page for this process, I explain this every month, or make this knowledge survive me. Produces the page with task-first structure, the header block, the worked example, and the pointer habit.
npx skills add mohitagw15856/pm-claude-skills --skill handbook-page --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Handbook Page Skill The handbook page is the highest-leverage document in team life: written once, it answers a question *forever* — but only if it's written answer-shaped. Most wiki pages are essay-shaped (history, context, philosophy, and eventually, maybe, the steps), while their readers arrive task-shaped ("how do I request access?"). The working page leads with the task, keeps context below the fold, carries the [doc-versioning-discipline](../doc-versioning-discipline/SKILL.md) header (owner, status, last-reviewed), includes one worked example — and then gets *used*: every repeat question gets answered with the link, because a handbook nobody points to is a diary. ## What This Skill Produces - **The page** — task-first structure: the answer/steps up top, the context and edge cases below - **The header block** — owner, status, last-reviewed — the trust signals - **The worked example** — one realistic walkthrough, because examples teach what steps can't - **The pointer habit** — the answer-with-the-link move that makes the page pay for itself ## Required Inputs Ask for these if not provided: - **The repeated question** — the actual thing people keep asking (verbatim asks beat
- What This Skill Produces
- Required Inputs
- Framework: The Page Rules
- Output Format
- The Answer
- Worked Example
- Edge Cases & Branches
- Background (for the curious)
- Quality Checks
- Anti-Patterns
What does the handbook-page skill do?
Write the handbook page that ends the repeated explanation — the answer-shaped structure (task-first, context second), the ownership and freshness header, and the write-once-point-forever discipline that turns tribal knowledge into infrastructure. Use when asked document how we do X, write the wiki page for this process, I explain this every month, or make this knowledge survive me. Produces the page with task-first structure, the header block, the worked example, and the pointer habit.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill handbook-page --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.