Skill Market

onboard

/cs:onboard — Founder interview that populates ~/.claude/company-context.md. The first command to run when starting with c-level-agents.

GitHub
githubcommunityclaude
0.0
0 installs26.1K GitHub starsby alirezarezvani

Skill Introduction

Overview
/cs:onboard — Founder interview that populates ~/.claude/company-context.md. The first command to run when starting with c-level-agents.

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community, claude work faster.

Target users

  • Developers, testers, and maintainers who handle Development tasks in Focus Code.
  • Teams that already trust workflows or content from alirezarezvani.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, claude that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Development, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, claude, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install onboard-41711b
View source

Detail Preview

SKILL.md

Primary filemarkdown4 KB

name: "onboard" description: "/cs:onboard — Founder interview that populates ~/.claude/company-context.md. The first command to run when starting with c-level-agents."

/cs:onboard — Founder Interview

Command: /cs:onboard

The first command to run when adopting c-level-agents. A structured founder interview that produces ~/.claude/company-context.md — the file every cs-* advisor reads before responding. Without this, the advisors are guessing.

What This Produces

~/.claude/company-context.md — a single file with the durable facts about the company. Read by:

  • cs-chief-of-staff (routing decisions)
  • Every cs-* advisor (context for any question)
  • /cs:brief (assumptions in any new decision)

The Interview (12 Questions)

Company Basics

  1. Company name and one-sentence pitch.
  2. Stage: pre-seed / seed / Series A / Series B / Series C+ / public
  3. Headcount: total, by function (eng / product / GTM / ops / G&A)
  4. Geographic distribution: HQ + remote split, key countries

Business Model

  1. Revenue model: SaaS subscription / usage / transaction / marketplace / hardware / services
  2. ICP: name one real customer and describe what they have in common with others
  3. ACV: median and range; deal count last 12 months
  4. Growth rate: ARR YoY; if pre-revenue, leading metric (users, MAU, etc.)

Financial Posture

  1. Runway: months of cash at current burn; bear-case months
  2. Last raise: amount, valuation, lead investor, date

Strategic Context

  1. Top 3 priorities for the current quarter (in plain language)
  2. Top 3 risks the founder loses sleep over (be specific)

Output Format

Saved to ~/.claude/company-context.md:

# Company Context
**Generated:** YYYY-MM-DD
**Last updated:** YYYY-MM-DD

## Identity
- **Company:** <name>
- **Pitch:** <one sentence>
- **Stage:** <stage>
- **HQ + remote:** <distribution>

## Business
- **Model:** <type>
- **ICP:** <description + named customer>
- **ACV:** $<median> (range $<low> - $<high>)
- **Deal count (LTM):** N
- **ARR growth (YoY):** X%

## Financial
- **Cash on hand:** $<amount>
- **Net burn (monthly):** $<amount>
- **Runway base:** N months
- **Runway bear:** N months
- **Last raise:** $<amount> at $<post> in <month YYYY>, led by <investor>

## Team
- **Total headcount:** N
- **Eng:** N | Product: N | GTM: N | Ops: N | G&A: N

## Quarter
- **Top priorities (Q<X> YYYY):**
  1. <priority>
  2. <priority>
  3. <priority>

- **Top risks:**
  1. <risk>
  2. <risk>
  3. <risk>

## Routing Hints
[Optional: any role the founder wants to use sparingly or rely on heavily]

Workflow

  1. Walk the founder through all 12 questions
  2. Quote founder's own words wherever possible (don't paraphrase the ICP)
  3. Save to ~/.claude/company-context.md
  4. (Optional) If llm-wiki bridge is configured: symlink to vault
    ln -sf ~/company-vault/00-meta/company-context.md ~/.claude/company-context.md
    
  5. Confirm with founder: read the file back, ask "anything missing?"

When to Re-Run

  • After a fundraise (numbers change)
  • After a major pivot or product launch
  • After 6+ months (most facts have drifted)
  • After a major hire (team distribution changes)
  • Always before a /cs:boardroom for a high-stakes decision

Persistence

By default, ~/.claude/company-context.md is local to the founder's machine. To make it persistent across machines / shareable:

Related


Version: 1.0.0

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet