From claude-superskills
Builds structured Obsidian notes from raw content with entity extraction, wikilinks, Zettelkasten atomic formatting, meeting notes, and knowledge graph integration.
npx claudepluginhub ericgandrade/claude-superskills --plugin claude-superskillsThis skill uses the workspace's default tool permissions.
This skill builds complete, knowledge-graph-ready Obsidian notes. It does more than just format text — it analyzes content to extract entities (people, projects, concepts, tools), converts those entities to wikilinks, chooses the right note type (atomic concept, project note, meeting note, daily note, reference note), and structures the output so it integrates with an existing vault's linking a...
Generates Obsidian Flavored Markdown with wikilinks, callouts, embeds, frontmatter properties, tags, and block references for creating/editing notes in Obsidian vaults.
Manages Obsidian vaults: search, create, edit, move Markdown notes; handle YAML frontmatter, wikilinks, backlinks, daily notes, Zettelkasten setup, and sync via obsidian-cli.
Builds and maintains persistent Obsidian wiki vaults using AI for source ingestion, knowledge querying, note linting, and autonomous research.
Share bugs, ideas, or general feedback.
This skill builds complete, knowledge-graph-ready Obsidian notes. It does more than just format text — it analyzes content to extract entities (people, projects, concepts, tools), converts those entities to wikilinks, chooses the right note type (atomic concept, project note, meeting note, daily note, reference note), and structures the output so it integrates with an existing vault's linking and tagging conventions.
The result is a note that is immediately navigable in Obsidian, discoverable through search and Dataview, and connected to the knowledge graph via bidirectional links.
Invoke this skill when:
Do NOT use this skill when:
obsidian-frontmatter insteadobsidian-links insteadobsidian-automation insteadAn atomic note captures exactly one idea. It is self-contained, evergreen, and heavily linked:
---
title: <Concept Name>
date: YYYY-MM-DD
tags:
- concept
- <topic>
aliases:
- <alternative name>
---
# <Concept Name>
<One to three paragraph clear definition of the concept.>
## Key Principles
- <Principle 1>
- <Principle 2>
## Related Concepts
- [[Related Concept A]] — brief relationship description
- [[Related Concept B]] — brief relationship description
## Sources
- [[Book or Article Title]] by Author Name
---
title: <Meeting Title — Date>
date: YYYY-MM-DD
tags:
- meeting
attendees:
- "[[Person One]]"
- "[[Person Two]]"
project: "[[Project Name]]"
status: done
---
# <Meeting Title>
**Date:** [[YYYY-MM-DD]]
**Attendees:** [[Person One]], [[Person Two]]
## Agenda
1. Topic One
2. Topic Two
## Notes
<Structured notes by agenda item>
## Decisions
- <Decision 1>
## Action Items
- [ ] <Task> — assigned to [[Person]]
## Next Meeting
[[Next Meeting Note]] scheduled for <date>
---
title: <Resource Title>
date: YYYY-MM-DD
tags:
- reference
- <topic>
source: "<URL or citation>"
author: <Author Name>
read_date: YYYY-MM-DD
rating: <1-5>
---
# <Resource Title>
> <One-line summary of the resource's main argument or value>
## Key Takeaways
- <Takeaway 1>
- <Takeaway 2>
## Quotes
> "<Memorable quote>" — <Author>
## How It Connects
- Relevant to [[Project X]] because...
- Supports the ideas in [[Concept Y]]
---
title: <Project Name>
date: YYYY-MM-DD
status: active
priority: medium
tags:
- project
stakeholders:
- "[[Person]]"
due_date: YYYY-MM-DD
---
# <Project Name>
> <One-sentence project description>
## Goal
<What success looks like>
## Status
<Current state of the project>
## Key Decisions
- <Decision with [[Meeting Note]] link>
## Resources
- [[Related Document]]
- [[Team Member]]
## Next Actions
- [ ] <Task>
Before building the note, understand the vault:
find <vault-root> -name "*.md" | xargs grep -l "<key terms>" 2>/dev/null | head 10
grep -rh "^ - " <vault-root>/**/*.md | sort | uniq -c | sort -rn | head 20
Read the user's input and determine:
If ambiguous, ask: "What type of note should this be — a concept note, meeting note, reference note, or project note?"
Scan the input text for entities that should become wikilinks:
Entity categories to extract:
Entity extraction rules:
[[New Concept]] ⟵ create this noteApply the appropriate template from the note types above. Then:
obsidian-frontmatter conventions (multiline lists, ISO dates, quoted wikilinks)For atomic concept notes:
Output the full Markdown content of the note including frontmatter. After the note, list:
[[Product Discovery|discovery process]][[Alice Chen|Alice]]NEVER:
# for title, ## for sections, ### for subsections)ALWAYS:
--- on line 1 with no blank line before it/, ?, #, ^, [, ], | characters)## See Also or ## Related sectionExample 1: Convert a brain dump into an atomic concept note
User: "Turn this into a proper Obsidian note: 'Evergreen notes are notes designed to accumulate insight over time. Unlike fleeting notes, they are written to stand alone. Key principle from Andy Matuschak.'"
Output:
---
title: Evergreen Notes
date: 2024-01-15
tags:
- concept
- note-taking
aliases:
- Evergreen Note
---
# Evergreen Notes
Evergreen notes are permanent notes designed to accumulate insight over time. Unlike fleeting notes captured in the moment, evergreen notes are written with enough context to stand alone and remain useful long after the writing session.
## Key Principles
- Write for your future self, not just for now
- Each note captures one idea fully and clearly
- Notes are revised and updated as understanding deepens
## Origin
Coined by [[Andy Matuschak]] as part of his writing practice.
## Related Concepts
- [[Atomic Notes]] — evergreen notes are always atomic
- [[Fleeting Notes]] — the raw capture stage before evergreen refinement
- [[Zettelkasten]] — the system that popularized this practice
## See Also
- [[Note-Taking Workflow]]
Example 2: Structure a meeting summary
User: "Create a meeting note for today's Q2 Planning session. Alice Chen and Bob Martinez attended. We decided to push the launch date to March 15. Bob owns the announcement. Next meeting in two weeks."
Output: Complete meeting note with frontmatter, structured agenda/notes/decisions/actions, wikilinks for Alice Chen, Bob Martinez, and the action item, plus a flag to create [[Q2 Planning — 2024-02-15]] for the next meeting.
Example 3: Build a reference note from book highlights
User: "Create a reference note for the book 'Building a Second Brain' by Tiago Forte. Key ideas: CODE method (Capture, Organize, Distill, Express), progressive summarization, project vs area vs resource vs archive (PARA)."
Output: A reference note with frontmatter (title, author, tags), key takeaways as bullets, the CODE and PARA acronyms explained, and wikilinks to [[Progressive Summarization]], [[PARA Method]], etc. as candidates for future atomic notes.
Example 4: Import web article content into vault
User: "Add this article summary to my vault as a reference note: [article excerpt provided]"
Example 5: Split a large note into atomic notes
User: "This note has become too big. Split it into separate atomic notes, one per concept."