メニュー
Audit an OKF knowledge base for integrity before it ships. Use to verify a generated/edited KB — checks OKF compliance, atomicity, link integrity, provenance/confidence, coverage gaps, and stale content. Produces a severity-ranked report; does not silently fix.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate a client's L2 "adoption readout" — the Ladder (DEC-0052's wedge). From a provisioned client's served OKF, run the deterministic 4-axis scorer over their process/workflow atoms, then narrate a sequenced Now/Next/Later transformation roadmap and emit it as a sovereign OKF `artifact` in the CLIENT's own repo. Use after a client is ingested + served (KNOWLEDGE-BRIEF generated) to produce the post-diagnostic readout that lands the wedge ("we'll take you to where we already are") and opens the Agency conversation. Human-curated authoring; reads the client's OWN OKF, never perturbs Dossier's KB.
Architect a world-class, ATOMIC information architecture for a Dossier docs site — turn a flat OKF knowledge base into a navigable, scannable, readable reading experience whose structure is DERIVED FROM THE KNOWLEDGE GRAPH, never hand-maintained. Use when a docs surface is hard to navigate (giant flat sidebars, no section overviews, no wayfinding, every page a dead end), when onboarding a new client's KB to the docs, or when asked to improve docs IA / navigation / readability.
Generate a tailored client landing instance — a typed LandingContent module — from a provisioned client's OKF repo and tenant manifest. Use after a client is ingested and served (KNOWLEDGE-BRIEF generated) to produce a client-specific marketing landing that re-frames Dossier's universal messaging in the client's own vocabulary, with a hero artifact that is a REAL atom from the client's repo. Human-curated authoring, not a hosted runtime.
Author or extract atomic, OKF-compliant concept documents that conform to Dossier's knowledge model. Use whenever turning raw/clean source content (or a topic) into knowledge-base concepts — processes, workflows, roles, decisions, systems, policies, artifacts, terms. Produces one well-formed markdown+YAML file per concept, with full provenance and typed relationships.
Wield the full power of GitHub-Flavored Markdown (GFM) and GitHub's rendering pipeline to design world-class documentation — alerts/admonitions, collapsible sections, tables, task lists, mermaid diagrams, math, footnotes, themed images, auto-anchors, and badges. Use whenever authoring a README, guide, or any markdown that renders on GitHub (and, with the noted caveats, on the Astro Starlight surface). The reference + procedure the documentation-engineer reaches for.
Run the ingestion sweep that pulls a new client's raw knowledge into Dossier — public website (Firecrawl), files (Unstructured), and Microsoft 365/SharePoint (Graph delta + Copilot connectors) — normalized to clean, provenance-stamped markdown ready for extraction. Use when onboarding a client or refreshing their sources.
| name | verify-kb |
| description | Audit an OKF knowledge base for integrity before it ships. Use to verify a generated/edited KB — checks OKF compliance, atomicity, link integrity, provenance/confidence, coverage gaps, and stale content. Produces a severity-ranked report; does not silently fix. |
Adversarially audit an OKF knowledge base (Dossier's own knowledge/, or a client KB). Assume it's incomplete or subtly wrong until proven otherwise. Read knowledge/model/index.md for the rules you're enforcing.
.md has valid YAML frontmatter and a type. Reserved filenames index.md/log.md used correctly. Glob all concepts; flag any missing/invalid frontmatter.[[id]] and every frontmatter edge resolves to an existing concept id. Report orphans (nothing links to them) and dangling links (point to nothing).source, confidence, timestamp present. Flag inferred content presented as fact, and missing provenance. List stale atoms (old timestamp).@dossier/okf wired (Dossier's own, or any provisioned tenant), run pnpm kb:check — it does parse/schema validation, dangling frontmatter edges, and [[wiki-link]] rot deterministically in <1 s (DEC-0060). Treat its output as ground truth for checks 1 & 3; don't hand-walk what it already verifies.Glob **/*.md, Read/Grep frontmatter and [[links]]. For a KB without the okf gate, fall back to building the id/edge sets yourself and diffing for breaks.file:line. Reproducible findings only.A severity-ranked report (blocker → warning → nit), each finding with file, evidence, and a suggested fix. End with a one-line verdict: ship / fix-first. Hand fixes to the owning agent — do not edit silently.