10 results for “documents”
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.
Ingest documents into your Senso.ai knowledge base through Edith smart glasses. Triggers when user wants to add content to their knowledge base.
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.
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).
Audit all environment variable usage in the codebase and generate a complete, documented .env.example. Use when the user says "what env vars do I need?", "document the config", "set up .env.example", or when onboarding someone new to the project.
Search your Senso.ai knowledge base hands-free through Edith smart glasses. Triggers on knowledge/document queries.
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).
Write an enthusiastic, well-structured PR description for the current changes. Use when the user is about to open a pull request and says "write a PR description", "describe these changes", or "hype up this PR".
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 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.