agentleFS
andymaiandymai/claude-agent-team/skills/obsidian-project/SKILL.md

obsidian-project

Skill4 starsChanged yesterdayMITView on GitHub

Start a new project in an Obsidian vault. It writes one folder of prefix-named notes (overview, PRD, architecture, research, tasks), links them, and adds the project to the vault's index. Use when the user asks to start, set up, or scaffold a project, a project folder, or project docs in Obsidian or in their vault. Also holds the conventions for links, tags, and tasks when you update those notes later.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 1

    1. andymai/skills★ 4100% same

    Edited · 0

    None found.

    Wrote their own version · 2

    1. aiqianqian521/obsidian-skills★ 1same name
    2. mjeffrey18/skills★ 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.

  • In this repository8 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 6 are distinctive, and 11 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 11

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create one folder of linked notes for a new project in an Obsidian vault, then add the project to the vault's index.

    line 14
  2. Distinctive:

    Use the first rule that gives you one folder:

    line 20
  3. Distinctive:

    If the search finds no vault or more than one, ask the user which folder to use.

    line 31
  4. Distinctive:

    Read CLAUDE.md, AGENTS.md, and README.md at the vault root if they exist.

    line 38
  5. Very specific:

    If the check does not print ok, ask the user for a different name.

    line 58
  6. Very specific:

    If <vault>/Projects/ does not exist, ask the user where projects go, or if you can create Projects/.

    line 73
  7. Very specific:

    Create <vault>/Projects/{name}/.

    line 78
  8. Very specific:

    Before you write research, search the vault for earlier notes on the same topic.

    line 101
  9. Very specific:

    Look for an index note with a list of projects.

    line 107
  10. Distinctive:

    Run each check, and fix any failure before you report:

    line 115
  11. Very specific:

    Links: use wikilinks with the project prefix, such as [[{name}-prd]].

    line 136
  12. Very specific:

    Other Obsidian syntax: if the skills of the obsidian plugin are installed (obsidian:obsidian-markdown, obsidian:obsidian-cli), follow them …

    line 145
  13. Very specific:

    Tags: use frontmatter arrays only, such as tags: [prd, draft].

    line 148
  14. Very specific:

    Tasks: use plain - [ ] and - [x] lines.

    line 152
  15. Distinctive:

    Settled rules: when work settles a rule, write it into the architecture note where it applies, and state what is true now.

    line 153
  16. Very specific:

    More notes: when a topic outgrows its section, give it its own note with the same prefix, such as {name}-roadmap.md.

    line 156
  17. Distinctive:

    Status changes: when the project becomes active, blocked, or archived, change the status tag in each note and update the project's line in …

    line 162

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Obsidian project

Create one folder of linked notes for a new project in an Obsidian vault, then add the project to the vault's index. Each note starts from a template in ${CLAUDE_PLUGIN_ROOT}/skills/obsidian-project/templates/.

1. Find the vault

Use the first rule that gives you one folder:

  1. The user names the vault folder.
  2. The user's CLAUDE.md or memory gives the vault path.
  3. A search of the home folder finds exactly one vault. Each match's parent folder is a vault:

    find ~ -maxdepth 4 -type d -name .obsidian -not -path '*/.Trash/*' 2>/dev/null

If the search finds no vault or more than one, ask the user which folder to use. Do not guess.

Gate: do not continue until you have one vault folder and it exists.

2. Read the vault's own rules

Read CLAUDE.md, AGENTS.md, and README.md at the vault root if they exist. If one of them describes a project layout, follow that layout instead of these templates, and say so in the report. The vault's rules win over this skill.

3. Name the project

  • {title}: the project name as the user writes it.
  • {name}: the file prefix. If the project has a repo, use the repo name in lowercase. Otherwise, write {title} in lowercase. Change each space, and each character that is not a letter, a digit, -, or _, to one hyphen. Example: "CI/CD Dashboard" gives ci-cd-dashboard.
  • {date}: today, as YYYY-MM-DD.

Gate: {name} becomes a folder name and part of each file name, so it must pass this check. Put the name in place of <name>:

printf '%s' '<name>' | grep -Eq '^[a-z0-9][a-z0-9_-]*$' && echo ok

If the check does not print ok, ask the user for a different name.

Obsidian finds a wikilink's note by file name anywhere in the vault, so each file name must be unique. Check the five names before you write anything:

