notes
Creates and manages Obsidian notes for projects, technical challenges, brag documents, meeting transcriptions, and company tracking using MCPVault MCP. Use when documenting projects, recording technical challenges, maintaining brag documents, preserving meeting and course transcriptions, or tracking job applications. Triggers: "create project note", "new project note", "technical challenge", "brag document", "achievement", "accomplishment", "transcription", "meeting notes", "1:1 notes", "feedback notes", "standup notes", "lecture notes", "course notes", "company note", "track interview", "job application". Not for end-of-session persistence across memory systems or for initializing repository-wide project context.
What this skill does
# Notes
Creates and manages Obsidian notes using MCPVault MCP for structured documentation.
## Workflow
```
resolve-vault --> select-type --> compose-note --> write --> link-related
```
Each note type has its own workflow. Use any type independently.
## Triggers
- **Project note** ("create project", "new project note", "document
project") → [project.md](references/project.md)
- **Challenge note** ("technical challenge", "take-home", "coding
interview", "system design") → [challenge.md](references/challenge.md)
- **Brag entry** ("brag document", "achievement", "accomplishment")
→ [brag.md](references/brag.md)
- **Transcription** ("transcription", "meeting notes", "1:1 notes",
"feedback notes", "standup notes", "lecture notes", "course notes")
→ [transcription.md](references/transcription.md)
- **Company tracking** ("company note", "track interview", "job
application") → [company.md](references/company.md)
- **Markdown syntax help** ("wikilink", "callout", "embed", "Obsidian
syntax") → [markdown.md](references/markdown.md)
`mapping.md` is loaded by the note-creation refs to resolve vault paths;
not a direct trigger. `markdown.md` is an informational reference with
no write operations.
## Filename Sanitization
When generating filenames from user input:
- Remove invalid characters: `/ \ : * ? " < > |`
- Replace accented characters with ASCII equivalents (e.g., `é` → `e`,
`ã` → `a`)
- Use Title Case for all filenames
- Example: `What's Next?` becomes `Whats Next.md`
## Writing Style
- Body: rich prose context after the heading, not just bullet points
- Bullets: describe what happened and why, with enough context to
understand weeks later
- Observations: `#category content` syntax — Obsidian indexes tags
natively
- Relations: typed verbs + wikilinks (`- follows [[X]]`,
`- part_of [[Project]]`, `- contains [[Session]]`); inline
`[[wikilinks]]` cover ordinary mentions, the Relations section holds
typed edges that add graph value; omit the section when no typed edges
apply
- Wikilinks must point to existing files. Verify before linking; orphan
links create empty files at the vault root
## Guidelines
- Ask one question at a time when gathering context from the user
- Use `write_note` for new notes, `read_note` + `patch_note` for updates
- Use `search_notes` to check if a note exists before creating
- Link related notes using `[[Note Name]]` wikilinks (verify target exists)
- Use Title Case for filenames
- Sanitize filenames from user input
## Anti-Pattern: Orphan Wikilinks
Creating `[[Some Note]]` to a file that does not exist makes Obsidian
generate an empty file at the vault root. Always run `search_notes`
before linking to verify the target exists. If the target is missing,
either create it first or omit the link.
## Anti-Pattern: Template-Driven Updates
Templates apply to new notes only. When updating an existing note, read
it first with `read_note`, then patch with `patch_note`. Re-applying a
template overwrites prior content and loses history.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.