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.
Setup for Senso's Shared Context path. It writes Start Here, the first document every agent on the team reads, at the root of the knowledge base. The user describes the organization, or the agent writes it from a project folder, a file, or the organization's own documents. Use when senso-shared-context sends the user here because the knowledge base is empty or has no Start Here, or when the user says "set up Shared Context" or "write our Start Here". Do not use for the Verification Loop setup (senso-verification-loop-setup). Do not use when the user names material to save (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 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.
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.
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, get the answer into the brand's own knowledge base, then offer to fix the gap — a verified page, on the Optimization tier; then the next question. Use for "let's go through the Verification Loop", "Verification Loop", "fill another gap", "find another question", "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 organization's memory. It holds the knowledge, policies, procedures and decisions that a team keeps up to date together. Every teammate's agent answers from it with sources, and changes are reviewed and saved as new versions. Use for "Shared Context", "shared context", "what's this org about", "catch me up", "how does this team work", "what do we know about", "what did we decide about", "where is our", "that's wrong, fix it", "update the doc", "save this decision", "ask <name>", "leave <name> a question", "push this to Senso", "what's waiting on me", "what can't our agents answer", "what changed since I last looked", and when the senso-quickstart router sends the user here. Runs senso-shared-context-setup first when the knowledge base is empty. Do not use for the Verification Loop (senso-verification-loop). Do not use for a plain save, lookup or handoff of named material (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.
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 ("find our pricing sheet", "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.
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".
Discover, score, and summarize high-signal fans for a creator using web-agent discovery, Redis ranking, and voice access.
Search your Senso.ai knowledge base hands-free through Edith smart glasses. Triggers on knowledge/document queries.
Ingest documents into your Senso.ai knowledge base through Edith smart glasses. Triggers when user wants to add content to their knowledge base.
ClawMax adapter for Senso ingestion. Use this when agents need to ingest files, screenshots, notes, or raw text into Senso using consistent ClawMax naming, foldering, verification, and handoff patterns for hackathon templates.
Use when securing Fastify API endpoints with JWT Bearer token validation, scope/permission checks, or stateless auth - integrates @auth0/auth0-fastify-api for REST APIs receiving access tokens from frontends or mobile apps.
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.
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.
Use when adding authentication (login, logout, protected routes) to Fastify web applications - integrates @auth0/auth0-fastify for session-based auth. For stateless Fastify APIs use auth0-fastify-api instead.
A comprehensive collection of agent skills for managing TrueFoundry platform operations — deployments, secrets, access control, AI gateway, guardrails, logs, MCP servers, prompts, and more.
Packages a locally created Claude skill for publishing to Shipables. Give it a path to your skill directory and it will read the SKILL.md, generate a shipables.json, bundle everything into a .tar.gz archive in /tmp/, and tell you exactly where to find it — ready to drag and drop into the Shipables upload UI. Trigger this skill whenever the user wants to publish, package, upload, or ship a skill to Shipables, or when they say things like "package my skill", "get my skill ready to publish", "prepare skill for shipables", or "create archive for my skill".