pka-skills

PKA Skills — Personal Knowledge Assistance for Claude Code

A set of Claude Code skills that turn any folder — or set of folders — into a Personal Knowledge Assistance system. The system infers the meaning of your existing structure rather than imposing one. It stores everything as plain files you can read without any tooling. It uses SQLite as an optional accelerant when your knowledge base grows large enough to need it.

You can install one skill or all six. They compose but are independently useful.

The Six Skills

Skill	Purpose	Standalone?	Optional Dependency
pka-bootstrap	First-run setup, Repo Map, SQLite, roles, lifecycle	Yes — foundation	—
pka-librarian	Document ingestion, OCR, routing, indexing, lint	Yes	—
pka-interface	Browser dashboard	Best with bootstrap	—
pka-meetings	Meeting capture, reconciliation, routing, indexing	Yes (route-only without thinkkit)	thinkkit (take-notes, resolve-against-transcript)
pka-wiki	Topic wiki synthesis, ingest, query enhancement	Best with bootstrap + librarian	—
pka-tutorial	Conversational onboarding and capability walkthrough	Best with bootstrap	—

Design Principles

• Infer, don't impose. Bootstrap reads your existing folder structure and infers what things mean from names and content samples.
• Markdown is the source of truth. SQLite is a fast index over files you already own.
• The map is alive. The Repo Map in your CLAUDE.md is maintained as your structure evolves.
• Vendor-agnostic output. Every generated file works under Claude Code, Gemini CLI, local LLMs, or any tool that accepts markdown context.
• Skills compose without coupling. pka-meetings orchestrates thinkkit when available but degrades gracefully without it.

Installation

# In Claude Code
/plugin marketplace add https://github.com/rappdw/pka-skills
/plugin install pka-skills

If the repo isn't published yet, install from a local path:

claude --plugin-dir /path/to/pka-skills

Optional: Install thinkkit for meeting capture

/plugin marketplace add https://github.com/rappdw/thinkkit
/plugin install thinkkit

Quick Start

cd ~/your-knowledge-folder
claude

Then say: "Set up my PKA" or "Bootstrap my personal knowledge system."

Bootstrap will:

1. Scan your existing structure
2. Infer a Repo Map
3. Ask three questions (name, autonomy level, confirm the map)
4. Write CLAUDE.md, .pka/ infrastructure, and inboxes
5. Initialize SQLite if your knowledge base is large enough

Build Order

If building from scratch, skills should be implemented in this order:

1. pka-bootstrap — topology, Repo Map, SQLite schema, role definitions
2. pka-librarian — content indexing, OCR, transcript awareness
3. pka-interface — visualization, meeting timeline views
4. pka-meetings — meeting pipeline (depends on Repo Map, SQLite, thinkkit)

Documentation

• Tutorial — A practical walkthrough of the system after setup
• Individual skill documentation in skills/<name>/SKILL.md

Repository Structure

pka-skills/
├── .claude-plugin/
│   ├── plugin.json
│   └── marketplace.json
├── skills/
│   ├── pka-bootstrap/
│   │   ├── SKILL.md
│   │   └── references/
│   ├── pka-librarian/
│   │   ├── SKILL.md
│   │   └── references/
│   ├── pka-interface/
│   │   ├── SKILL.md
│   │   └── references/
│   ├── pka-meetings/
│   │   ├── SKILL.md
│   │   └── references/
│   ├── pka-wiki/
│   │   ├── SKILL.md
│   │   └── references/
│   └── pka-tutorial/
│       ├── SKILL.md
│       └── references/
├── evals/
│   ├── pka-bootstrap.evals.json
│   ├── pka-librarian.evals.json
│   ├── pka-interface.evals.json
│   ├── pka-meetings.evals.json
│   ├── pka-wiki.evals.json
│   └── pka-tutorial.evals.json
├── docs/
│   └── TUTORIAL.md
├── README.md
├── CHANGELOG.md
└── LICENSE

Two Content Layers

PKA distinguishes two kinds of content:

• Authored moments — your meeting notes, 1-1s, drafts, journal. Your voice, immutable records of specific moments.
• Synthesis pages — topic wikis (via pka-wiki) that cite authored moments and evolve over time. Optional layer inspired by Karpathy's LLM wiki pattern, adapted to PKA's files-are-source-of-truth model.

Wikis cite moments. Moments never cite wikis. The synthesis layer is additive — delete any wiki without losing underlying content.

Personal Context as a Portable Asset

PKA treats your knowledge base as an agent-maintained personal context portfolio. The owner profile, decision log, session history, and Repo Map together form a structured representation of who you are, how you work, and what you know — maintained by the AI agents as they work with you, not by you filling out forms.