Skip to content
Skills Library
Personal productivity · Writing

create-note

/create-note

Create an Obsidian Inbox capture, a human-owned Atomic Note draft, or approved reusable knowledge from a conversation. Use for "capture this", "create a note", "write this in my own words", "save this explanation", or promoting material from existing notes. Use ingest for external sources and save-session for a session recap.

Repository
Skills ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create an Obsidian Inbox capture, a human-owned Atomic Note draft, or approved reusable knowledge from a conversation. Use for "capture this", "create a note", "write this in my own words", "save this explanation", or promoting material from existing notes. Use ingest for external sources and save-session for a session recap.

Triggers from the description

capture thiscreate a notewrite this in my own wordssave this explanation
Original author description

Create an Obsidian Inbox capture, a human-owned Atomic Note draft, or approved reusable knowledge from a conversation. Use for "capture this", "create a note", "write this in my own words", "save this explanation", or promoting material from existing notes. Use ingest for external sources and save-session for a session recap.

How it works

  1. 1. Choose the note and owner
  2. 2. Check for an existing note
  3. 3. Draft the right amount
  4. 4. Preview, write, and verify
  5. References
Original SKILL.md headings · 66 lines, 512 words
SKILL.md preview
---
name: create-note
description: >-
  Create an Obsidian Inbox capture, a human-owned Atomic Note draft, or approved reusable knowledge
  from a conversation. Use for "capture this", "create a note", "write this in my own words",
  "save this explanation", or promoting material from existing notes. Use ingest for external sources
  and save-session for a session recap.
user-invocable: true
---

# Create Note

Choose the purpose before the template. An Atomic Note can explain a technique, preserve a principle,
or explore a question; it is not limited to ideas.

## 1. Choose the note and owner

Read `../vault/SKILL.md` and the live `AGENTS.md`. Resolve the destination and active template:

| Intent | Note |
| --- | --- |
| Save an observation, question, thought, or snippet before losing it | Inbox capture using General Notes |
| Leave space for the user to develop their own explanation | Human-owned draft using Atomic Note |
| Preserve a reusable explanation developed in the conversation | Approved agent-written Knowledge note using Atomic Note |
| Explain connections across several notes | MOC using its live template and existing Bases |

Use the request to choose the mode; ask when authorship or destination is unclear. A quick capture
needs no classification interview. An unfinished question can already deserve an Atomic Note.

When promoting material from daily notes or other existing notes, read `references/promote-mode.md`.

Completion: purpose, owner, destination, and active template are known.

## 2. Check for an existing note

For Knowledge or MOCs, read root `index.md`, search when needed, and inspect plausible matches.
Choose to create, link, or enrich based on scope and ownership. An existing human-owned page is not
an automatic enrichment target. For Inbox captures, check for a filename collision without turning
capture into a vault-wide research task.

Completion: the proposed write does not overwrite an existing note or duplicate known coverage.

## 3. Draft the right amount

- **Capture:** keep the supplied material short and preserve its meaning and source context.
- **Human draft:** use the live template, resolve title/date fields, and add only approved tags and
  relevant source links. Leave the user's explanation and questions for them to write. User-supplied
  prose may be included exactly as approved. Omit agent ownership metadata.
- **Agent synthesis:** write a standalone explanation supported by the conversation and sources.
  Distinguish facts from open questions; use the schema's wiki metadata. Do not invent the user's
  beliefs, experiences, or learning.
- **MOC:** explain the connections, preserve existing Base embeds, and select an existing Base when
  useful. A new or changed Base needs separate approval.

Completion: the draft fits its purpose and represents its owner honestly.

## 4. Preview, write, and verify

Show the exact path and content or section edit, plus any required index/log changes. After approval,
use the vault safe-write flow and account for automatic template insertion. Reread the result and
verify one frontmatter block, resolved fields, and working links.

Register Knowledge writes as the live schema requires. Human drafts belong under the human-note
catalog section, not agent-written concepts. Ordinary Inbox captures need no wiki registration.
Preserve source daily notes and unrelated content.

Completion: every approved change is verified, required registration is complete, and the report
states the path, owner, create/enrich mode, and any incomplete step.

## References

| Priority | Load when | Reference |
| --- | --- | --- |
| 1 | Promoting observations, questions, or explanations from existing notes | `references/promote-mode.md` |
Files in this package (2)
  • SKILL.md 4 KB
  • references/promote-mode.md 2 KB

Versions

RepositoryScoreLicence
This page · kriscard/Skills90MIT
atomicinnovation/accelerator100MIT
builtby-win/skills100MIT

Database snapshot: 13.11.2026 · package version 255f512800f9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ingest
    Discuss and file an article, URL, video, book note, or selected Inbox source, then reuse a matching Atomic Note or create a human-owned scaffold for the user to write. Use when the user asks to ingest or add source material to the Obsidian knowledge base.
  • 100obsidian-knowledge
    Use for any knowledge work in an Obsidian vault — capturing a quick note or link, organizing an Inbox, or turning bigger material (PDFs, docx, slides, syllabi, papers, transcripts, URL lists) into structured, teaching-quality notes. Works for any subject, adapts to the vault…
  • 100make-note
    Create well-structured notes in Obsidian with intelligent tag suggestions. Use this skill whenever the user asks to create a note, make a note, save something to Obsidian, capture a thought, or write something to their vault. Also trigger when the user says "note this", "add to…
  • 90to-note
    Save content as a Markdown note in the user's Obsidian vault. Use for /to-note, or when asked to save, record, or send something to Obsidian or the notes vault.
  • 100obsidian-capture
    Save a note, decision, or thought to the Obsidian vault right now. Use when someone says "capture this", "save this to Obsidian", "note this down", "log this decision", "obsidian note", "save this for later", "capture that idea". Requires OBSIDIAN_VAULT_PATH to be set.
  • 100secondbrain-note
    This skill should be used when the user asks to "create note", "capture thought", "save this", "document idea", "write note", "jot down", "quick note", "remember this", "capture this", or mentions wanting to save knowledge, ideas, or learnings for later reference in their secondbrain.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.