C-Level Advisory ContextConfigurationData

Context Engine

Load and manage company context for all C-suite advisor skills.

$skillfish add ~skills/context-engine

Capabilities Real Examples Get Started Models & Context

What This Skill Can Do

Concrete capabilities you get when you install this skill.

Build and maintain a company context document across all strategic dimensions

Capture ICP, positioning, competitive landscape, and messaging in structured form

Define company metrics baseline with definitions and current-state benchmarks

Provide instant onboarding context for new executives and advisors

Run quarterly context refresh sessions to keep the document current

Synthesize disparate company knowledge into a single maintained source of truth

Real Conversations

See how the Context Engine skill responds to actual requests. These are representative examples of what your AI agent will produce.

You

I want to start using the C-suite advisor skills seriously but every conversation starts from scratch — I have to re-explain that we're B2B SaaS, HR tech, $2.8M ARR, 32 employees, Series A, targeting 150-1000 employee companies. How do I set up the context engine so all advisors have the full picture?

Agent

The Context Engine is designed exactly for this — it's a structured company profile that all C-suite skills load before advising.

Your Company Context Document:

company:
  name: [Your company]
  product: B2B SaaS — HR tech platform
  stage: Series A
  arr: $2.8M
  growth_rate: [MoM %]
  headcount: 32
  funding: [Amount raised, lead investor]

icp:
  company_size: 150-1000 employees
  buyer: HR Director / VP People
  geography: US (primary)
  vertical: [Any specific verticals you win in]

metrics:
  nrr: [%]
  acv: [Average contract value]
  cac_payback: [Months]
  gross_margin: [%]
  runway: [Months]

team:
  leadership: [CEO/CTO/etc. and brief backgrounds]
  engineering: [Size, stack]
  sales: [Size, model — inbound/outbound]

strategy:
  top_priorities_this_quarter: [3 items]
  biggest_risks: [Top 2-3]
  active_decisions: [What you're currently deciding]

How to use it: Paste this document at the start of any C-suite advisor session. All advisors are designed to consume this format and calibrate advice accordingly.

Maintenance: Update quarterly minimum — ARR, headcount, and active decisions change fastest. Stale context produces stale advice.

Want me to help you fill in each field based on what you've shared?

You

I use the CEO advisor, CFO advisor, and CTO advisor regularly — sometimes in the same week. Each session feels disconnected. The CEO advisor doesn't know what I discussed with the CFO advisor last week. How do I create continuity?

Agent

This is the core problem the Context Engine solves — it's the shared memory layer across all C-suite advisor sessions.

Two-Layer Context Architecture:

Layer 1 — Static Company Context (update quarterly) The company profile document: metrics, team, strategy, ICP. Every advisor loads this at session start.

Layer 2 — Dynamic Session Log (update after each session) Maintain a running advisor log that captures:

[Date] CFO Advisor — Topic: Q4 budget reforecast
Key decisions: Approved $45K additional headcount for 2 AEs in Q1
Open questions: Should we reduce infrastructure spend or take the revenue risk?
Action items: Model 3 scenarios for board by Dec 15

[Date] CTO Advisor — Topic: Engineering hiring plan
Key decisions: Hire 2 senior engineers before 2 junior engineers
Context for other advisors: Engineering capacity is the bottleneck on roadmap, not product direction

Cross-pollination protocol: When starting a CEO advisor session, paste the last 2-3 entries from your log: "Here's what I discussed with CFO and CTO advisors this week — factor this in."

Practical setup:

Keep a Notion page or doc called "Advisor Context — [Month]"
After each session, spend 5 minutes writing a 3-5 bullet summary
At the start of the next related session, paste the relevant summaries

This turns disconnected sessions into a connected advisory board. Do you want a template for the session log?

Get Started

How to install and use this skill in your preferred environment.

Skills are designed for AI coding agents (Claude Code, Cursor, Windsurf) and IDE-based workflows where the agent can read files, run scripts, and act on your codebase. Web-based AI can use the knowledge and frameworks, but won't have tool access.

Models & Context

Which AI models and context windows work best with this skill.

Recommended Models

Best

Claude Opus 4 Claude Sonnet 4 GPT-4.1 Gemini 2.5 Pro Grok 3 Kimi K2

Good

Claude Haiku 4.5 GPT-4.1 mini Gemini 2.5 Flash Grok 3 mini

Larger models produce more detailed, production-ready outputs.

Context Window

This skill's SKILL.md is typically 3–10 KB — fits in any modern context window.

8K Skill only

32K+ Skill + conversation

100K+ Skill + references + codebase

All current frontier models (Claude, GPT, Gemini) support 100K+ context. Use the full window for complex multi-service work.

Pro tips for best results

1

Be specific

Include numbers — users, budget, RPS — so the skill can size the architecture.

2

Share constraints

Compliance needs, team size, and existing stack all improve the output.

3

Iterate

Start with a high-level design, then ask follow-ups for IaC, cost analysis, or security review.

4

Combine skills

Pair with companion skills below for end-to-end coverage.

Ready to try Context Engine?

Install the skill and start getting expert-level guidance in your workflow — any agent, any IDE.