Read, write, search and organize a Senso context layer — the shared knowledge base a team and their agents both use. Use whenever the user names material or asks about what is in the knowledge base: saving a file or a note ("save revenue.pdf to Senso", "remember this for later"), looking something up ("what did we decide about pricing", "what's in our knowledge base", "look it up in our docs"), handing saved work to a teammate, importing the organization's website, or a `senso` command that returned an error the user does not understand. The flow skills load this one for every knowledge base command. Not for a user who has not named material and wants to be got started — that is senso-quickstart — and not for unrelated wikis or vector databases.

A full end-to-end hackathon coordination skill. Use this skill whenever a user mentions a hackathon, hack day, build competition, or sprint event — even casually (e.g., "we're doing a hackathon this weekend", "I want to prep for a hackfest", "help us organize our hack team"). This skill guides a solo hacker or team through every phase: intake of hackathon details, team formation, idea collection and selection, GitHub repo setup, task assignment, vibe-coding, presentation prep, and final submission. Works in Claude Code, Claude.ai, and any coding agent that supports skills. Trigger this skill even when the user only mentions one phase (e.g., "help us pick an idea for our hackathon") — always load the full skill to understand context and jump in at the right phase.

Configure a Senso organization's brand kit (voice, tone, persona, writing rules) and content type templates. Use when the user wants to set up or update their brand identity, create content output formats, or prepare for content generation.

Read and work a Senso organization's gap report — the questions and claims its knowledge base could not back up, and what was decided about each. Use for "what are my gaps", "what can't we answer", "what's missing from our knowledge base", "show the gap report", for acting on a gap someone already found ("close this gap", a gap id in hand), for recording that content was written for a gap, and for dismissing one. Not for finding the next industry question the brand is missing from — that is senso-verification-loop — and not for writing content, which is senso-generate-verify.

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).

Search a Senso knowledge base for verified answers, context chunks, or content IDs. Use when the user asks a question that should be grounded in organizational knowledge, says "check Senso", or needs factual answers backed by verified documents.

The one-time setup for Senso's Verification Loop: the brand's own material in the knowledge base, the industry set, the brand name confirmed, which part of the industry they occupy noted, and the content type and brand kit ready for drafting. Use when senso-verification-loop hands here because an organization is not set up, or when a user names one of these chores — "set my industry", "what industry are we", "match me to an industry", "change my industry", "is my brand name right", "which part of the industry do we cover". A user who asks for the loop itself belongs to senso-verification-loop, which runs this skill first when it has to. Not for finding a question, drafting or publishing, and not for a user who named material to save, which is senso-context-layer.

Senso's Verification Loop — find a question people in the brand's industry ask AI models where a competitor gets named and the brand does not, fix it from the brand's own material, and publish a verified page every line of which traces to a document they supplied; then the next one. Use for "let's go through the Verification Loop", "Verification Loop", "fill another gap", "what am I missing from", "how do I rank", "am I being cited", "who's beating us", "where do we stand", "how are our tracked questions doing", "what do the models say about us" and "check what the models say about us" — and when the senso-quickstart router sends a user here. Runs the setup skill first when the organization is not set up. Not for a user who named material to save (senso-context-layer), and not for the gap report on its own (senso-gap-report).