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.
Search YouTube transcripts for timestamped quotes, speaker appearances, mentions, sponsors and recommendations. Use for Arcmira MCP or CLI research across videos and livestreams.
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).
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).
The way into Senso when the user has not said which path they want. Use for "get me started with senso" (the phrase they are given to paste), "set up Senso", "run onboarding", "help me with Senso", or any ask for help with Senso that names no material and no path. It says what Senso is, offers the two paths — the Verification Loop and Shared Context — and hands to the one they pick. A user who names a path up front belongs to that path's skill, not here; a user who names material to save belongs to senso-context-layer. This skill runs no setup and no loop of its own.
Put an approved Senso draft live where AI models can cite it, and follow what happens to it. Use for publishing generated content ("publish this", "make it live", "push it to citeables"), checking or retrying where it went ("did it publish", "retry the failed one"), pulling it back ("unpublish", "take it down"), and for what happened after — citations, which prompts a page is winning, and the provenance audit of a live URL. Also destinations and the call-to-action card. The publish step of senso-verification-loop. Not for writing or checking content — that is senso-generate-verify.
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.
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.
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).
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-first AI senior care companion. Calls seniors daily to check mood, medications, and needs. Detects falls, loneliness, and service requests (food, medicine, bathing, transportation). Alerts family with recommended local services. Use when building senior care, voice AI, or healthcare check-in applications.
Search your Senso.ai knowledge base hands-free through Edith smart glasses. Triggers on knowledge/document queries.
Use this skill to scan URLs and inbox messages for scams targeting older adults, monitor an inbox autonomously, publish results to cited.md, and enforce x402-style payment rails for ElderShield.
Develops and operates the Nexus research cockpit: FastAPI + TinyFish live agent, Redis streams/pub-sub, WunderGraph Cosmo GraphQL subscriptions, React D3 graph. Use when editing Nexus, sessions, tinyfish_runner, discovery, final report, normalization, embeddings, or graph UI.
Use when adding authentication or login to any app - detects your stack (React, Next.js, Vue, Nuxt, Angular, Express, Fastify, React Native), sets up an Auth0 account if needed, and routes to the correct SDK setup workflow.
Generate a structured mental model of an unfamiliar codebase — entry points, data flow, key abstractions, and gotchas. Use when starting on a new repo, when the user says "explain this codebase", "how does this work", "onboard me", or before making large changes to unfamiliar code.
Use when adding authentication to Next.js applications (login, logout, protected pages, middleware, server components) - supports App Router and Pages Router with @auth0/nextjs-auth0 SDK.
Add, configure, and integrate assistant-ui components in React apps. Use when developers ask to add a chat thread, set up a runtime, integrate with AI SDK, configure tools, or build AI chat interfaces with assistant-ui.
Package and deploy an AI agent to production with logging, tracing, and health checks. Supports TrueFoundry, Modal, Railway, Fly.io, and containerized deploys. Use when the user says "deploy this agent", "put this in prod", "containerize my agent", or "add observability".
Manage the Senso content verification and publishing workflow. List items awaiting review, approve or reject content versions, publish to external destinations, save drafts, manage content ownership, and unpublish content. Use when the user wants to review, approve, reject, or publish generated content.