pm-setup
Skill0 starsChanged 33 days agoMITView on GitHub
Creates the structure of a product manager's second brain in an empty folder. Use when the user says "set up my PM vault", "create a second brain", "настрой базу", "создай второй мозг", or runs /pm-setup.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Tetteh-Yaw-Precious/pm-setuptheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Tetteh-Yaw-Precious/pm-setup★ 0same name
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.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask which folder the base goes in.
- Very specific: line 15
Create the folders context/, topics/, raw/, calls/, decisions/, specs/, inbox/.
- Very specific: line 18
Create index.md — the map of the base.
- Distinctive: line 20
Ask which agents the person uses.
- Very specific: line 28
Ask whether there is already material lying around — a downloads folder, a chat export, a folder of meeting notes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Set up the base
Steps
- Ask which folder the base goes in. Offer the current one.
- Create the folders
context/,topics/,raw/,calls/,decisions/,specs/,inbox/. - Copy
AGENTS.mdfrom this skill into the root of the base. - Create
index.md— the map of the base. Sections: long-lived, current work, closed topics, decisions, specs, meetings. Empty for now. - Ask which agents the person uses. Create a pointer to
AGENTS.mdfor each:- Claude Code —
CLAUDE.md - Cursor —
.cursor/rules/pm-second-brain.mdc - Gemini CLI —
GEMINI.md - Codex —
AGENTS.mdalready works
- Claude Code —
- Offer to run
git initand make the first commit. - Show what was created and name the next step: describe the product in
context/and open the first topic with/pm-topic. - Ask whether there is already material lying around — a downloads folder, a
chat export, a folder of meeting notes. If there is, say to copy it into
inbox/and run/pm-inbox. Nothing has to be tidied first.
If the folder is not empty
Overwrite nothing. Say which files already exist and ask what to do.
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.

