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".
In this repository68 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- ai-engineering-chip-huyenSkill
- ask-mattSkill
- book-to-skillSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- daily-noteSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- getContextSizeSkill
- git-guardrails-claude-codeSkill
- graphify-querySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- knowledge-linkSkill
- knowledge-synthesisSkill
- loop-meSkill
- master-plan-builderSkill
- migrate-to-shoehornSkill
- note-reviewSkill
- notion-curatorSkill
- obsidian-knowledge-curatorSkill
- okc-bookFlashcardsSkill
- okc-bookSummarySkill
- okc-diagnosticsAndSynchronizationSkill
- okc-docSkill
- okc-doctorSkill
- okc-driftSkill
- okc-emergeSkill
- okc-exploreSkill
- okc-findSkill
- okc-linterSkill
- okc-normalizeSkill
- okc-setupSkill
- okc-study-multichoiceSkill
- okc-studySkill
- okc-syncSkill
- okc-traceSkill
- okc-urlArticleSkill
- okc-urlPlaylistSkill
- okc-urlPodcastSkill
- okc-urlSpotifySkill
- okc-urlTwitterSkill
- okc-urlYoutubeSkill
- prototypeSkill
- researchSkill
- resolving-merge-conflictsSkill
- scaffold-exercisesSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- tddSkill
- teachSkill
- to-specSkill
- to-ticketsSkill
- The first 60 shown.
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
- Distinctive: line 30
If a note on the same topic already exists → update it, don't create a new one.
- Distinctive: line 95
After saving, update or create the category's Master Plan:
- Distinctive: line 102
Never use YAML frontmatter
- Very specific: line 103
Never use emojis outside of ## 📌 Key Takeaways
- Very specific: line 105
Never invent content — mark unavailable info as [NOT AVAILABLE]
- Distinctive: line 106
Always check for duplicates before creating
- Distinctive: line 113
No duplicates found → create new note
≈ “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.
Files
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 operatingStep 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=5If 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 type | Naming pattern | Target folder |
| YouTube video (series) | Series ## — Title.md | <RootFolder>/<Category>/ |
| YouTube video (standalone) | Channel — Video Title.md | <RootFolder>/<Category>/ |
| Article / web | Publication — Title.md | <RootFolder>/<Category>/ |
| Raw idea / concept | Concept — Descriptive Title.md | <RootFolder>/<Category>/ |
| Master plan | Master 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 oneConstraints
- 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"
- Search:
obsidian search query="AI agents memory" limit=5 - No duplicates found → create new note
- Target:
dataScienceKnowledgeBase/AI Engineer/Agents/Concept — AI Agents External Memory.md - Validate → write → verify → update Master Plan if exists
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
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.

