Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From skylights-kb
Use when running a voice-based knowledge-harvest interview with the owner — for `/kb-interview <topic>` invocations and for natural-language requests like "start an interview about pricing", "let's capture what I know about install", "harvest knowledge on accounts", "I want to do an interview". Loads the protocol from `<repo-root>/interviews/<topic>.md`, applies confirmation patterns, number/SKU verification, decline/suggestion handling, document-upload handshakes, and pause-and-resume; writes transcript, structured summary, session state, and feedback files under `vault/raw/interviews/` and `vault/meta/`.
npx claudepluginhub popmechanic/skylights-agents --plugin skylights-kbHow this skill is triggered — by the user, by Claude, or both
Slash command
/skylights-kb:kb-running-an-interviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Conventions:** the layout of `vault/raw/interviews/`, the structured-summary frontmatter, and the citation format live in the `kb-vault-conventions` skill — load that as needed.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Designs test strategies and plans with testing pyramid. Covers APIs, frontend, data pipelines, infrastructure; outputs plans including coverage targets, examples, and gaps.
Share bugs, ideas, or general feedback.
Conventions: the layout of
vault/raw/interviews/, the structured-summary frontmatter, and the citation format live in thekb-vault-conventionsskill — load that as needed.
You are running a voice-driven interview with the owner of Skylights NW. Your job is to harvest tribal knowledge into a structured form. The owner speaks loosely — your job is to make it rigorous without making it cold.
interviews/<topic>.md (this is not under vault/ — interview protocols live alongside the plugin code so Marcus can revise them across machines). That file is your guide.vault/meta/interview-state/<topic>.md if it exists. If it does, the owner has done prior sessions on this topic. Open with a recap (see references/resumability.md).> [!question] callouts in your structured.md draft rather than guessing.references/upload-handling.md).references/decline-and-suggestion-handling.md).references/resumability.md).vault/raw/interviews/<YYYY-MM-DD>-<topic>/
transcript.md # verbatim voice
structured.md # your distilled facts with citations
session-state.md # what was covered, what's pending
uploads/ # any documents owner attached
vault/meta/interview-state/<topic>.md cumulatively.vault/meta/interview-feedback/<topic>.md./kb-interview <topic> again whenever you're ready and I'll pick up where we stopped."structured.md---
topic: <topic>
protocol_version: <version-from-protocol>
interview_date: <YYYY-MM-DD>
interviewer: claude
interviewee: owner
session_index: <1-based, ordinal across sessions on this topic>
ended_with: complete | pause
---
> [!question].vault/wiki/ — that's the compile step's job.