refactor(pkm-curation): move skill from common/personal to common/pkm directory

2026-06-25 12:04:08 -04:00
parent 68f9b4691e
commit 371697375a
3 changed files with 0 additions and 0 deletions
@@ -0,0 +1,51 @@
+---
+id: pkm-curation-agent-integration
+aliases:
+  - PKM Curation agent Integration
+tags:
+  - knowledge-management
+  - reference
+area: Personal Knowledge Management
+project:
+---
+
+# Agent Integration
+
+## Purpose
+
+This skill should be usable from any agent, and it should also fit chat environments where the agent as tool access.
+
+## Recommended Role
+
+- batch curation, targeted note cleanup, folder reviews, and repeatable vault maintenance
+- interactive note refinement, serendipity review, and exploratory linking sessions
+- editor-side entry point that delegates vault actions to agent where possible
+
+## Preferred Behaviors
+
+- search the vault before proposing links
+- inspect nearby notes before creating new ones
+- patch files directly when the requested change is clear
+- summarize edits in plain Markdown
+- ask before removing any content or links from a note
+- ask before moving, renaming, or creating many files
+
+## Good Task Shapes
+
+- curate a specific note
+- process a small `Inbox/` batch
+- review recent notes for missing links
+- extract atomic notes from one source note
+- run a serendipity review against a current topic
+
+## Avoid
+
+- large autonomous folder reorganizations
+- broad speculative linking passes
+- converting every long note into atomic notes
+- changing note titles without stating why
+
+## Portability Guidance
+
+- keep the workflow in `SKILL.md` tool-agnostic where possible
+- prefer small deterministic file edits so the skill remains portable to other `SKILL.md`-based agents
@@ -0,0 +1,61 @@
+---
+id: pkm-curation-vault-conventions
+aliases:
+  - PKM Curation Vault Conventions
+tags:
+  - knowledge-management
+  - obsidian
+  - reference
+  - ai
+area: Personal Knowledge Management
+project:
+---
+
+# Vault Conventions
+
+## Required Frontmatter
+
+All notes should include YAML frontmatter with:
+
+```yaml
+---
+id: unique-id
+aliases: []
+tags: []
+area: Primary area/domain
+project: [[Project Note]]
+---
+```
+
+Use an empty value for `project:` when there is no relevant project note.
+
+## Core Principles
+
+- Markdown-first
+- explicit `[[wikilinks]]`
+- atomic notes for durable ideas
+- project, topic, and date-based organization
+- consistency over novelty
+
+## Folder Roles
+
+- `Inbox/`: raw capture and unprocessed notes
+- `Dailies/`: day-specific notes and reflection
+- `Templates/`: note templates
+- `Knowledge/`: preferred home for evergreen atomic notes if the folder exists or is created
+- project/topic folders: active work and structured reference material
+
+## Task Conventions
+
+- Use Markdown task items: `- [ ] Task description [[Project Name]]`
+- Add status and priority tags where useful
+- Use `due:: YYYY-MM-DD` for due dates
+- Add `start::` and `end::` only when explicitly requested or when tracking active work
+
+## Curation Heuristics
+
+- A saved thing is not yet a knowledge note.
+- A source note is not the same as an evergreen note.
+- A link should reflect a real conceptual or project relationship.
+- A long note may remain long if it is reference material; only extract notes when reuse is likely.
+- Prefer gradual improvement over mass refactoring.