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.

Audit the overall code quality, architecture, and maintainability of a project or file and give an honest, unfiltered assessment. Use when the user asks "is this good?", "what do you think of this codebase?", or wants a holistic review before shipping.

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.

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

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.