7 results for “onboarding”
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".
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.
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.
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.
Onboard a Vapi voice agent by calling +1 (443) 391 9140 and describing your business in 60-90 seconds. Generates YAML config, materializes files into your IDE, and (optionally) wires the agent to a Stripe payment-link + Telegram notifier with a cited.md audit trail. Cross-tool support for Claude Code, Cursor, Copilot, and Gemini CLI.
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.
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.