How do I install the Second Brain Project skill?

Run npx skillmds@latest add undefined-ui/second-brain-project in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Second Brain Project safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Second Brain Project?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Second Brain Project free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Second Brain Project?

undefined-ui (@undefined-ui) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Second Brain Project by undefined-ui

Name: Second Brain Project
Author: undefined-ui

Second Brain Project

Set up or update a project in the vault: the four-stage folder pipeline, a project-scoped CLAUDE.md with one goal, and links to the concept pages it depends on. Use this skill when the user starts something new they will work on over time, says "create a project", "set up a folder for X", or asks to define the goal and structure of ongoing work. Do NOT use for one-off tasks, for wiki pages about a topic, or for scoping an existing project down to work in it.

undefined-ui 4e2107e 1.9 KB Updated Sep 17, 2026

File contents

Set up a project

The knowledge layer answers what you know. The project layer answers what you are doing this week. Merging them fills a wiki with dead task lists and buries working files under conceptual notes.

Core rule

One goal per project, stated in its own CLAUDE.md. A project with three goals is three projects.

Workflow

Interview if needed. What this produces, for whom, by when, and what the agent's role is. Vague answers produce a file that makes every future session worse.
Create the folders: Inputs/, Process/, Outputs/, Feedback/.
Write the project CLAUDE.md: what this is, the one goal with a date, your role, working rules, current state. Name what the agent should not do here as well.
Link the knowledge layer. Find concept pages the project depends on and reference them from the project file. Copy into Inputs/ only the few that genuinely matter.
Register it in the root CLAUDE.md project list.

Output format

Project: <name>
Goal: <one measurable outcome with a date>
Folders created: Inputs, Process, Outputs, Feedback
Concept pages linked: <list>
Agent role: <one line>

Calibration

Feedback/ is the folder people skip and the one that makes the system improve. If the user has no idea what would go in it, that is worth surfacing: it usually means the goal is not measurable yet.

Do not create a project for work that finishes this week. That is a task.

---name: second-brain-projectdescription: Set up or update a project in the vault: the four-stage folder pipeline, a project-scoped CLAUDE.md with one goal, and links to the concept pages it depends on. Use this skill when the user starts something new they will work on over time, says "create a project", "set up a folder for X", or asks to define the goal and structure of ongoing work. Do NOT use for one-off tasks, for wiki pages about a topic, or for scoping an existing project down to work in it.---# Set up a projectThe knowledge layer answers what you know. The project layer answers what youare doing this week. Merging them fills a wiki with dead task lists and buriesworking files under conceptual notes.## Core ruleOne goal per project, stated in its own `CLAUDE.md`. A project with three goalsis three projects.## Workflow1. **Interview if needed.** What this produces, for whom, by when, and what the agent's role is. Vague answers produce a file that makes every future session worse.2. **Create the folders:** `Inputs/`, `Process/`, `Outputs/`, `Feedback/`.3. **Write the project `CLAUDE.md`:** what this is, the one goal with a date, your role, working rules, current state. Name what the agent should not do here as well.4. **Link the knowledge layer.** Find concept pages the project depends on and reference them from the project file. Copy into `Inputs/` only the few that genuinely matter.5. **Register it** in the root `CLAUDE.md` project list.## Output format```Project: <name>Goal: <one measurable outcome with a date>Folders created: Inputs, Process, Outputs, FeedbackConcept pages linked: <list>Agent role: <one line>```## Calibration`Feedback/` is the folder people skip and the one that makes the system improve.If the user has no idea what would go in it, that is worth surfacing: it usuallymeans the goal is not measurable yet.Do not create a project for work that finishes this week. That is a task.

Frequently asked questions