Agent skill

Handbook Page

by mohitagw15856 in mohitagw15856/pm-claude-skills

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…

MITAuto-check passedKnowledge Management

Install Handbook Page

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill handbook-page -a claude-code

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

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills handbook-page --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/handbook-page .claude/skills/handbook-page && 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
handbook-page
GitHub stars
1.4k
Token cost
~1.3k tokens
SKILL.md length
691 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 5 steps: Answer-shaped, not essay-shaped: the… → Steps at do-this grain with branches… → The worked example is half the teaching:… → …
  • Asked document how we do X
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Page Rules and Output Format, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Handbook Page is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.3k 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 Knowledge Management. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked document how we do X
  • Write the wiki page for this process
  • I explain this every month
  • Make this knowledge survive me

Example prompts

  • “/handbook-page”

Workflow steps

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

  1. Answer-shaped, not essay-shaped: the reader's task is satisfied in the first screen — the steps, the link, the form, the decision table…
  2. Steps at do-this grain with branches explicit: the oral version's "oh, unless…" branches become visible forks (runbook-writer grain for…
  3. The worked example is half the teaching: one realistic case walked end-to-end ("requesting prod access for a new analyst: …") — readers…
  4. The header makes it trustworthy: owner (who answers when the page is wrong), status, last-reviewed — without these, readers who've been…
  5. The pointer habit is the payoff loop: from publication day, every repeat ask gets "here you go: [link] — tell me if anything's unclear"…

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Handbook Page loads about 1.3k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 691 words of instructions outside code blocks.

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

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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 691 words, ~1,326 tokens.

Download SKILL.mdSave it as .claude/skills/handbook-page/SKILL.md (or your agent's skills folder).
name
handbook-page
description
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.

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 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 topic descriptions — the faq-builder mining logic); pages written for imagined questions join the unread
  • The answer, from the explainer — the current oral version, including the caveats and the "oh but if it's a contractor it's different" branches that live only in the explainer's head
  • The audience floor — who arrives at this page and what they already know; the page assumes the floor and links the rest
  • Where the handbook lives — and the naming/finding conventions there, so the page is discoverable by the words askers use

Framework: The Page Rules

  1. Answer-shaped, not essay-shaped: the reader's task is satisfied in the first screen — the steps, the link, the form, the decision table. History and rationale live below under "Background," read by the curious minority. The test: the modal reader leaves within ninety seconds, satisfied.
  2. Steps at do-this grain with branches explicit: the oral version's "oh, unless…" branches become visible forks (runbook-writer grain for anything procedural) — the page must beat asking-a-human, and humans handle branches; pages that don't send readers back to the human.
  3. The worked example is half the teaching: one realistic case walked end-to-end ("requesting prod access for a new analyst: …") — readers pattern-match from examples faster than they parse instructions, and the example disambiguates everything the steps left abstract.
  4. The header makes it trustworthy: owner (who answers when the page is wrong), status, last-reviewed — without these, readers who've been burned by stale wikis re-ask the human anyway, and the page's ROI dies. The owner's review is 5 minutes on the heartbeat cadence.
  5. The pointer habit is the payoff loop: from publication day, every repeat ask gets "here you go: [link] — tell me if anything's unclear" — which (a) delivers the answer, (b) trains the link-first reflex, and (c) field-tests the page (every "the page didn't cover my case" is an edit, same day). Explaining orally after the page exists is paying twice for the same knowledge.
Show full SKILL.md (207 more words)Show less

Output Format

