Stats
Actions
Tags
From opscompanion
Load org, user, integration, and workspace context to ground the conversation. Use at session start or when the user asks about their org/team/environment context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/opscompanion:opscompanion-contextThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are loading organizational context from OpsCompanion to ground this conversation with team knowledge.
You are loading organizational context from OpsCompanion to ground this conversation with team knowledge.
Run:
opc --agent claude context
| Flag | Description |
|---|---|
--full-memory | Show full memory bodies instead of excerpts |
--computed-links | Include computed workspace links |
-v, --verbose | Show detailed nodes and integration entries |
For a deeper context load with full memory, run:
opc --agent claude context --full-memory
The context command returns structured markdown with these sections:
| Section | Contains |
|---|---|
| Identity | Organization name, user name, email, public IDs |
| Integrations | Configured cloud providers and services |
| Workspaces | Workspace names, node counts, providers |
| Memory | Organization and user memory (excerpts by default, full with --full-memory) |
After loading context, use it to:
If opc --agent claude context fails with a config error, invoke the opscompanion-init skill to set up the CLI first.
Present the context as a brief summary, not a raw dump. Highlight what's most relevant to the current conversation. Example:
You're Kenneth Eversole at OpsCompanion. Your org has 10 integrations across AWS, Azure, GCP, and others. Two workspaces: dev (Azure) and Production (multi-cloud, 24 nodes).
npx claudepluginhub opscompanion/opscompanion-skills --plugin opscompanionActivate for: load context, inject context, cross-domain context, context for this endeavour, relevant background, multi-domain context, what context do I need, before I work on this, context from HR, context from finance, context from ops, combine context, cross-domain brief, what should I know before starting. NOT for: situation briefs (use executive-brief), search queries (use workplace-search).
Discovers team structure, terminology, goals, performance frameworks, values, and ways of working by crawling Slack, Notion, Google Drive, Gmail, Calendar; validates with manager before persisting.
Builds a structured personal context dataset in TypeDB from connected services (Gmail, Calendar, GitHub, LinkedIn, HealthKit, Drive). Useful for maintaining operator context across sessions.