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.

Ingest documents into your Senso.ai knowledge base through Edith smart glasses. Triggers when user wants to add content to their knowledge base.

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

Upload files or raw text into a Senso knowledge base. Handles file upload via presigned URLs, raw text/markdown creation, folder targeting, and processing status polling. Use when the user wants to add documents, files, or text content to their Senso KB.

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

Build a complete, self-healing knowledge base for any company using Senso

Build a complete, self-healing knowledge base for any company using Senso

Take a brand new Senso org from empty to fully populated self-improving knowledge system in 10 minutes. Researches the user's company from their website plus external sources, builds out the knowledge base with brand kit, content types, and tracking prompts, generates the first drafts, publishes sample citeables, kicks off GEO monitoring, and files a self-heal report with gap analysis. The first-run experience for any new Senso user. Use when the user runs Senso for the first time or says "set up Senso", "run onboarding", or "populate my knowledge base".

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.

Browse, organize, and manage the Senso knowledge base folder tree. Create folders, move and rename nodes, view content details, download files, and check sync status. Use when the user wants to structure, reorganize, or explore their KB.

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.

Guide the Senso v2 onboarding experiment: understand the brand, bring in relevant knowledge, compare a recorded external AI answer with approved facts, stage a checked draft with evidence, then publish when requested. Use for Senso quickstart v2, testing the new verification loop, or continuing a v2 onboarding session. Ordinary file saves belong to senso-context-layer.

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.

Voice AI agent skills and MCP tools for Bland AI. Make phone calls, manage personas, knowledge bases, pathways, and more. Use when the user wants to build, test, or manage AI-powered phone agents.

Build and configure an AI-powered phone hotline for loan support using Bland AI, Auth0, and Senso. USE FOR: setting up AI phone agents for lending, creating voice-based loan support systems, integrating Auth0 passwordless OTP with Bland AI voice agents, connecting Senso knowledge bases to phone call workflows, building fintech customer service hotlines. NOT FOR: general web app development, non-voice chatbots, or projects unrelated to phone-based loan support.

Voice AI agent skills and MCP tools for Bland AI. Make phone calls, manage personas, knowledge bases, pathways, and more. Use when the user wants to build, test, or manage AI-powered phone agents.

Explain a piece of code, concept, or system in plain English with zero assumed knowledge. Use when the user is confused, new to a codebase, or says "I have no idea what this does", "explain this to me", or "ELI5".

Generate brand-aligned content using the Senso content engine. Orchestrates brand kit verification, content type selection, prompt management, and generation runs. Use when the user wants to generate content like blog posts, FAQs, comparison pages, or any templated output from their knowledge base.