Loads, validates, and manages the company context file for C-suite advisor sessions, ensuring data freshness and enforcing privacy rules before external interactions.
Say it in your own words; the assistant finds this recipe by itself. Examples:
Use this skill at the start of any C-suite advisor session to initialize the working memory with company details. It is also required when the context file is missing, outdated, or when preparing to send company data to external APIs or search engines to ensure compliance with privacy protocols.
The memory layer for C-suite advisors. Every advisor skill loads this first. Context is what turns generic advice into specific insight.
company context, context loading, context engine, company profile, advisor context, stale context, context refresh, privacy, anonymization
Step 1 — Check for context file: ~/.claude/company-context.md
- Exists → proceed to Step 2
- Missing → prompt: "Run /cs-onboard setup to build your company context — it makes every advisor conversation significantly more useful."
Step 2 — Check staleness: Read Last updated field.
- < 90 days: Load and proceed.
- ≥ 90 days: Prompt: "Your context is [N] days old. Quick 15-min refresh (/cs-onboard update), or continue with what I have?"
- If continue: load with [STALE — last updated DATE] noted internally.
Step 3 — Parse into working memory. Always active: - Company stage (pre-PMF / scaling / optimizing) - Founder archetype (product / sales / technical / operator) - Current #1 challenge - Runway (as risk signal — never share externally) - Team size - Unfair advantage - 12-month target
| Condition | Confidence | Action |
|---|---|---|
| < 30 days, full interview | High | Use directly |
| 30–90 days, update done | Medium | Use, flag what may have changed |
| > 90 days | Low | Flag stale, prompt refresh |
| Key fields missing | Low | Ask in-session |
| No file | None | Prompt /cs-onboard setup |
If Low: "My context is [stale/incomplete] — I'm assuming [X]. Correct me if I'm wrong."
During conversations, you'll learn things not in the file. Capture them.
Triggers: New number or timeline revealed, key person mentioned, priority shift, constraint surfaces.
Protocol:
1. Note internally: [CONTEXT UPDATE: {what was learned}]
2. At session end: "I picked up a few things to add to your context. Want me to update the file?"
3. If yes: append to the relevant dimension, update timestamp.
Never silently overwrite. Always confirm before modifying the context file.
Apply references/anonymization-protocol.md:
- Numbers → ranges or stage-relative descriptors
- Names → roles
- Revenue → percentages or stage labels
- Customers → "Customer A, B, C"
Handle gracefully — never block the conversation.
Required:
- Last updated (date)
- Company Identity → What we do
- Stage & Scale → Stage
- Founder Profile → Founder archetype
- Current Challenges → Priority #1
- Goals & Ambition → 12-month target
High-value optional:
- Unfair advantage
- Kill-shot risk
- Avoided decision
- Watch list
Missing required fields: note gaps, work around in session, ask in-session only when critical.
references/anonymization-protocol.md — detailed rules for stripping sensitive data before external callsLICENSESKILL.mdreferences/anonymization-protocol.mdVendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-advisor/skills/context-engine, licence MIT. The upstream licence file ships inside the skill.