Use this skill to generate well-branded interfaces and assets for Cogni Work (cogni-work.ai / insight-wave), either for production or throwaway prototypes, mocks, decks, and design artifacts. Contains the essential design guidelines, colors, type, fonts, assets, and UI kit components needed to prototype or ship…
This skill should be used when the user wants to manage the WBS of a cogni-consult engagement — listing each action field's deliverables and their status, planning a field's deliverable set, picking the next deliverable to work, adding/splitting/merging action fields after scoping, or setting a deliverable's schedule…
Generate an interactive HTML dashboard showing a cogni-consult engagement's status — action fields, deliverables, design-thinking stage, and persona-review progress. Use whenever the user mentions dashboard, engagement dashboard, engagement status, "show me the engagement", "visualize the engagement", WBS view, status…
This skill should be used when the user wants to produce a deliverable of a cogni-consult engagement by running its design-thinking loop — empathize→define→ideate→prototype→test on one deliverable inside an action field. Trigger on: "work the deliverable", "run design thinking on ", "produce the deliverable", "start…
This skill should be used when the user wants to manage or invoke the acting stakeholder personas of a cogni-consult engagement — defining personas from the scope's Stakeholder dimension, enriching one with evidence, or having a persona challenge a deliverable in its own voice. Trigger on: "set up the personas", "add…
This skill should be used when the user wants a phased roadmap or timeline of a cogni-consult engagement's own WBS deliverables — sequenced from the dependency graph and durations and written as an Obsidian-browsable markdown artifact. Trigger on: "project plan", "engagement timeline", "roadmap", "show the roadmap"…
This skill should be used when a consultant elects to turn a completed cogni-consult deliverable into presentation-ready documentation — a brief the consultant hands to Claude Design to render. Trigger on: "publish this deliverable", "turn into slides", "make a poster/web page from ", "build a report from ", "make an…
This skill should be used when the user wants to resume, continue, or check the status of a cogni-consult engagement across sessions. Trigger on: "continue the engagement", "resume the engagement", "engagement status", "where was I with the engagement", "what's next for the engagement", "show engagement progress"…
This skill should be used when the user wants to scope a cogni-consult engagement — framing the SMART key question, working the five scoping dimensions, and deriving the 3-6 action fields that become the engagement's work-breakdown structure. Trigger on: "scope the engagement", "consult scope", "frame the key…
This skill should be used when the user wants to start a new consulting engagement — cogni-consult is the action-fields-WBS engagement model, so new structured consulting work starts here. Trigger on: "start a consult engagement", "new consulting engagement", "set up a consult project", "begin an action-fields…
Compose a research report by reading the bound cogni-wiki knowledge base, then re-deposit the result back into the same wiki — the wiki-roundtrip primitive. Reads .cogni-knowledge/binding.json to resolve the wiki path so the user does not have to. Dispatches cogni-research with reportsource=wiki against the bound…
Research a topic INTO a bound cogni-knowledge base — runs cogni-research on the topic and deposits the findings into the knowledge base's wiki in one prompt. Reads .cogni-knowledge/binding.json to resolve the wiki path so the user does not have to. Every deposited page is stamped with derivedfromresearch: , and the…
Phase 5 of the inverted pipeline. Reads /.metadata/plan.json + /.metadata/ingest-manifest.json + the populated cogni-wiki, dispatches a wiki-composer pass (plus ONE bounded fail-soft zero-network coverage-gated re-dispatch when a sub-question has ingested evidence the draft left uncited), and lands /output/draft-vN.md…
Phase 2 of the inverted pipeline. Reads plan.json, dispatches one source-curator agent per sub-question to WebSearch + score candidate sources AND fetch each survivor's body via WebFetch into the shared fetch-cache, then merges the per-sub-question batches into candidates.json via candidate-store.py. Each candidate…
Render an HTML dashboard for a bound cogni-knowledge base — runs the vendored wiki-dashboard scripts (renderdashboard.py + buildgraph.py) natively against the bound wiki and writes a knowledge-overlay.md sidecar that lists deposited research projects and the latest lint-audit claimdrift count. Use this skill whenever…
Phase 4.5 of the inverted pipeline (between ingest and compose). Distills the run's source claims into recurring type:concept / type:entity / type:person pages, creating-or-merging them under a lock with claim-level dedup so the bound wiki compounds across runs (distilled pages get enriched, not duplicated). Also…
Phase 3 of the inverted pipeline. Builds fetch-manifest.json from the fetch results the curators already produced in Phase 2 (bodies are already fetched during curate). Cobrowse is OPT-IN (--cobrowse): the skill walks the user through enabling the Claude-in-Chrome extension, then dispatches source-fetcher sequentially…
Phase 7 of the inverted pipeline — deposits the verified draft as a wiki synthesis page, closing the compounding loop. Reads the latest verified draft plus its verify and citation manifests, refuses self-citing loops, atomically writes the synthesis page into the bound wiki, updates the surrounding index, log, and…
Run a read-only structural health check on a cogni-knowledge base — page/link/schema integrity plus entries-count and claim drift for the bound wiki. Use this skill whenever the user says 'check knowledge health', 'knowledge health', 'is my knowledge base healthy', 'audit the knowledge base structure', 'knowledge…
Rebuild the curated root index + per-type sub-indexes of a cogni-knowledge base on demand, migrate an EXISTING pre-0.0.8 wiki to the curated layout (control files into wiki/meta/, overview folded into the index intro, flat root split into root-map + sub-indexes, schema 0.0.7→0.0.8), or repair drifted machine-owned…
Standalone single-source ingest for cogni-knowledge — deposit ONE source directly into the bound wiki with no research run: a web page or PDF URL, a local file (.docx/.html/.txt), pasted text, a local PDF, or a local interview note. Lands one wiki/sources/ .md page (or wiki/interviews/ .md with type: interview for an…
Phase 4 of the inverted pipeline. Reads fetch-manifest.json, dispatches source-ingester per fetched source to write wiki/sources/ .md pages with preextractedclaims:, merges per-source results into ingest-manifest.json, then consolidates the wiki integration (backlinks, thematic index, question nodes, sub-indexes) into…
Run semantic lint on a cogni-knowledge base — surface stale pages/drafts, claim drift, and broken reverse links, optionally repairing the mechanical classes with --fix. Use this skill whenever the user says 'lint the knowledge base', 'knowledge lint', 'fix knowledge drift', 'clean up the wiki', 'repair reverse links'…
Phase 1 of the inverted pipeline. Decomposes a research topic into 3-7 sub-questions with per-sub-question candidate-domain hints, writes plan.json into a fresh project directory under the bound knowledge base. Pure decomposition by default (no web); an optional, fail-soft preliminary scoping search engages only…
12 3d agoA156 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: