AGENT SKILL

cs-onboard

Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.

License 许可
MIT
最近更新
2026-06-06
Stars
★ 0
Forks
0

01 前言 Front Matter

name
cs-onboard
license
MIT
metadata
{ "author": "Alireza Rezvani", "domain": "orchestration", "updated": 1772668800000, "version": "1.0.0", "category": "c-level", "frameworks": "founder-interview, context-capture, quarterly-refresh" }
description
Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.

02 资源文件 2

03 SKILL.md 正文

C-Suite Onboarding

Structured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.

Commands

  • /cs:setup — Full onboarding interview (~45 min, 7 dimensions)
  • /cs:update — Quarterly refresh (~15 min, "what changed?")

Keywords

cs:setup, cs:update, company context, founder interview, onboarding, company profile, c-suite setup, advisor setup


Conversation Principles

Be a conversation, not an interrogation. Ask one question at a time. Follow threads. Reflect back: "So the real issue sounds like X — is that right?" Watch for what they skip — that's where the real story lives. Never read a list of questions.

Open with: "Tell me about the company in your own words — what are you building and why does it matter?"


7 Interview Dimensions

1. Company Identity

Capture: what they do, who it's for, the real founding "why," one-sentence pitch, non-negotiable values. Key probe: "What's a value you'd fire someone over violating?" Red flag: Values that sound like marketing copy.

2. Stage & Scale

Capture: headcount (FT vs contractors), revenue range, runway, stage (pre-PMF / scaling / optimizing), what broke in last 90 days. Key probe: "If you had to label your stage — still finding PMF, scaling what works, or optimizing?"

3. Founder Profile

Capture: self-identified superpower, acknowledged blind spots, archetype (product/sales/technical/operator), what actually keeps them up at night. Key probe: "What would your co-founder say you should stop doing?" Red flag: No blind spots, or weakness framed as a strength.

4. Team & Culture

Capture: team in 3 words, last real conflict and resolution, which values are real vs aspirational, strongest and weakest leader. Key probe: "Which of your stated values is most real? Which is a poster on the wall?" Red flag: "We have no conflict."

5. Market & Competition

Capture: who's winning and why (honest version), real unfair advantage, the one competitive move that could hurt them. Key probe: "What's your real unfair advantage — not the investor version?" Red flag: "We have no real competition."

6. Current Challenges

Capture: priority stack-rank across product/growth/people/money/operations, the decision they've been avoiding, the "one extra day" answer. Key probe: "What's the decision you've been putting off for weeks?" Note: The "extra day" answer reveals true priorities.

7. Goals & Ambition

Capture: 12-month target (specific), 36-month target (directional), exit vs build-forever orientation, personal success definition. Key probe: "What does success look like for you personally — separate from the company?"


Output: company-context.md

After the interview, generate ~/.claude/company-context.md using templates/company-context-template.md.

Fill every section. Write [not captured] for unknowns — never leave blank. Add timestamp, mark as fresh.

Tell the founder: "I've captured everything in your company context. Every advisor will use this to give specific, relevant advice. Run /cs:update in 90 days to keep it current."


/cs:update — Quarterly Refresh

Trigger: Every 90 days or after a major change. Duration: ~15 minutes.

Open with: "It's been [X time] since we did your company context. What's changed?"

Walk each dimension with one "what changed?" question:

  1. Identity: same mission or shifted?
  2. Scale: team, revenue, runway now?
  3. Founder: role or what's stretching you?
  4. Team: any leadership changes?
  5. Market: any competitive surprises?
  6. Challenges: #1 problem now vs 90 days ago?
  7. Goals: still on track for 12-month target?

Update the context file, refresh timestamp, reset to fresh.


Context File Location

~/.claude/company-context.md — single source of truth for all C-suite skills. Do not move it. Do not create duplicates.

References

  • templates/company-context-template.md — blank template for output
  • references/interview-guide.md — deep interview craft: probes, red flags, handling reluctant founders

04 同仓库更多 Skills

AdmiralGallade
AdmiralGallade/harness-repository

verify-sign

Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

template-usage

Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

sign-artifact

Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build/push; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

sei-analytics

Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

security-report

Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says "security report", "vulnerabilities", "SBOM", "security scan", "compliance check", or asks about application security.

★ 0
AdmiralGallade
AdmiralGallade/harness-repository

scorecard-review

Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says "scorecard", "service maturity", "production readiness", "compliance score", or asks about service health scores.

★ 0