ABOUTME: Vault-to-skills sync, promotes recurring patterns from Second Brain to skill files

ABOUTME: Scan/filter/group/propose/approve/apply cycle with signal strength tracking

Knowledge Sync

Promotes recurring patterns from vault Second Brain notes into skill files. Runs on human schedule (monthly, post-milestone), never autonomously.

Signal Strength

Annotation Schema

Second Brain notes use a ## Skill Candidates table:

## Skill Candidates
<!-- Updated by learning-docs during retrospectives -->

| Pattern | Target Skill | Seen In | First Seen | Signal |
|---------|-------------|---------|------------|--------|
| Go error wrapping with %w | golang | feed-brain, bbp | 2026-01-15 | weak |
| Token bucket rate limiting | cloud-infrastructure | feed-brain, nur, clawdbot | 2026-01-10 | strong |

Table-based: easy to append via CLI, readable in Obsidian, parseable by Claude.

Process

1. •SCAN: obsidian search query="## Skill Candidates" path="Second Brain" matches
2. •FILTER: only strong signals; skip rows where signal = applied or pattern already exists in target skill
3. •GROUP: candidates by target skill with vault source citations
4. •PROPOSE: draft exact text to add to each skill file (show diff-style)
5. •APPROVE: human gate (always RED in decision framework)
6. •APPLY: edit skill file + add backlink + update signal

Apply Step Details

After human approval for each candidate:

1. •Edit target skill file with the proposed addition
2. •Add source backlink as HTML comment: <!-- vault: [[Second Brain - Development#Pattern Name]] -->
3. •Update the Skill Candidates table: change signal from strong to applied

# Example: update signal in vault
obsidian read file="Second Brain - Development"
# Find the row, replace "strong" with "applied" in the table
obsidian append file="Second Brain - Development" content="..."

Presentation Format

## Knowledge Sync Report

### Candidates Found: N strong, M weak (skipped)

#### golang (2 candidates)

**1. Go error wrapping with %w**
- Source: [[Second Brain - Development#Go Error Handling]]
- Seen in: feed-brain, bbp
- Proposed addition to `skills/golang/SKILL.md`:

[exact text to add]

- [ ] Approve  [ ] Skip  [ ] Modify

#### cloud-infrastructure (1 candidate)
...

Quality Notes

• •Take your time scanning every Skill Candidates table thoroughly
• •Read the target skill file before proposing additions (avoid duplicates)
• •Quality of proposals matters more than quantity
• •Do not skip validation steps

Rules

• •Never auto-apply. Always present proposals and wait for approval.
• •One skill at a time. Don't batch across skills without per-skill approval.
• •Preserve existing content. Additions only, never modify existing skill text.
• •Backlinks are mandatory. Every applied pattern traces back to its vault source.
• •Cadence: monthly or after major project milestones. Not after every session.