help
Skill138 starsChanged 7 months agoMITView on GitHub
PM-Kit command reference and workflow guide. Use for "/help", "what commands are available", "how do I use PM-Kit", "cheat sheet", "show me workflows", or "/help preview" for topic-specific help.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 53 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
If topic not found, show cheat sheet and suggest closest match.
- Very specific: line 54
Read handbook/HELP_GUIDE.md and extract the relevant section(s).
- Very specific: line 107
If user says /help all or "list all skills":
“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/help — PM-Kit Help Guide
Surface the command reference and workflow guide. Read-only — no files created.
Context
Full guide: @handbook/HELP_GUIDE.md Config: @_core/config.yaml Workflow examples: @handbook/WORKFLOW_EXAMPLES.md Processing flows: @_core/PROCESSING.md
Usage
/help
/help daily
/help preview
/help report
/help export
/help integrations
/help workflow
/help foldersProcessing Steps
1. Parse Topic
| Input | Action |
| No args | Show quick cheat sheet + category overview |
daily, today | Daily operations section |
preview, html | Preview & HTML artifact section |
report, executive | Report to me section + vs /progress |
export, xlsx, docx, pdf, pptx | Export flags section |
integrations, jira, linear, notion | Integrations section |
workflow, routine | Recommended workflows section |
folders, structure, paths | Folder map section |
ask, qmd | Capture & retrieval section |
setup, onboard | Setup & maintenance section |
{command} | Look up specific command in HELP_GUIDE.md |
If topic not found, show cheat sheet and suggest closest match.
2. Load Content
Read handbook/HELP_GUIDE.md and extract the relevant section(s).
For specific commands, also check if .claude/skills/{command}/SKILL.md exists — include one-line description and example invocation.
3. Format Output
Default (/help):
# PM-Kit Help
## Quick Cheat Sheet
{table from HELP_GUIDE.md}
## Categories
- **Daily:** /today, /daily, /progress, /report, /weekly, /push
- **Artifacts:** /doc, /decide, /block, /meet
- **Preview:** /preview, /report --preview
- **Export:** --xlsx, --docx, --pdf, --pptx
- **Capture:** /inbox, /ask
- **Maintenance:** /onboard, /health, /update, /help
## New here?
/onboard → /today → /daily project-a: shipped X, wip Y
Full guide: handbook/HELP_GUIDE.mdTopic-specific (/help preview):
Return only that section from HELP_GUIDE.md, plus 2-3 example commands.
4. Suggest Next Command
End with one contextual suggestion based on time of day or topic:
| Context | Suggestion |
| Morning / daily topic | "Try: /today or /daily project-a: ..." |
| Preview topic | "Try: /preview docs/{project}/{slug}.md" |
| Report topic | "Try: /report all or /report --preview" |
| No topic, Friday | "It's Friday — try /weekly then /report all --preview" |
| Default | "Try: /help workflow for full daily routine" |
Rules
- Read-only — never create or modify files
- Concise — cheat sheet first, details on request
- Point to handbook — for deep dives, cite
handbook/HELP_GUIDE.md - No skill dumping — don't list all 34 skills unless user asks for "all skills"
List All Skills (only when asked)
If user says /help all or "list all skills":
Glob: .claude/skills/*/SKILL.mdOutput table: Command | One-line description | User-invocable?
Group by category matching HELP_GUIDE.md structure.
Other versions71 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 71
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- indranilbanerjee/digital-marketing-pro★ 920same name
- waynesutton/markdown-site★ 628same name
- bitwize-music-studio/claude-ai-music-skills★ 589same name
- andrew-shwetzer/career-ops-plugin★ 501same name
- andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-★ 500same name
61 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use create-stories, story-done and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 9 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 9 projects that use this
- +10 more from lilangMax
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- askSkill
- blockSkill
- dailySkill
- decideSkill
- discoverSkill
- docSkill
- docxSkill
- excalidraw-generatorSkill
- explainSkill
- gwsSkill
- healthSkill
- inboxSkill
- interviewSkill
- jiraSkill
- journeySkill
- json-canvasSkill
- linearSkill
- meetSkill
- mermaid-visualizerSkill
- notionSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- onboardSkill
- pdfSkill
- pptxSkill
- previewSkill
- prioritizeSkill
- progressSkill
- pushSkill
- reportSkill
- show-meSkill
- skill-creatorSkill
- todaySkill
- updateSkill
- vault-opsSkill
- weeklySkill
- xlsxSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