find "<vault>" -type f \( -name "{name}.md" -o -name "{name}-prd.md" \
  -o -name "{name}-architecture.md" -o -name "{name}-research.md" \
  -o -name "{name}-tasks.md" \) -not -path '*/.trash/*'
ls -d "<vault>/Projects/{name}" 2>/dev/null

Gate: if either command prints a path, stop and ask the user for a different name. Do not overwrite or merge notes.

If <vault>/Projects/ does not exist, ask the user where projects go, or if you can create Projects/.

4. Write the notes

Create <vault>/Projects/{name}/. For each template, read it, replace every {name}, {title}, and {date}, and write the note:

TemplateNote
overview.md{name}.md
prd.md{name}-prd.md
architecture.md{name}-architecture.md
research.md{name}-research.md
tasks.md{name}-tasks.md

Fill a section only from what the user told you or what you read in this session. Good sources are the repo, a linked doc, and earlier notes in the vault. Where you have nothing, keep the template's %% ... %% prompt. Obsidian hides these comments in reading view. Never invent goals, requirements, metrics, or stack choices to fill a section.

Example. The user says "a CLI that renames photos by EXIF date, in Rust".

  • Good: the Stack table gets | CLI | Rust | The user's choice |. The Problem section keeps its prompt.
  • Bad: a Problem paragraph about "photographers who lose hours to sorting files". Nobody said that.

Before you write research, search the vault for earlier notes on the same topic. Look in Knowledge/ first if it exists. Link those notes from the research note, and do not repeat their content.

5. Add the project to the index

Look for an index note with a list of projects. This note is a map of content, often index.md or Home.md. If you find one, add one line for the new project, such as - [[{name}]]: <one sentence about the project>. Match the format of the lines next to it. If the vault has no such list, skip this step and say so in the report. Do not create an index.

6. Check, then report

Run each check, and fix any failure before you report:

  • ls "<vault>/Projects/{name}" shows the five notes.
  • No note still has a placeholder. In this command, replace only the folder path, and keep the three search terms with their braces: grep -rnF -e '{name}' -e '{title}' -e '{date}' "<vault>/Projects/<project folder>". It must print nothing.
  • Each [[...]] link in the overview names a note that exists.
  • Each note starts with frontmatter that has a tags: array.

Report these items:

  • The folder path and the five notes.
  • What you filled, and where each fact came from.
  • The sections that still have only a prompt.
  • The index line, or why you skipped it.

Conventions for project notes

These rules apply when you write the notes and when you update them later.

  • Links: use wikilinks with the project prefix, such as [[{name}-prd]]. The prefix keeps file names unique, so a link never opens another project's note.
  • Link syntax: these three rules prevent links that look correct and do not work.
    • A wikilink finds its note by file name, never by an aliases property. To show different text, write [[{name}-prd|PRD]].
    • In frontmatter, put a wikilink in quotes, such as related: "[[{name}-prd]]". Without the quotes, YAML reads it as a nested list.
    • In a table, put a backslash before the pipe of an alias: [[{name}-prd\|PRD]]. Without it, the pipe starts a new table cell.
  • Other Obsidian syntax: if the skills of the obsidian plugin are installed (obsidian:obsidian-markdown, obsidian:obsidian-cli), follow them for callouts, embeds, properties, and vault commands. This skill does not repeat them.
  • Tags: use frontmatter arrays only, such as tags: [prd, draft].
    • Status: active, draft, blocked, archived.
    • Type: project, prd, architecture, research, task, knowledge.
    • Domain, if it helps: web, cli, infra, api, mobile, data.
  • Tasks: use plain - [ ] and - [x] lines. Do not add emoji dates or priorities.
  • Settled rules: when work settles a rule, write it into the architecture note where it applies, and state what is true now. Do not keep a separate decision log, because old entries fill the context with history.
  • More notes: when a topic outgrows its section, give it its own note with the same prefix, such as {name}-roadmap.md. Link the new note from the overview's Quick Links.
  • Rename or move: rename or move a note with Obsidian, so that Obsidian updates the links to it. Use the app, or obsidian rename and obsidian move if the Obsidian CLI is available. If you must use the file system, search the vault for [[<old name> in the same step, and fix each link that you find.
  • Status changes: when the project becomes active, blocked, or archived, change the status tag in each note and update the project's line in the index.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.