メニュー
This skill should be used when the user asks to "file a note", "organize vault", "PARA structure", "vault rules", "add frontmatter", "tag a note", "archive a note", "naming convention", or when working with Obsidian vault files.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/JSai23/claude-tooling --skill vault-system-kコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.
SKILL.md を表示中
SOC 職業分類に基づく
| name | vault-system-k |
| type | knowledge |
| description | This skill should be used when the user asks to "file a note", "organize vault", "PARA structure", "vault rules", "add frontmatter", "tag a note", "archive a note", "naming convention", or when working with Obsidian vault files. |
Knowledge skill — PARA filing system: folder structure, naming conventions, frontmatter schemas, tag vocabulary, filing rules.
Core rules for managing a PARA-based Obsidian vault. This skill provides the complete filing system, naming conventions, and structural rules.
0-Inbox/ Raw captures, zero friction
archive/ Processed originals
1-Projects/ Active work with goal + deadline
{project-name}/ Flat inside (one sub-folder level allowed)
2-Areas/ Ongoing interests, no end date
{area-name}/ Flat inside, no sub-folders ever
3-Resources/ Reference material
clips/ Raw captures (Readwise, manual)
short-form/ Tweets, posts, quick takes
long-form/ Articles, essays
books/ Book notes
videos/ Video notes, transcripts
4-Archive/ Done or dead
_System/ Templates, config, references
Max depth: 4 levels. Vault > PARA category > folder > note. No sub-folders inside Areas. Projects allow one level of sub-folders (research/, backtests/) because projects are temporary.
Ask in order, first match wins:
1-Projects/{project}/2-Areas/{area}/3-Resources/{subfolder}/4-Archive/ or deleteWhen ambiguous, use semantic search to confirm — if top matches cluster in one area, that's strong signal.
Notes: YYYY-MM-DD_descriptive-slug.md — always. Generate slug from content.
MOCs (Maps of Content):
00_area-name.md — L0: Main area MOC (one per area, always exists)01_subtopic.md — L1: Sub-MOC (only when 15+ notes cluster on subtopic)Project briefs: 00_project-name.md — always at project root.
Every note gets frontmatter. Required fields: type, created, tags.
Note maturity lives in frontmatter, not tags:
status: draft — raw, incompletestatus: refining — being actively worked onWriter and thinker encode intent for the librarian:
filing-hint — suggested PARA destinationcontext — freeform: what prompted this, what it relates tosource — who created it (e.g., thinker)These are stripped by the librarian when filing.
Consult references/frontmatter-schemas.md for exact YAML for each type.
Tags express the role a note plays in your thinking. They are cross-cutting, intent-based, and orthogonal to PARA.
| Tag | Role | Meaning |
|---|---|---|
#seed | Raw spark | Early idea, observation, needs development |
#thread | Developing narrative | Part of bigger picture, being actively developed |
#tool | Applicable method | Framework, technique, mental model to apply |
#question | Open gap | Unresolved question, gap in understanding |
#insight | Crystallized understanding | Key takeaway, settled understanding |
No other tags. PARA handles topics. Tags handle knowledge roles.
Tags can combine (1-2 max): [seed, question], [tool, insight].
MOCs are living documents that synthesize understanding, not just list links.
Structure: Thesis paragraph → Sections with annotated links → Open Questions → Cross-links to related areas.
L0 MOC: One per area/project. Links everything. Written prose with [[wikilinks]].
L1 Sub-MOC: Only when 15+ notes cluster on a subtopic. L0 references L1; L1 goes deep.
Use [[wikilinks]]. Link when connection is clear and useful — don't force it.
## Related section at bottom, or inline where relevantEverything enters through 0-Inbox/. Writer and thinker both write here. Only the librarian files to PARA destinations.
filing-hint, context, source, tags)04-archive/inbox/YYYY-MM-DD_slug.md## Related section if strong connections existArchive notes get these fields added:
archived: YYYY-MM-DD
archived-from: 2-Areas/area-name
archive-reason: superseded | completed | stale | abandoned
Never auto-archive MOCs, active area notes, or Resources.
For detailed reference:
references/para-rules.md — Full filing rules, archive workflow, content flow, depth enforcementreferences/frontmatter-schemas.md — Exact YAML for every frontmatter typereferences/filing-logic.md — Area scope table, project scope table, decision trees