Skip to content
Back to skills

Man

ASecurity

The forge's manual, read from its own definitions — bare = the commands and the working methods, with a command = its purpose, arguments and roster, with a method = its paragraph and skill

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 20, 2026
tools

Works with

  • claude code

Security analysis

A100/100

Scanned October 4, 2026

npx -y skills add pche-broken-artist/forge-of-thought --skill man --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Man?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Man
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pche-broken-artist-man/badge)](https://www.skillsdirectory.com/skills/pche-broken-artist-man)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: The forge's manual, read from its own definitions — bare = the commands and the working methods, with a command = its purpose, arguments and roster, with a method = its paragraph and skill
argument-hint: "[command | method]"
---

The manual of the forge (POS.1190): a reader, never a text of its
own. Everything it prints is read at the moment of the call from the
files that own it — CLAUDE.md, the skills, the agents, the state and
genre files — and shortened to the line; nothing is stated here that
lives there. Read-only; it runs no command it describes. Alias:
`/manual` (`.claude/skills/manual/SKILL.md`). The word `help` is
Claude Code's own command, hence the Unix name.

**Bare `/man` — the overview.**
1. Read the Commands table of CLAUDE.md and print it as a list: the
   command with its arguments, then its purpose cut to one line.
   `/man` and `/manual` included.
2. Read the Working methods section of CLAUDE.md and print each
   method's name with the first sentence of its paragraph.
3. Close with one line: `/man <command>` for a command's page,
   `/man <method>` for a method's.

**`/man <command>` — the page of one command.**
1. Resolve `$0` to `.claude/skills/<command>/SKILL.md`; if none
   exists, say so and list the commands (step 1 of the overview).
2. Print the command's purpose (its `description`), its arguments
   (its `argument-hint`, else the CLAUDE.md row) and the CLAUDE.md
   row's purpose in full.
3. Print the roster the command dispatches over, where its skill
   names one: the same scan the bare command makes, read from that
   skill, each entry with the `description` of its own file and,
   where the file carries one, its `## Lens` section — for a genre
   its Elicitation checklist — in full, so that the user knows what
   a check, a lens, a persona or a genre looks for before running
   it. `/man` adds what each entry looks for and runs nothing.
4. Close with one line naming the skill file, for the reader who
   wants the whole procedure.

**`/man <method>` — the page of one working method.** Resolve `$0`
against the bold names of the Working methods section of CLAUDE.md
(case-insensitive, hyphens and spaces alike); print the paragraph in
full and, where it names a skill that holds the method's shape,
that skill's path. Unknown: say so and list the methods (step 2 of
the overview).

Language: the conversation language (CLAUDE.md, prime directive 6 —
translate on write), the whole page, descriptions and Lens sections
included; only the notation stays English — command names, file
paths, IDs, front-matter keys and the bold names of the methods,
each followed by its translation once.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…