kb

Explains knowledge base layout, queue semantics, expiry, links, and maintenance for git-backed markdown bases.

3|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/AlmogBaku/aos --skill kb-almogbaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kb
Source: https://github.com/AlmogBaku/aos/tree/main/capabilities/kb/skills/kb
Command: npx skills add https://github.com/AlmogBaku/aos --skill kb-almogbaku

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agents working with a personal knowledge base need to understand how bases are structured, which queue to read, when pages expire, and which narrower kb skill handles a given job — without this map they misfile captures, drain the wrong queue, or run destructive commands against the wrong base. ## Core Features & Use Cases - Base layout orientation: Documents the anatomy of a base (.kb/, _raw/, wiki zones, index.md) and the three tests for pending/, work/, and cache/. - Queue and query guidance: Distinguishes kb inbox (agent-scoped ingest work) from kb pending list --where waits_on=human, and covers kb find/kb search with quoted date comparisons. - Safe lifecycle operations: Prescribes dry-run-first kb prune and reason-required kb archive, always with an explicit --base, plus wikilink conventions and an authority model for reads, report-only findings, and destructive actions. - Use Case: A user asks "why wasn't my note kept?" or "run base maintenance" — the agent uses this skill to inspect pending entries, dry-run a prune on the named base, and route the actual filing to kb-capture or kb-recall as appropriate. ## Quick Start Ask the agent to explain how your knowledge base is organized and to dry-run a prune on a named base to show which pages would expire.

Frequently Asked Questions about kb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check what is waiting in my knowledge base queue?▼

Use `kb inbox` to see ingest work waiting on the agent, scoped to your principal. For items waiting on a human, run `kb pending list --where waits_on=human`, since inbox filters those out entirely.

How do I safely delete expired pages from a knowledge base?▼

Run `kb --base <name> prune --dry-run` first to review the deletion list, then repeat without `--dry-run`. Always name `--base` explicitly, because a bare prune resolves a base from the current directory or registry default and may delete from the wrong one.

What is the difference between kb prune and kb archive?▼

Prune deletes pages whose `expires:` date has passed and is deterministic. Archive is a judgment that a page stopped mattering, requiring `kb archive <page> --reason "<why>"`, and it should be proposed to the user rather than run on the agent's own initiative.

Why does kb inbox show an empty list when items are pending?▼

Inbox only returns items with `waits_on: agent` scoped to the acting principal, and it exits 0 with an empty list otherwise. Items waiting on a human require `kb pending list --where waits_on=human` instead.

When should I use wikilinks instead of file paths in a knowledge base?▼

Use `[[wikilink]]` for any link inside a base, because pages move during promotion and reorganization and path-based links break. Ordinary markdown links are for targets outside the base, which the link graph ignores.

Can an agent write to any zone in a shared knowledge base?▼

No. Writes are governed by the grants table in each base's AGENTS.md, checked with `kb grants check` before non-obvious writes. On shared bases, agent writes land as proposals in the queue, and the tool itself does not enforce grants — discipline and the weekly audit do.