Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From skylights-kb
Use whenever working in the Skylights NW knowledge-base vault — defines trunk taxonomy, frontmatter schema, citation patterns, raw/wiki/meta boundaries, and the read-only invariant for agents. Triggers on any task that reads or writes files in vault/, runs /kb-* commands, or asks questions about the KB.
npx claudepluginhub popmechanic/skylights-agents --plugin skylights-kbHow this skill is triggered — by the user, by Claude, or both
Slash command
/skylights-kb:kb-vault-conventionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is the single source of truth for how the Skylights NW knowledge-base vault is organized. Read it before doing any work involving `vault/`, the wiki, raw materials, or KB-related slash commands.
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.
This skill is the single source of truth for how the Skylights NW knowledge-base vault is organized. Read it before doing any work involving vault/, the wiki, raw materials, or KB-related slash commands.
The vault has three directories, each with a strict role:
vault/raw/ — source material. Never deleted. Compile reads from here.vault/wiki/ — compiled, agent-readable knowledge. Only kb-compile writes here. Agents read it.vault/meta/ — LLM-maintained indexes, logs, state, reports.The wiki is partitioned into 10 trunks. Every wiki article belongs to exactly one trunk:
| Trunk | Holds |
|---|---|
products/ | Skylight models, glass options, accessories |
suppliers/ | Velux, Crystallite, Fakro, etc. — terms, lead times, contacts |
accounts/ | Custom vs. stock account playbooks, drop-ship patterns |
sales/ | Sales playbooks (homeowner / contractor), pricing rules of thumb |
install/ | Procedures, PNW-specific gotchas, safety, edge cases |
operations/ | Service area, crews, scheduling norms, warranty policy |
systems/ | Schema docs for Zoho CRM, QuickBooks, Contacts Journal, RingCentral, Velux chat, Zoho Mail |
marketing/ | Velux directory PPC, Google organic, Angie's, vehicle wraps |
glossary/ | Domain terms (deck-mount, curb-mount, flashing kit, etc.) |
business/ | Company-level — business/team/ (one article per person), business/vision/ (north-star) |
No agent ever writes to vault/wiki/. Period. The only writers are:
/kb-compile (via the kb-compiler subagent), which produces wiki articles from raw/If you're an agent and you find a fact in the wiki that's wrong, do NOT edit the article. Write a note to vault/raw/inbox/ describing what's wrong. The owner reviews on next compile.
See references/frontmatter-schema.md for required wiki article fields.
See references/citation-conventions.md for how to cite raw sources.
The wiki uses two callout types that have specific meanings:
> [!question] ... — open question, awaiting an interview to resolve. Lint aggregates these.> [!conflict] ... — two sources disagree. Compile inserts these; never resolve them by deleting the older claim — owner resolves manually.