cs-onboardFounder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refre...
Install via ClawdBot CLI:
clawdbot install alirezarezvani/cs-onboardGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 20, 2026
A founder launching a new B2B software tool uses /cs:setup to articulate their vision, target market, and core challenges. This helps align C-suite advisors on growth strategy and product development priorities during the pre-PMF phase.
A founder of a direct-to-consumer brand uses /cs:update to refresh company context after rapid team expansion and revenue growth. This ensures advisors provide relevant guidance on operational scaling and fundraising readiness.
A founder transitioning to CEO role uses /cs:setup to redefine company identity and culture post-founder exit. This captures new strategic goals and team dynamics for advisors focusing on organizational stability.
A founder in a product-driven hardware company uses /cs:update to document supply chain challenges and revised timelines. This keeps C-suite advisors informed on operational hurdles and financial runway adjustments.
An executive director uses /cs:setup to outline mission evolution, donor base, and operational constraints. This provides context for advisors on nonprofit-specific challenges like fundraising and program scaling.
Companies with recurring revenue from software licenses use this skill to clarify customer segments and retention strategies. The context file helps advisors optimize pricing tiers and churn reduction tactics.
Founders of two-sided marketplaces use interviews to detail network effects and trust mechanisms. This enables advisors to address liquidity challenges and community governance issues effectively.
Agencies relying on project work and retainers use this to capture client dependencies and capacity constraints. The context supports advisors in improving resource allocation and service diversification.
💬 Integration Tip
Ensure the ~/.claude/company-context.md file is accessible to all C-suite skills by placing it in the correct directory and running /cs:update quarterly to maintain accuracy.
Scored Apr 19, 2026
Search and analyze your own session logs (older/parent conversations) using jq.
Local semantic memory with Qdrant and Transformers.js. Store, search, and recall conversation context using vector embeddings (fully local, no API keys).
Maintain Clawdbot's compounding knowledge graph under life/areas/** by adding/superseding atomic facts (items.json), regenerating entity summaries (summary.md), and keeping IDs consistent. Use when you need deterministic updates to the knowledge graph rather than manual JSON edits.
Manage and retrieve long-term memories with LanceDB using semantic vector search, category filtering, and detailed metadata storage.
Fast semantic memory system with JSON indexing, auto-consolidation, and <20ms search. Capture learnings, decisions, insights, events. Use when you need persistent memory across sessions or want to recall prior work/decisions.
Long-term memory via ChromaDB with local Ollama embeddings. Auto-recall injects relevant context every turn. No cloud APIs required — fully self-hosted.