Help us improve
Share bugs, ideas, or general feedback.
From skills
Creates or updates PARA project notes in an Obsidian vault with structured fields (outcome, deadline, status, next action).
npx claudepluginhub kriscard/skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/skills:projectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create or update project notes in `1 - Projects/`. A Project in PARA requires both an outcome (a
Creates and edits notes in PKM vault using templates for ADR, research, tasks, meetings; duplicate checks via semantic search, link discovery, annotations, index updates.
Provides persistent Obsidian vault memory for coding agents. Auto-orients sessions with TODOs and project overviews, supports lookup of notes/patterns, and writes discoveries using commands like init, lookup, note.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Create or update project notes in 1 - Projects/. A Project in PARA requires both an outcome (a
checkable "done" state) and a deadline — without both, it belongs in 2 - Areas/.
Classify the request before doing anything:
| Signal | Mode |
|---|---|
| "Create / new / set up / track" | CREATE |
| "Update / refresh / status / done" | UPDATE |
| Ambiguous | Ask: "Create new or update existing?" |
Check if a project note already exists:
obsidian search query="<project name>"
obsidian files folder="1 - Projects/" format=json
If a close match exists, surface it and confirm before proceeding.
A project needs both a discrete outcome and a deadline. Ask via AskUserQuestion:
If "no deadline" or no discrete outcome: propose 2 - Areas/ instead. Don't create a project note
for things that never end.
Single AskUserQuestion call (batch to minimize round-trips):
1 - Projects/<Project Name>.md1 - Projects/<Project Name>/ only if user mentions sub-notes (architecture
docs, PRDs, strategy notes)obsidian create path="1 - Projects/<Name>.md" template="Project"
Set frontmatter with obsidian property:set and fill the sections with gathered details. The CLI
has no patch for section edits — if a section must be targeted, ask the user (MCP
obsidian_patch_content or recreate via read + create ... overwrite). Always show a preview and
wait for confirmation before writing.
obsidian search query="Active Projects"
If found, append a wikilink to the new project.
If named, resolve to file path. Otherwise list and ask:
obsidian files folder="1 - Projects/" format=json
Read the project file. Look for:
Updated: more than 14 days ago → flag for refreshPrefer not to rewrite the full file. The CLI has no patch, so a section-targeted update means
either the MCP obsidian_patch_content tool (heading-targeted) or a read + create ... overwrite
rewrite. Ask the user which to use, then update the Current Status section and bump the
Updated: YYYY-MM-DD marker to today.
If the user says "this project is done":
4 - Archives/Projects - YYYY/<Name>.mdstatus: ✅ Done| Priority | Load when | Reference |
|---|---|---|
| 1 — First | Building the intake interview — need exact question wording or option lists | references/interview-questions.md |
| 2 — Context | User questions PARA principles, Hot/Cold classification, or why outcome+deadline is required | references/tiago-principles.md |