Skip to content
Skills Library
Personal productivity · Writing

capture

/capture

Save durable knowledge to the vault. Use when the session produced facts worth keeping — research findings, decisions, how-something-works — or when the user says "remember this" / "capture this".

Licence
MIT
Last repository change
30.09.2026

Assessment and security

100/ 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.
Content35 / 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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.09.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

Save durable knowledge to the vault. Use when the session produced facts worth keeping — research findings, decisions, how-something-works — or when the user says "remember this" / "capture this".

Triggers from the description

remember thiscapture this
Original author description

Save durable knowledge to the vault. Use when the session produced facts worth keeping — research findings, decisions, how-something-works — or when the user says "remember this" / "capture this".

How it works

  1. What qualifies
  2. Steps
  3. Rules
Original SKILL.md headings · 50 lines, 297 words
SKILL.md preview
---
name: capture
description: Save durable knowledge to the vault. Use when the session produced facts worth keeping — research findings, decisions, how-something-works — or when the user says "remember this" / "capture this".
---

# Capture

One job: move facts from this session's context into external memory
(`vault/Knowledge/`) so future sessions can find them.

> All `vault/…` paths below resolve against the vault base (see CLAUDE.md →
> "Resolving the vault path"); on a clone that's the repo's `vault/`, on a plugin
> install it's the setup-recorded path. Resolve the base before writing.

## What qualifies

- Durable facts: how a system works, a decision and its why, research findings
- NOT session narrative (that goes in the daily note via reflect)
- NOT feelings about the work (that goes in Reflections via reflect)

## Steps

1. Identify the fact(s) worth keeping. Ask: "would a future session with no
   memory of today need this?" If no — don't capture it.
2. Check `vault/MEMORY.md`'s Knowledge index for an existing note on the
   topic. **Update the existing note** rather than creating a near-duplicate.
3. If new: create `vault/Knowledge/<topic-slug>.md`:

   ```markdown
   # <Topic>

   <the facts, stated plainly — not "today we found", just "X is Y">

   Related: [[other-note]] (only if genuinely related)
   ```

   One topic per note. If you're writing about two topics, make two notes.
4. Queue the one-line index entry for `MEMORY.md`'s `## Knowledge index` —
   do NOT edit MEMORY.md now (it's read-only mid-session for prompt-cache
   stability, see CLAUDE.md hard rules). Reflect adds it at session close:

   ```markdown
   - [<Topic>](Knowledge/<topic-slug>.md) — <what question this note answers>
   ```

## Rules

- Facts in the note, one-liner in the index. Never paste note content into
  MEMORY.md — the index must stay small.
- State facts timelessly ("the API limit is 100/min"), so notes don't rot
  into stale narrative. When a fact changes, edit the note. Git keeps history.
- Max 5 captures per session. More than that means you're logging, not
  capturing — be selective.

Versions

RepositoryScoreLicence
This page · slogsdon/loop-and-gate-foundation100MIT
wenlan-app/wenlan100Apache-2.0
wenlan-app/wenlan100Apache-2.0
optimiziramsi/skills100MIT
Kolibee-GmbH/m2b100MIT
davepoon/buildwithclaude100MIT
aw3-technology/vibehub-plugins100MIT
anurag-rivora/product-brain-starter100MIT
borghei/Claude-Skills100MIT

Database snapshot: 13.11.2026 · package version fb8993f2b63b (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

  • 86vault-capture
    Use when durable knowledge comes up (a decision, finding, gotcha or research result), or the user asks to save, note or file something or a source in the knowledge vault. Skip transient task state and anything a repository's own docs should hold.
  • 90bm-remember
    Quickly capture a thought, fact, or reminder into Basic Memory as a lightweight note. Use when the user says "remember that…", "note this", "save this to memory", or runs /basic-memory:bm-remember. For quick deliberate capture — not full decision or session records.
  • 90history-notes
    Use when the user says remember this or settles one durable fact. Not for remote, credential, publish, deploy, or irreversible changes.
  • 100project-notes-notion
    Capture durable project facts and decisions in Notion, including domain purchases, cloud trials, renewals, deployments, recovery steps, and handoffs. Use when the user asks to save project knowledge, or at meaningful project milestones when ongoing capture is already authorized.…
  • 100remember
    Capture knowledge to your Second Brain when triggered by "remember this", "save this", or "brain dump
  • 100vault-knowledge
    This skill should be used when working on any project to understand how to effectively interact with the Obsidian knowledge vault. It teaches when to capture knowledge, what to capture, how to format vault notes, and how to search effectively. Use when you need to "save to…

Feedback and reports

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