agentleFS
c-ibarrac-ibarra/ObsidianKnowledgeCurator/.agents/skills/note-capture/SKILL.md

note-capture

Skill0 starsChanged 43 days agoMITView on GitHub

Use this skill when the user wants to capture a new idea, article, quote, meeting note, or any raw content into the Obsidian vault. Triggers include "capture this", "save this to my vault", "add a note about", "turn this into a note".

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a note on the same topic already exists → update it, don't create a new one.

    line 30
  2. Distinctive:

    After saving, update or create the category's Master Plan:

    line 95
  3. Distinctive:

    Never use YAML frontmatter

    line 102
  4. Very specific:

    Never use emojis outside of ## 📌 Key Takeaways

    line 103
  5. Very specific:

    Never invent content — mark unavailable info as [NOT AVAILABLE]

    line 105
  6. Distinctive:

    Always check for duplicates before creating

    line 106
  7. Distinctive:

    No duplicates found → create new note

    line 113

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

Note Capture Skill

Goal

Transform raw input into a structured Obsidian note that follows the vault's conventions exactly — no YAML, blockquote header, correct naming, correct sections — and save it to the right folder under the appropriate <RootFolder>.

Prerequisites

# 1. Obsidian must be open
pgrep -x Obsidian > /dev/null && echo "open" || echo "CLOSED"

# 2. Read obsidian-cli skill before operating

Step 1 — Analyze vault before acting

# Check existing folder structure
obsidian folders
obsidian files folder="<RootFolder>" total

# Search for duplicates
obsidian search query="<core topic>" limit=5

If a note on the same topic already exists → update it, don't create a new one.

⚠️ Never touch: dataScienceKnowledgeBase/dswok

Step 2 — Determine note type and target path

Input typeNaming patternTarget folder
YouTube video (series)Series ## — Title.md<RootFolder>/<Category>/
YouTube video (standalone)Channel — Video Title.md<RootFolder>/<Category>/
Article / webPublication — Title.md<RootFolder>/<Category>/
Raw idea / conceptConcept — Descriptive Title.md<RootFolder>/<Category>/
Master planMaster Plan — Series Name.md<RootFolder>/<Category>/

Step 3 — Build note structure (no YAML, ever)

# Descriptive Title

> **Author — Descriptive Title**
> Source: Source description
> Channel/Author: Name · Date: Month Year
> Type: article | video | analysis
> Tags: #no-read-yet

## 📌 Key Takeaways
1. ...
2. ...
3. ...

## 1. Thematic Section
...

## 2. Thematic Section
...

## Flashcards
Q: Question
A: Answer

## Glossary
**Term**: Definition (only non-obvious technical terms)

## Related
- [[Existing note in the vault]]

Step 4 — Validate with superpowers before writing

  • No YAML frontmatter
  • Header blockquote with Tags: #no-read-yet
  • File name follows the naming convention
  • [[links]] in Related exist in the vault
  • No hallucinated content
  • Category is consistent with the vault

Step 5 — Write to vault

# Create new note
obsidian create path="<RootFolder>/<Category>/<Note Name>.md" \
  content="<content>" silent

# Verify
obsidian read file="<Note Name>"

After saving, update or create the category's Master Plan:

obsidian search query="Master Plan <Category>" limit=3
# append note link to existing Master Plan, or create one

Constraints

  • Never use YAML frontmatter
  • Never use emojis outside of ## 📌 Key Takeaways
  • Never touch dataScienceKnowledgeBase/dswok
  • Never invent content — mark unavailable info as [NOT AVAILABLE]
  • Always check for duplicates before creating

Example

Input: "Capture this idea: AI agents are better with external memory"

  1. Search: obsidian search query="AI agents memory" limit=5
  2. No duplicates found → create new note
  3. Target: dataScienceKnowledgeBase/AI Engineer/Agents/Concept — AI Agents External Memory.md
  4. Validate → write → verify → update Master Plan if exists

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.