20 results for “setup”
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).
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.
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.
Retired. This skill's contents moved to three skills — senso-verification-loop-setup (the industry, the brand name, the segment), senso-verification-loop (where the brand stands, the next question it is missing from, the accuracy of answers that name it) and senso-gap-report (the gap report). It no longer does anything. If it is loaded, tell the user to run `senso setup` to install the current skills, and use those.
Use when implementing Auth0 authentication in Nuxt 3/4 applications, configuring session management, protecting routes with middleware, or integrating API access tokens - provides setup patterns, composable usage, and security best practices for the @auth0/auth0-nuxt SDK
Use when adding authentication or login to any app - detects your stack (React, Next.js, Vue, Nuxt, Angular, Express, Fastify, React Native), sets up an Auth0 account if needed, and routes to the correct SDK setup workflow.
Use when adding authentication or login to any app - detects your stack (React, Next.js, Vue, Nuxt, Angular, Express, Fastify, React Native), sets up an Auth0 account if needed, and routes to the correct SDK setup workflow.
Set up Edith smart glasses as an OpenClaw channel. Run this when the user wants to connect their smart glasses to OpenClaw, mentions "Edith glasses", or provides a link code for glasses setup.
Create and modify APIs using WunderGraph Cosmo Connect. Covers gRPC plugin development (Go/TypeScript), standalone gRPC services, schema-to-proto workflows, CLI commands (wgc), local router setup, graph.yaml composition, field resolvers, batching, federation entities, and deployment. Use when building Cosmo Connect subgraphs, plugins, gRPC services, or setting up a local Cosmo Router.
Create and modify APIs using WunderGraph Cosmo Connect. Covers gRPC plugin development (Go/TypeScript), standalone gRPC services, schema-to-proto workflows, CLI commands (wgc), local router setup, graph.yaml composition, field resolvers, batching, federation entities, and deployment. Use when building Cosmo Connect subgraphs, plugins, gRPC services, or setting up a local Cosmo Router.
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.
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.
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.
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).
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).
Set up a data ingestion or sync pipeline — from source to destination, with transformation. Supports Airbyte, custom ETL scripts, and webhook-based ingestion. Use when the user says "sync data from X", "pull data into the DB", "set up a pipeline", or "ingest from API".
Add a demo mode to the app that bypasses auth and loads mock data, so the app works flawlessly during a hackathon presentation without needing a real account or live backend. Use when the user says "set up demo mode", "make it work without login", or "I need it to look good for the judges".
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.
Add, configure, and integrate assistant-ui components in React apps. Use when developers ask to add a chat thread, set up a runtime, integrate with AI SDK, configure tools, or build AI chat interfaces with assistant-ui.
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".