11 results for “organize”
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 ("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.
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.
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).
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.
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.
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).
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, 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).
This skill should be used when a user pastes a Senso link (docs.senso.ai, senso.ai) and asks to set it up, or says "connect my agent to Senso", "set up Senso", "sign me in to Senso", "sign me back in to Senso" or "use Senso as my knowledge base", or when a senso command fails because the CLI is missing or the key is rejected. It installs the Senso CLI and skills, signs the user in through the browser, confirms the organization with them, then hands to Shared Context. Works for first-time and returning users. Not for a user already connected who names a task.