Load company background for executive advisor sessions, check whether it is outdated or incomplete, and propose updates learned during conversations. Apply rules for excluding sensitive details and anonymizing permitted information before external searches or API calls.
Loads and manages company context for all C-suite advisor skills. Reads ~/.claude/company-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy/anonymization rules before external API calls. Use when starting any C-suite advisor session, when context looks stale or missing, or before sending company data to an external service.
Review the instructions the agent will receive before you install.
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
Step 2 — Check staleness: Read Last updated field.
[STALE — last updated DATE] noted internally.Step 3 — Parse into working memory. Always active:
| 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: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:
[CONTEXT UPDATE: {what was learned}]Never silently overwrite. Always confirm before modifying the context file.
Apply references/anonymization-protocol.md:
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 callsNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.
Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.
Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.
Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.
Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.
Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.