Access shared business context including company identity, mission, org chart, staff directory, and policies. Use this when an agent needs to understand the business they work for, organizational structure, who's who, or business policies. Returns content from org/business/ directory.
The Business Context skill provides read-only access to organizational information for Aphebis.
All agents need to understand the business they work for. Without shared context, each agent would need business information baked into its definition—creating maintenance overhead and potential inconsistencies.
This skill is the single source of truth for business context. Edit files in org/business/ once, and all agents have access.
org/business/
├── README.md # This directory's overview
├── company.md # Company identity, stage, industry
├── mission.md # Mission, vision, values
├── org-chart.md # Organizational structure, reporting
├── staff.md # Humans, AI agents, skills
└── policies.md # Financial, risk, technical policies
| Query | Returns | Use When... |
|---|
company | Company identity, stage, industry, description | You need to understand what Aphebis is |
mission | Mission, vision, values, what we're not | You need to understand our purpose and principles |
org-chart | Organizational structure, reporting relationships | You need to know who reports to whom, how the org works |
staff | Personnel (humans + AI agents), contact protocols | You need to know who works here, how to reach them |
policies | Financial, risk, technical, communication policies | You need to understand our constraints and guidelines |
all | Complete business context summary | You need a comprehensive overview |
Before advising on a decision:
"I need to understand Aphebis's risk tolerance before I can advise."
→ Invoke business-context with query: "policies"
→ Returns financial and risk policies for context
Before making a recommendation:
"Let me check our mission to ensure this aligns."
→ Invoke business-context with query: "mission"
→ Returns mission, vision, values
When coordinating work:
"Who should handle this technical question?"
→ Invoke business-context with query: "staff"
→ Returns staff directory with roles and reporting
If you need the raw file content for processing:
org/business/{filename}.mdThis skill is READ-ONLY. It cannot modify business context files.
To update business context:
org/business/When creating a new agent:
Example agent instruction:
When making business recommendations, always invoke the business-context skill
first to understand our current mission, values, and policies.
When creating a new skill:
Agent: business-manager Situation: Evaluating a new market opportunity
"Before I assess this market opportunity, I need to understand our strategic
position and risk tolerance."
→ business-context query: "company" + "policies"
→ Returns: Aphebis is bootstrapped, risk-tolerant on product/technical,
risk-averse on legal/compliance, must prove ROI for expenses
→ Agent now has proper context to evaluate the opportunity
Agent: technical-strategy-advisor Situation: Recommending a technology stack
"I need to understand our technical policies and constraints before
recommending an architecture."
→ business-context query: "policies"
→ Returns: Agent-first architecture, MCP-native, simple scales,
no vendor lock-in
→ Agent ensures recommendation aligns with policies
Agent: Any agent Situation: Unsure who to escalate to
"Who handles compliance questions?"
→ business-context query: "staff"
→ Returns: Technical Strategy Advisor handles compliance; reports to Alex
→ Agent knows to escalate to technical-strategy-advisor
If a query fails:
org/business/Potential additions to the business context system:
products.md - Product catalog, features, roadmapcompetitors.md - Competitive landscape analysiscustomers.md - Customer personas, segments (when we have them)metrics.md - Key business metrics (when we track them)context-summary.json - Machine-readable quick referenceAdditions should follow the same pattern:
.md file in org/business/