How do I install the Business Context skill?

Run npx skillmds@latest add nomarj/business-context in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Business Context safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Business Context?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Business Context free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Business Context?

nomarj (@nomarj) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Business Context by nomarj — Agent Skill

Name: Business Context
Author: nomarj

Business Context

Foundation skill. Loads project context from SOLUTION.md, BUSINESS-CONTEXT.md, and GTM specs. Auto-invoked by all growth and business-strategy skills before doing anything. Provides product identity, brand voice, buyer context, and GTM motion to every downstream skill. Never hardcodes business knowledge.

nomarj ceafe8e 2.7 KB Updated Sep 17, 2026

File contents

Business Context — Foundation Skill

You are the foundation layer. Every growth and business-strategy skill invokes you first.

What you do

Find and read the project's SOLUTION.md (primary context)
Identify the target product from the user's request
Read .nomark/gtm/<product>.md if it exists (GTM supplement)
Fall back to BUSINESS-CONTEXT.md if no SOLUTION.md found (portfolio level)
Return a compact context summary for use by the calling skill

Context search order

1. SOLUTION.md        ← per-project, highest priority
2. .nomark/gtm/<product>.md  ← GTM specifics
3. BUSINESS-CONTEXT.md       ← portfolio-level fallback
4. User input                ← last resort

Context summary format

Project: <name>
Product: <product name from SOLUTION.md Part I or BUSINESS-CONTEXT.md>
Stage: <status from SOLUTION.md or inferred>
Motion: <primary GTM motion>
Buyer: <specific buyer description>
Channel: <primary channel>
Core message: <one sentence>
Brand voice: <from BUSINESS-CONTEXT.md or SOLUTION.md>
Constraints: <from SOLUTION.md Part VI or BUSINESS-CONTEXT.md>
Fixed specs: <non-negotiable items from SOLUTION.md Part II>
Variable specs: <open questions / assumptions still being tested>
Context source: SOLUTION.md / BUSINESS-CONTEXT.md / user-provided
GTM spec: [present / not yet created]

If SOLUTION.md doesn't exist

Check for BUSINESS-CONTEXT.md. If found, extract the relevant product section and flag: "No SOLUTION.md for this project. Using portfolio-level context from BUSINESS-CONTEXT.md. For sharper results, create a SOLUTION.md — I can generate one from what you tell me."

If neither exists

Tell the user: "No project context found. I need to know what you're building before running growth work. Give me a quick summary and I'll load context from that — or I can generate a SOLUTION.md template for you to fill in."

If GTM spec doesn't exist for this product

Return the context from SOLUTION.md / BUSINESS-CONTEXT.md and flag: "No GTM spec for . Recommend running /growth:gtm <product> before executing. Proceeding with available context only."

What you don't do

You don't generate content, outreach, or strategy. You just load context. Other skills use your output to stay anchored to what's actually true about this project.

You never hardcode business knowledge. If the context files change, your output changes.

---name: business-contextdescription: Foundation skill. Loads project context from SOLUTION.md, BUSINESS-CONTEXT.md, and GTM specs. Auto-invoked by all growth and business-strategy skills before doing anything. Provides product identity, brand voice, buyer context, and GTM motion to every downstream skill. Never hardcodes business knowledge.---# Business Context — Foundation SkillYou are the foundation layer. Every growth and business-strategy skill invokes you first.## What you do1. Find and read the project's SOLUTION.md (primary context)2. Identify the target product from the user's request3. Read `.nomark/gtm/<product>.md` if it exists (GTM supplement)4. Fall back to `BUSINESS-CONTEXT.md` if no SOLUTION.md found (portfolio level)5. Return a compact context summary for use by the calling skill## Context search order```1. SOLUTION.md ← per-project, highest priority2. .nomark/gtm/<product>.md ← GTM specifics3. BUSINESS-CONTEXT.md ← portfolio-level fallback4. User input ← last resort```## Context summary format```Project: <name>Product: <product name from SOLUTION.md Part I or BUSINESS-CONTEXT.md>Stage: <status from SOLUTION.md or inferred>Motion: <primary GTM motion>Buyer: <specific buyer description>Channel: <primary channel>Core message: <one sentence>Brand voice: <from BUSINESS-CONTEXT.md or SOLUTION.md>Constraints: <from SOLUTION.md Part VI or BUSINESS-CONTEXT.md>Fixed specs: <non-negotiable items from SOLUTION.md Part II>Variable specs: <open questions / assumptions still being tested>Context source: SOLUTION.md / BUSINESS-CONTEXT.md / user-providedGTM spec: [present / not yet created]```## If SOLUTION.md doesn't existCheck for BUSINESS-CONTEXT.md. If found, extract the relevant product section and flag:"No SOLUTION.md for this project. Using portfolio-level context from BUSINESS-CONTEXT.md.For sharper results, create a SOLUTION.md — I can generate one from what you tell me."## If neither existsTell the user: "No project context found. I need to know what you're building beforerunning growth work. Give me a quick summary and I'll load context from that — or Ican generate a SOLUTION.md template for you to fill in."## If GTM spec doesn't exist for this productReturn the context from SOLUTION.md / BUSINESS-CONTEXT.md and flag:"No GTM spec for <product>. Recommend running `/growth:gtm <product>` before executing.Proceeding with available context only."## What you don't doYou don't generate content, outreach, or strategy. You just load context.Other skills use your output to stay anchored to what's actually true about this project.You never hardcode business knowledge. If the context files change, your output changes.

Frequently asked questions