By rappdw
Personal Knowledge Assistance — four skills that turn any folder into a local, AI-powered knowledge system replacing Obsidian/Notion/Tana
ALWAYS use this skill when the user mentions PKA, personal knowledge, repo map, knowledge base setup, replacing Obsidian/Notion/Tana/Heptabase, organizing notes and files into a unified system, adding roles to their AI team, project lifecycle management, transitioning or archiving projects, restoring archived projects, checking which projects are stale or winding down, bootstrapping any kind of personal knowledge assistant, OR setting up Obsidian coexistence / a hybrid monorepo (root .git + child repos at knowledge/ and projects/* coordinated via .meta). Triggers also include: "bootstrap obsidian", "bootstrap vault", "MOC stubs", "frontmatter retrofit", "bootstrap git", "initialize the hybrid repo", "set up the meta monorepo", "bootstrap all", "bootstrap everything". This skill handles first-run setup (scanning folders, inferring structure, writing CLAUDE.md, creating SQLite indexes, defining roles) AND ongoing management (updating the repo map, adding team roles, transitioning completed projects to a knowledge archive, checking project activity) AND the additive Obsidian / hybrid-monorepo bootstraps (idempotent, user-triggered, never auto-run). Use it even if the user doesn't say "PKA" explicitly — if they want to unify scattered notes, set up AI-powered file organization, or manage workspace lifecycle, this is the right skill.
ALWAYS use this skill when the user wants a dashboard, browser interface, or visual view of their knowledge base, notes, projects, or PKA system. Triggers on: building a dashboard, updating an existing dashboard, adding sections or views to a dashboard, visualizing data in a browser, creating a PKA interface, refreshing a stale dashboard, fixing dashboard search, changing dashboard theme or dark mode, adding kanban/timeline/card views, or any request to see knowledge or project data visually in HTML. Generates a single-file HTML dashboard (no server, no build step, double-click to open) with sections auto-generated from the Repo Map. Use this skill even if the user just says "build my dashboard", "update the dashboard", "show me my data in a browser", "add a view for X", or "the dashboard needs refreshing". Supports SQLite and markdown-only modes.
ALWAYS use this skill when the user wants to process, route, OCR, index, or organize documents in their knowledge system. Triggers on: processing an inbox or team-inbox, routing dropped files to the right folders, OCR on PDFs or scanned documents, re-indexing a knowledge base, setting up a scanner (ScanSnap, iPhone), organizing files into a folder structure, inventorying what's in an inbox, extracting text from PDFs, or any document ingestion task within a PKA or personal knowledge system. Use this skill even when the user just says "process my inbox", "what's in the inbox", "route these docs", "re-index", "OCR these", "set up my scanner", or drops files and asks what to do with them. Handles transcript detection (holds .vtt/.srt files for meeting processing instead of routing them). Also runs lint / health checks on the knowledge base (orphan files, broken links, stale wiki sources, contradiction candidates) — triggered by "run a health check", "lint my knowledge base", "what needs attention", or "check for broken links". Works standalone or with pka-bootstrap.
ALWAYS use this skill when the user mentions meetings, meeting notes, taking notes, transcripts, action items from meetings, or filing/routing meeting documentation. Triggers on: starting a meeting, taking notes during a meeting, 1-1s with anyone, reconciling notes against a transcript, filing or routing meeting notes to the right folder, processing a Zoom/Teams transcript, extracting action items from meetings, asking what action items they have, capturing meeting decisions, or any meeting-related documentation task. Use this even when the user just says "I'm in a meeting", "take notes", "file these notes", "I have a transcript", "what are my action items this week", or mentions a specific meeting like "1-1 with Aarav" or "SLT planning". Orchestrates thinkkit take-notes and resolve-against-transcript when available. Handles smart routing, attendee linking, and action item extraction. Works standalone for routing if thinkkit is not installed.
ALWAYS use this skill when the user is new to PKA, asks for a tour, walkthrough, tutorial, onboarding, or says they don't know how to use their PKA system. Triggers on: "I just installed PKA", "how do I use this", "what can I do with this", "walk me through PKA", "teach me how this works", "give me a tour", "I'm new here", "what are my options", "how do I find things", "show me the ropes", "help me get started", or any confusion about where to begin. Also use when a user asks how to do a specific PKA task for the first time (how to capture meetings, drop files, use the dashboard, transition a project) — the skill teaches the workflow with concrete examples rather than just executing. Adapts to the user's current PKA state: offers a full tour if bootstrapped, points to pka-bootstrap if not.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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.
| 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 | — |
CLAUDE.md is maintained as your structure evolves.pka-meetings orchestrates thinkkit when available but degrades gracefully without it.# 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
/plugin marketplace add https://github.com/rappdw/thinkkit
/plugin install thinkkit
cd ~/your-knowledge-folder
claude
Then say: "Set up my PKA" or "Bootstrap my personal knowledge system."
Bootstrap will:
CLAUDE.md, .pka/ infrastructure, and inboxesIf building from scratch, skills should be implemented in this order:
Two additive capabilities sit on top of the base PKA setup. Both are user-triggered (never auto-detected) and idempotent:
knowledge/.obsidian/ exists, roles enhance files they touch with frontmatter, MOC entries, and [[wikilinks]]. Run bootstrap obsidian for a one-time mechanical retrofit (MOC stubs, person indexes, filename-pattern frontmatter — never reads file bodies, never overwrites).bootstrap git sets up a root .git coordinating independent child repos at knowledge/ and each projects/<name>/ via a .meta manifest, with LFS-configured templates. Roles then auto-commit per semantic unit in child repos (with Co-Authored-By: Claude trailer) while the root repo remains a human-review gate. Sessions end with a consolidated push.A user with no Obsidian vault and no hybrid monorepo sees identical behavior to before. See docs/specification-addendum.md (spec) and the seed references in skills/pka-bootstrap/references/ (obsidian-conventions.md, git-protocol.md, obsidian-bootstrap.md, git-bootstrap.md).
v1.6.1 — Pointer layer for MOC files. The librarian maintains a ## Pointers section inside each _MOC.md (one row per concept cluster, three columns: Topic, Entities, Files). FTS5 indexes pointer-row content with a 3× rank boost over body matches, turning a 1,500-file haystack query into a 30-cluster summary followed by 3–5 targeted file reads. No vector store, no embeddings. See skills/pka-librarian/references/pointer-layer.md.
npx claudepluginhub rappdw/pka-skills --plugin pka-skillsSynthetic data toolkit — schema-driven generation, Excel extraction, dataset extension, anonymization, and MCP serving. Domain-agnostic engine with 10+ starter templates covering HR, e-commerce, SaaS metrics, healthcare, finance, security, logs, IoT, CRM, and surveys. Uses YAML schemas with Faker, distributions (normal/lognormal/zipf/poisson), FK integrity, behavioral profiles, temporal event generation, and multi-format writers (xlsx/csv/json/sql/parquet).
Your AI team and personal knowledge base — Chief of Staff, hiring pipeline, and SQLite-backed search for any project
Thinking tools for AI — structured exploration, strategic debate, council deliberation, CISO review, discovery scaffolding, codebase mapping, specification generation, and meeting notes
Kit completo de skills pra transformar uma pasta em vault Obsidian profissional + dashboard local com ML. 6 skills: init (scaffold), librarian (cura contínua), migrate (adoção não-destrutiva), organizer (clusters/duplicatas), expand (notas-ponte via LLM restrito), pulse (dashboard localhost com FSRS, recommendations, anomalies). 100% local, privacy-first, pt-br.
Claude + Obsidian knowledge companion. Sets up a persistent, compounding wiki vault (Karpathy's LLM Wiki pattern). v1.7 "Compound Vault" + v1.8 methodology modes close 5 of 5 priority gaps from the May 2026 compass artifact. Ships: substrate alignment with kepano/obsidian-skills, default Obsidian CLI transport, hybrid retrieval (contextual prefix + BM25 + cosine rerank per Anthropic's Sept 2024 research), per-file advisory locking for multi-writer safety, pre-commit verifier agent, AND methodology modes (LYT / PARA / Zettelkasten / Generic) for first-class organizational support no other Claude+Obsidian competitor offers. v1.7.x audit closure: every BLOCKER + HIGH + MEDIUM + LOW finding from the v1.7.0 audit is CLOSED or DEFERRED-with-rationale. Optional DragonScale Memory extension (log folds, deterministic addresses, semantic tiling lint, boundary-first autoresearch).
Knowledge management for Obsidian vaults and structured markdown repositories
LLM-maintained knowledge base skill — structured wiki with Obsidian, milestone-based source clustering, proactive write-back, and autonomous lint
Generate research-backed knowledge systems from natural conversation. 15 kernel primitives, 26 commands, 249 research claims, 3 presets.
Personal AI Infrastructure — persistent memory, session continuity, and knowledge graph for Claude Code