Hackathon MVP for an entity intelligence cache — query → Redis semantic cache → Ghost (Postgres) entities → Tinyfish Search + mock retrieval → distillation → deltas → synthesis; optional Senso KB publish for cited.md pipeline.

Senso's Shared Context path — the knowledge a team and its agents retrieve, use and improve together: an agent asks, nothing on file answers, the person who knows writes it down, the next agent finds it. Use for "Shared Context", "shared context", "open questions", "what can't our agents answer", "settle that", "save this decision", "what are our agents being told about", "what changed since I last looked" — and when the senso-quickstart router sends a user here. Runs senso-shared-context-setup first when the knowledge base is empty. Not for the Verification Loop (senso-verification-loop), and not for a plain save, lookup or handoff of named material (senso-context-layer).

Write publishable content for a Senso prompt from the knowledge base, and check it before it goes anywhere. The agent drafts from retrieved sources — in the shape of the content type and the voice of the brand kit — states nothing the knowledge base does not back, saves the draft to Senso and sends the user a link to read it rather than printing it into the conversation, and evaluates it once after the user has reviewed it. Use for drafting content for a tracked question ("write something for this prompt", "draft an article", "generate content"), for revising a draft, and for judging a piece of text against the knowledge base or the brand kit ("is this accurate", "check this text against our docs", "run an eval"). Also owns the content type and brand kit commands, which senso-verification-loop-setup runs as chores and this skill runs when a draft is asked for on its own. The drafting and evaluation step of senso-verification-loop. Not for publishing — that is senso-publish.

The setup for Senso's Shared Context path — getting a first document into the organization's knowledge base so the team's agents have something to retrieve, and starting the owner-and-status convention with it. Use when senso-shared-context hands here because the knowledge base is empty, or when a user says "set up Shared Context". Not for the Verification Loop's setup (senso-verification-loop-setup), and not for a user who named material to save (senso-context-layer).