business
Skill304 starsChanged 2 months agoMITView on GitHub
Browse, search, and explore your organization's business context system — glossary terms, product catalog, metric definitions, OKRs/objectives, and team structure. This skill provides interactive access to all business knowledge stored in `.knowledge/organizations/`. Use this skill whenever the user wants to understand business terminology, look up metric definitions, explore what products exist, review company objectives, understand team structure, search for business terms, or generally wants to know "what business context do we have?" Trigger on phrases like "/business", "show me our glossary", "what metrics are defined?", "what products do we have?", "show me our OKRs", "who's on which team?", "look up [business term]", "search for [term] in our business knowledge", "what's the definition of [term]?", "show me our business context", "browse our company knowledge", "what teams do we have?", "find [term] in the knowledge base", or any request to view or search organizational knowledge. This skill is especially useful when starting analyses (to understand available metrics and terms), when onboarding new team members (to share business vocabulary), when writing reports (to verify metric definitions match company standards), or when collaborating across teams (to establish shared terminology). Always use this skill instead of reading `.knowledge/organizations/` files directly — it provides formatted, user-friendly output with search, pagination, and helpful error messages.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- matheusflorindo32/apex-elite-frameworktheir own version, first seen Jul 19, 2026
- shristi2211/Claude_Skillstheir own version, first seen May 21, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- shristi2211/Claude_Skills★ 1same name
- matheusflorindo32/apex-elite-framework★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository65 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- always-compareSkill
- analysis-designSkill
- analyst-coreSkill
- archaeologySkill
- archive-analysisSkill
- auth-preflightSkill
- causalSkill
- chart-to-driveSkill
- close-the-loopSkill
- codex-reviewSkill
- compare-datasetsSkill
- connect-dataSkill
- connect-snowflakeSkill
- context-compareSkill
- context-traceSkill
- data-inspectSkill
- data-mapSkill
- data-profilingSkill
- data-quality-checkSkill
- datasetsSkill
- distribution-profilerSkill
- evalSkill
- evaluate-graderSkill
- experiment-briefSkill
- experimentSkill
- exploreSkill
- exportSkill
- forecastSkill
- google-doc-exportSkill
- google-slides-exportSkill
- guardrailsSkill
- historySkill
- improve-contextSkill
- knowledge-bootstrapSkill
- log-correctionSkill
- maintain-contextSkill
- metric-specSkill
- metricsSkill
- monitor-evalsSkill
- notion-exportSkill
- paceSkill
- patternsSkill
- question-framingSkill
- question-routerSkill
- reliabilitySkill
- resume-pipelineSkill
- run-pipelineSkill
- runsSkill
- score-analysisSkill
- session-handoffSkill
- setup-dev-contextSkill
- setup-notionSkill
- setupSkill
- setup-slackSkill
- setup-snowflakeSkill
- srm-checkSkill
- stakeholder-communicationSkill
- stress-testSkill
- switch-datasetSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. About 0 are common, 6 are distinctive, and 16 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
16
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Read .knowledge/setup-state.yaml to find active organization
- Very specific: line 24
If no org configured: "No organization context found.
- Very specific: line 45
Read .knowledge/setup-state.yaml to find active organization name
- Very specific: line 46
REQUIRED: Use helpers/knowledge/business_context.py → load_business_context(org_path) to load data
- Distinctive: line 47
DO NOT manually read YAML files
- Very specific: line 52
Check .knowledge/analyses/index.yaml for past analyses
- Distinctive: line 53
If analyses exist, add a section called "Implicit Knowledge (from Past Analyses)"
- Very specific: line 60
Always provide next steps: suggest /setup to populate formal context, or show how to add entries manually
- Very specific: line 79
If empty: "No glossary terms defined.
- Very specific: line 97
If empty: "No products defined.
- Very specific: line 116
If empty: "No metrics defined.
- Very specific: line 134
If empty: "No objectives defined.
- Very specific: line 152
If empty: "No teams defined.
- Distinctive: line 155
Search across all categories for a term:
- Distinctive: line 157
Search glossary terms (exact + fuzzy match)
- Very specific: line 163
If no match: "No results for '{term}'.
- Very specific: line 166
Use helpers/knowledge/business_context.py → get_glossary(), get_products(), etc.
- Very specific: line 171
Check the active dataset's schema.md for columns matching the term
- Very specific: line 172
Check the active dataset's quirks.md for mentions of the term
- Very specific: line 173
If found, show: "Not in formal glossary, but found in dataset: [column name] — [description].
- Distinctive: line 182
Use tables for structured data (align columns)
- Distinctive: line 184
Always show file paths so users know where to edit
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/business — Business Context Browser
Interactive browser for your organization's knowledge system. Explore terms, products, metrics, objectives, and team structure.
Scope
This skill browses the organization's documented knowledge in
.knowledge/organizations/{org}/business/ (via helpers/knowledge/business_context.py).
It never queries the dataset: /business products shows the product catalog YAML, not the
products table. For what exists in the data, use /explore; for analysis history, /history.
Trigger
Invoked as /business or /business {subcommand}
Prerequisites
- Organization context must exist at
.knowledge/organizations/{org}/ - Read
.knowledge/setup-state.yamlto find active organization - If no org configured: "No organization context found. Run
/setupPhase 3 to configure business context, or create one manually at.knowledge/organizations/{name}/."`
Subcommands
/business (no args) — Overview
Display a summary of available business context:
📊 Business Context: {org_name}
Glossary: {n} terms defined
Products: {n} products cataloged
Metrics: {n} metrics specified
Objectives: {n} OKRs/goals tracked
Teams: {n} teams mapped
Type /business {category} for details.Implementation:
- Read
.knowledge/setup-state.yamlto find active organization name - REQUIRED: Use
helpers/knowledge/business_context.py→load_business_context(org_path)to load data- DO NOT manually read YAML files
- The helper handles file not found errors, parsing errors, and provides consistent structure
- Count entries in each category (glossary, products, metrics, objectives, teams)
- Display summary table
- If business context is empty or sparse (fewer than 3 categories populated):
- Check
.knowledge/analyses/index.yamlfor past analyses - If analyses exist, add a section called "Implicit Knowledge (from Past Analyses)"
- Extract and show:
- Most frequently analyzed metrics (count mentions across analysis titles/tags)
- Recurring business questions or themes
- Common data gotchas from the active dataset's
quirks.md
- This helps new team members understand what the team actually measures, even when formal docs aren't populated yet
- Frame this as "What the team measures (inferred from past work)" vs "Formal documentation (not yet configured)"
- Check
- Always provide next steps: suggest
/setupto populate formal context, or show how to add entries manually
/business glossary — Browse Terms
Display all business term definitions:
📖 Glossary ({n} terms)
Term | Definition | Category
──────────────────|─────────────────────────────────────|──────────
Active User | User with ≥1 session in last 30d | Engagement
Churn | No activity for 60+ days | Retention
...Implementation:
- Load via the helper (
get_glossary()) - Sort alphabetically
- Show first 20 terms; offer "Show all" if more
- If empty: "No glossary terms defined. Add terms to
.knowledge/organizations/{org}/business/glossary/terms.yaml."
/business products — View Product Catalog
Display product hierarchy:
📦 Products ({n} total)
Product | Category | Status | Key Metrics
──────────────────|─────────────|───────────|────────────
Core Platform | SaaS | Active | MAU, Revenue
Mobile App | Mobile | Active | DAU, Retention
...Implementation:
- Load via the helper (
get_products()) - Display in table format
- If empty: "No products defined. Add products to
.knowledge/organizations/{org}/business/products/index.yaml."
/business metrics — Inspect Metric Definitions
Display metric dictionary:
📏 Metrics ({n} defined)
Metric | Type | Formula/Definition | Owner
──────────────────|─────────────|───────────────────────────|──────
Conversion Rate | Ratio | signups / visitors | Growth
MRR | Currency | SUM(active_subscriptions) | Finance
...Implementation:
- Load via the helper (
get_metrics()) - Cross-reference with
.knowledge/datasets/{active}/metrics/if available - Show definition, type, owner
- If empty: "No metrics defined. Use the metric-spec skill to define metrics, or add to
.knowledge/organizations/{org}/business/metrics/index.yaml."
/business objectives — Review OKRs/Goals
Display current objectives:
🎯 Objectives ({n} active)
Objective | Key Results | Status
───────────────────────────────|──────────────────────────|────────
Increase activation rate | +15% by Q2 | On Track
Reduce churn | <5% monthly by Q3 | At Risk
...Implementation:
- Load via the helper (
get_objectives()) - Show status indicators (On Track / At Risk / Behind)
- If empty: "No objectives defined. Add OKRs to
.knowledge/organizations/{org}/business/objectives/index.yaml."
/business teams — Show Team Structure
Display team organization:
👥 Teams ({n} mapped)
Team | Lead | Focus Area | Analysts
──────────────────|─────────────|───────────────────|──────────
Growth | Jane D. | Acquisition | 2
Product | John S. | Core Experience | 3
...Implementation:
- Load via the helper (
get_teams()) - Show team summary
- If empty: "No teams defined. Add team structure to
.knowledge/organizations/{org}/business/teams/index.yaml."
/business lookup {term} — Search
Search across all categories for a term:
- Search glossary terms (exact + fuzzy match)
- Search product names
- Search metric names
- Search objective text
- Display all matches with category labels
If no match: "No results for '{term}'. Try a different search term or browse categories with /business."
Implementation:
- Use
helpers/knowledge/business_context.py→get_glossary(),get_products(), etc. - Case-insensitive substring match across all categories
- Rank: exact match > starts-with > contains
- Show top 10 results with category badge
- If no formal match found AND the term looks like a metric (e.g., contains "rate", "count", "total", "revenue", "user"):
- Check the active dataset's
schema.mdfor columns matching the term - Check the active dataset's
quirks.mdfor mentions of the term - If found, show: "Not in formal glossary, but found in dataset: [column name] — [description]. Consider adding to
/business metricsfor future reference."
- Check the active dataset's
Error Handling
- Missing org directory → suggest
/setupPhase 3 - Empty categories → show helpful "how to add" message with file path
- Malformed YAML → show parse error, suggest checking file syntax
- Partial context (some categories empty) → show what exists, note gaps
Display Rules
- Use tables for structured data (align columns)
- Limit initial display to 20 rows; offer pagination
- Always show file paths so users know where to edit
- Adapt detail level: summary for
/business, detail for subcommands
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

