# Knowledge Sync

> Sync vault knowledge patterns to skills. Scans Second Brain for strong signals, proposes skill updates. Use when user says knowledge sync, sync skills, update skills from vault, or promote patterns.

- **Type:** Skill
- **Install:** `agentstack add skill-maroffo-claude-forge-knowledge-sync`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [maroffo](https://agentstack.voostack.com/s/maroffo)
- **Installs:** 0
- **Category:** [Security](https://agentstack.voostack.com/c/security)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [maroffo](https://github.com/maroffo)
- **Source:** https://github.com/maroffo/claude-forge/tree/main/skills/knowledge-sync

## Install

```sh
agentstack add skill-maroffo-claude-forge-knowledge-sync
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 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

| Signal | Criteria | Action |
|--------|----------|--------|
| weak | 1 project or 1 source | Track, don't propose |
| strong | 3+ projects OR 2+ independent sources | Propose to human |
| applied | Already synced to skill | Skip |

## Annotation Schema

Second Brain notes use a `## Skill Candidates` table:

```markdown
## Skill Candidates

| 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: ``
3. Update the Skill Candidates table: change signal from `strong` to `applied`

```bash
# 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

```markdown
## 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.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [maroffo](https://github.com/maroffo)
- **Source:** [maroffo/claude-forge](https://github.com/maroffo/claude-forge)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-maroffo-claude-forge-knowledge-sync
- Seller: https://agentstack.voostack.com/s/maroffo
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.