AGENT SKILL

context-engine

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.

License 许可
MIT
所属仓库
ASoudy/AGS
最近更新
2026-05-23
Stars
★ 0
Forks
0

01 前言 Front Matter

name
context-engine
license
MIT
metadata
{ "author": "Alireza Rezvani", "domain": "orchestration", "updated": 1772668800000, "version": "1.0.0", "category": "c-level", "frameworks": "context-loading, anonymization, context-enrichment" }
description
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.

02 资源文件 1

03 SKILL.md 正文

Company Context Engine

The memory layer for C-suite advisors. Every advisor skill loads this first. Context is what turns generic advice into specific insight.

Keywords

company context, context loading, context engine, company profile, advisor context, stale context, context refresh, privacy, anonymization


Load Protocol (Run at Start of Every C-Suite Session)

Step 1 — Check for context file: ~/.claude/company-context.md

  • Exists → proceed to Step 2
  • Missing → prompt: "Run /cs: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: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

Context Quality Signals

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."


Context Enrichment

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.


Privacy Rules

Never send externally

  • Specific revenue or burn figures
  • Customer names
  • Employee names (unless publicly known)
  • Investor names (unless public)
  • Specific runway months
  • Watch List contents

Safe to use externally (with anonymization)

  • Stage label
  • Team size ranges (1–10, 10–50, 50–200+)
  • Industry vertical
  • Challenge category
  • Market position descriptor

Before any external API call or web search

Apply references/anonymization-protocol.md:

  • Numbers → ranges or stage-relative descriptors
  • Names → roles
  • Revenue → percentages or stage labels
  • Customers → "Customer A, B, C"

Missing or Partial Context

Handle gracefully — never block the conversation.

  • Missing stage: "Just to calibrate — are you still finding PMF or scaling what works?"
  • Missing financials: Use stage + team size to infer. Note the gap.
  • Missing founder profile: Infer from conversation style. Mark as inferred.
  • Multiple founders: Context reflects the interviewee. Note co-founder perspective may differ.

Required Context Fields

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

  • references/anonymization-protocol.md — detailed rules for stripping sensitive data before external calls

04 同仓库更多 Skills

ASoudy
ASoudy/AGS

web-typography

Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", or "typographic scale". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.

★ 0
ASoudy
ASoudy/AGS

ux-heuristics

Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "UX review", "users are confused", "heuristic evaluation", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "usability testing". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.

★ 0
ASoudy
ASoudy/AGS

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "Entrepreneurial Operating System", or "business operating system". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.

★ 0
ASoudy
ASoudy/AGS

top-design

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "premium website", "portfolio site", "scroll animations", "Awwwards quality", "brand experience", "cinematic web design", "parallax storytelling", or "agency-quality site". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.

★ 0
ASoudy
ASoudy/AGS

system-design

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.

★ 0
ASoudy
ASoudy/AGS

storybrand-messaging

Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.

★ 0