How do I install the Manage A Knowledge Base skill?

Run npx skillmds@latest add ariaxhan/manage-a-knowledge-base in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Manage A Knowledge Base safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Manage A Knowledge Base?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Manage A Knowledge Base free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Manage A Knowledge Base?

ariaxhan (@ariaxhan) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Manage A Knowledge Base by ariaxhan

Name: Manage A Knowledge Base
Author: ariaxhan

Manage A Knowledge Base

Run a personal knowledge base or second brain as a system, not a junk drawer. Use for any stage of a notes collection: "process my inbox / triage my captures", "find contradictions across my notes", "synthesize / weave these notes together", "prune / clean up my ideas list", "archive stale notes / decay scan", "check my notes for broken links or missing metadata", "manage my vault / zettelkasten / second brain". Produces filed notes, collision logs, synthesis notes, a pruned idea list, archive decisions, and an integrity report, depending on the phase invoked.

ariaxhan 6213c92 8 files · 11.4 KB Updated Sep 17, 2026

File contents

Manage a Knowledge Base

A notes collection has a lifecycle. Captures come in raw, get sorted, get connected, get synthesized, and eventually decay, and the whole thing drifts into broken links and duplicates unless something maintains it. This kit is the six maintenance moves, each a self-contained workflow in reference/.

Pick the phase that matches what the collection needs right now. You don't run all six every time.

The lifecycle

CAPTURE → TRIAGE → CONNECT → SYNTHESIZE → CURATE → DECAY
                                                    ↑
                              INTEGRITY (periodic cross-check)

Triage: turn a pile of raw captures into filed, structured notes. → reference/triage-captures.md
Connect: find where notes contradict, reinforce, or unexpectedly bridge. → reference/find-collisions.md
Synthesize: knit several notes into one integrated piece aimed at a question. → reference/synthesize-notes.md
Curate: prune the idea backlog; graduate the clusters that earned it. → reference/curate-ideas.md
Decay: score notes by use and age; archive the cold, promote the proven. → reference/decay-and-archive.md
Integrity: audit metadata, links, and contradictions across the whole base. → reference/audit-integrity.md

Which phase do I need?

The user says…	Phase	Reference
"process my inbox", "I have a pile of unsorted captures"	Triage	`reference/triage-captures.md`
"what contradicts what", "find connections across my notes"	Connect	`reference/find-collisions.md`
"synthesize these", "knit these threads", "the bigger picture"	Synthesize	`reference/synthesize-notes.md`
"clean up my ideas", "which ideas are worth keeping"	Curate	`reference/curate-ideas.md`
"archive stale notes", "my base is bloated", "decay scan"	Decay	`reference/decay-and-archive.md`
"broken links", "missing metadata", "integrity check"	Integrity	`reference/audit-integrity.md`

Principles that hold across every phase

Batch the judgment moments, never auto-promote. The value of a note system is the human deciding what's worth keeping. Surface decisions in small batches; don't let the assistant silently file or delete.
Recurrence beats excitement. A pattern, idea, or cluster graduates only when it shows up across multiple independent sessions. One enthusiastic capture is not a trend.
Confidence threshold over volume. One strong, real finding beats ten maybes. False positives erode trust in the whole system faster than missed ones.
Protect the evergreen. Anything marked durable is never auto-archived, however old or untouched.

Output

Each phase produces its own artifact: filed notes, a dated collision log, a synthesis note, a pruned idea file, archive/promotion decisions, or an integrity report with a pass rate. Open the matching reference for the exact steps and output format.

---name: manage-a-knowledge-basedescription: Run a personal knowledge base or second brain as a system, not a junk drawer. Use for any stage of a notes collection: "process my inbox / triage my captures", "find contradictions across my notes", "synthesize / weave these notes together", "prune / clean up my ideas list", "archive stale notes / decay scan", "check my notes for broken links or missing metadata", "manage my vault / zettelkasten / second brain". Produces filed notes, collision logs, synthesis notes, a pruned idea list, archive decisions, and an integrity report, depending on the phase invoked.---# Manage a Knowledge BaseA notes collection has a lifecycle. Captures come in raw, get sorted, get connected, get synthesized, and eventually decay, and the whole thing drifts into broken links and duplicates unless something maintains it. This kit is the six maintenance moves, each a self-contained workflow in `reference/`.Pick the phase that matches what the collection needs right now. You don't run all six every time.## The lifecycle```CAPTURE → TRIAGE → CONNECT → SYNTHESIZE → CURATE → DECAY ↑ INTEGRITY (periodic cross-check)```- **Triage**: turn a pile of raw captures into filed, structured notes. → `reference/triage-captures.md`- **Connect**: find where notes contradict, reinforce, or unexpectedly bridge. → `reference/find-collisions.md`- **Synthesize**: knit several notes into one integrated piece aimed at a question. → `reference/synthesize-notes.md`- **Curate**: prune the idea backlog; graduate the clusters that earned it. → `reference/curate-ideas.md`- **Decay**: score notes by use and age; archive the cold, promote the proven. → `reference/decay-and-archive.md`- **Integrity**: audit metadata, links, and contradictions across the whole base. → `reference/audit-integrity.md`## Which phase do I need?| The user says… | Phase | Reference ||---|---|---|| "process my inbox", "I have a pile of unsorted captures" | Triage | `reference/triage-captures.md` || "what contradicts what", "find connections across my notes" | Connect | `reference/find-collisions.md` || "synthesize these", "knit these threads", "the bigger picture" | Synthesize | `reference/synthesize-notes.md` || "clean up my ideas", "which ideas are worth keeping" | Curate | `reference/curate-ideas.md` || "archive stale notes", "my base is bloated", "decay scan" | Decay | `reference/decay-and-archive.md` || "broken links", "missing metadata", "integrity check" | Integrity | `reference/audit-integrity.md` |## Principles that hold across every phase- **Batch the judgment moments, never auto-promote.** The value of a note system is the human deciding what's worth keeping. Surface decisions in small batches; don't let the assistant silently file or delete.- **Recurrence beats excitement.** A pattern, idea, or cluster graduates only when it shows up across multiple independent sessions. One enthusiastic capture is not a trend.- **Confidence threshold over volume.** One strong, real finding beats ten maybes. False positives erode trust in the whole system faster than missed ones.- **Protect the evergreen.** Anything marked durable is never auto-archived, however old or untouched.## OutputEach phase produces its own artifact: filed notes, a dated collision log, a synthesis note, a pruned idea file, archive/promotion decisions, or an integrity report with a pass rate. Open the matching reference for the exact steps and output format.

Frequently asked questions