Menu

Individual skill

curate-project-memory

Give Codex lasting project context in a local Obsidian-compatible Markdown vault. Use when a user asks PMC to set up or connect the project's Obsidian vault, scan or explain a codebase, create a Project Home, remember a decision, constraint, discovery, procedure, debugging lesson, or current state, recall what Codex already knows, prepare a handoff, check whether notes are stale or contradictory, relate code to knowledge, keep something session-only, export or share reviewed context, or resume work from existing project notes.

plugins/DuncanMain/project-memory-core/skills/curate-project-memory/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Curate Project Memory

Use conversation as the interface. Do not ask the user to run commands or edit configuration manually. Use Codex's normal file tools and request narrowly scoped filesystem permission when needed.

## First-run experience

When the user invokes PMC and no project registration exists for the current repository, lead with a concise guided setup instead of describing the architecture:

1. Explain in one sentence: "PMC gives Codex lasting project context in an Obsidian vault you control."
2. Ask whether to create a new vault or connect an existing Obsidian vault. Ask only this one question first.
3. After that choice, ask for or confirm the vault path, infer the current repository, and propose a readable project name.
4. Complete the vault setup and project registration conversationally. Do not require the user to know commands, markers, folder layouts, or configuration formats.
5. Create useful initial notes rather than empty shells whenever the repository can be inspected safely.
6. At completion, state where the vault and project notes live, explain how to open the vault in Obsidian, and offer to scan the repository now.