[Page title = the question, in the asker's words]

Owner: [name] · Status: active · Last reviewed: [date]

The Answer

[Steps/decision table/link — first screen, task-complete]

Worked Example

[One realistic end-to-end case]

Edge Cases & Branches

[The "unless…" forks, explicit]

Background (for the curious)

[Why it works this way · history · related pages]

Quality Checks

  • The first screen completes the modal reader's task
  • Branches from the oral version are visible forks, not omissions
  • The worked example is realistic and end-to-end
  • The header carries owner, status, and a real review date
  • The pointer habit started on publication day — the next ask got the link

Anti-Patterns

  • Do not open with history — the reader is mid-task; context is the appendix
  • Do not write the ideal process — document the real one, or the page and reality diverge and both lose trust
  • Do not skip the example to save time — it's the half of the page that actually teaches
  • Do not publish ownerless — orphan pages rot into the stale wiki that taught readers to re-ask humans
  • Do not keep explaining orally — every post-page explanation is a vote against your own infrastructure

Example Trigger Phrases

  • "Document how we do X."
  • "Write the wiki page for this process."
  • "I explain this every month."
  • "Make this knowledge survive me."

© mohitagw15856, MIT. 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/handbook-page of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Handbook Page 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.

Handbook Page compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Handbook Page this skillmohitagw15856/pm-claude-skills1.4k—~1.3kAutomated safety check: PassMIT
Logseq Review Workflow Evallogseq/logseq45k—~1kAutomated safety check: PassAGPL-3.0
Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill2.5k2 repos~3.2kAutomated safety check: PassNone
Obsidian CLIAtmosphere/atmosphere3.8k13 repos~795Automated safety check: PassApache-2.0
Esm Cjs Risk Scanlogseq/logseq45k—~3.3kAutomated safety check: PassAGPL-3.0
Knowledge Searchdataelement/bisheng12k—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…

    45k GitHub stars~1k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Baoyu URL To Markdown

    sdyckjq-lab/llm-wiki-skill

    Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.

    2.5k GitHub starsUsed in 2 repos~3.2k tokens
    Knowledge ManagementAuto-check passed
  • Obsidian CLI

    Atmosphere/atmosphere

    Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.

    3.8k GitHub starsUsed in 13 repos~795 tokens
    Knowledge ManagementAuto-check passed
  • Esm Cjs Risk Scan

    logseq/logseq

    Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.

    45k GitHub stars~3.3k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Knowledge Search

    dataelement/bisheng

    Search the user's knowledge bases and knowledge spaces (企业知识库检索).

    12k GitHub stars~1.1k tokensUpdated yesterday
    Knowledge ManagementAuto-check passed
  • Capture Conversation

    outline/outline

    Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.

    41k GitHub stars~474 tokensUpdated today
    Knowledge ManagementAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Handbook Page

What does Handbook Page 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…. Handbook Page is an agent skill from mohitagw15856/pm-claude-skills. 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.

When should I use Handbook Page?

Handbook Page fits situations like: asked document how we do X; write the wiki page for this process; I explain this every month; make this knowledge survive me.

How do I install Handbook Page in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill handbook-page -a claude-code`. Or copy the skill folder (skills/handbook-page in mohitagw15856/pm-claude-skills) into .claude/skills/handbook-page in your project. Claude Code loads it when a task matches its description.

How do I install Handbook Page in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill handbook-page -a codex`. Or copy the skill folder (skills/handbook-page in mohitagw15856/pm-claude-skills) into .agents/skills/handbook-page in your project. Codex loads it when a task matches its description.

Can I use Handbook Page 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 mohitagw15856/pm-claude-skills --skill handbook-page -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/handbook-page, .gemini/skills/handbook-page, .github/skills/handbook-page and .opencode/skills/handbook-page in your project.

What does Handbook Page need to run?

SKILL.md names no scripts, command-line tools or credentials: Handbook Page is instructions for the agent only.

Does Handbook Page 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 Handbook Page 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 Handbook Page use?

Handbook Page is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Handbook Page use?

About 1.3k tokens (SKILL.md is roughly 5.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 Handbook Page?

Skills that share tags, products or a category with Handbook Page: Logseq Review Workflow Eval (logseq/logseq, 45k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars) and Esm Cjs Risk Scan (logseq/logseq, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Handbook Page?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

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