Agent skill

Context Builder

by mvschwarz in mvschwarz/openrig

Gather and distill context from meetings, competitors, regulatory sources, and internal discussions.

Apache-2.0Auto-check passedAgent Workflows

Install Context Builder

skills CLI
$ npx skills add mvschwarz/openrig --skill context-builder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvschwarz/openrig context-builder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/_canonical/pm/context-builder .claude/skills/context-builder && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
context-builder
GitHub stars
5.5k
Token cost
~850 tokens
SKILL.md length
285 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
Apache-2.0

At a glance

Gather and distill context from meetings, competitors, regulatory sources, and internal discussions.

  • Works in 4 steps: Understand the Feature → Search and Gather → Update Shared Context (if new knowledge… → …
  • Agent Workflows work in your project
  • SKILL.md covers What You Produce, Three-Layer Context Model, Process and Guidelines
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Context Builder is an agent skill from mvschwarz/openrig. Gather and distill context from meetings, competitors, regulatory sources, and internal discussions. Produces background.md for a feature and updates shared context docs when new knowledge is discovered.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/context-builder”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Understand the Feature
  2. Search and Gather
  3. Update Shared Context (if new knowledge found)
  4. Write background.md

What it can do on your machine

Read from SKILL.md and the folder at commit a7fed63. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Context Builder loads about 850 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 285 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~850

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mvschwarz/openrig at commit a7fed63, republished under its Apache-2.0 licence (© mvschwarz). 285 words, ~850 tokens.

Download SKILL.mdSave it as .claude/skills/context-builder/SKILL.md (or your agent's skills folder).
name
context-builder
description
Gather and distill context from meetings, competitors, regulatory sources, and internal discussions. Produces background.md for a feature and updates shared context docs when new knowledge is discovered.

You are a context research assistant helping a product manager gather and distill all relevant background material for a feature or initiative.

What You Produce

  1. background.md — Feature-specific context summary. Goes in the feature folder. References shared context sources.
  2. Shared context updates — When you discover new synthesized knowledge useful across features (e.g., a customer requirements summary, a competitive analysis), write or update the appropriate shared context doc.

Three-Layer Context Model

reference/              Layer 3 — Raw sources (meetings, PDFs, documents)
    |  distill
context/                Layer 2 — Synthesized markdown (shared across features)
    |  pull relevant
background.md           Layer 1 — Feature-specific context

Process

Step 1: Understand the Feature

Ask the PM:

  • What feature or initiative is this context for?
  • What aspects are most important? (customer needs, competitive, regulatory, technical)
  • Any specific meetings, customers, or competitors to focus on?
Step 2: Search and Gather

Search across all layers. Be thorough but focused:

  • Validation first: Check the feature folder for validation.md (office hours output). If it exists, it has demand evidence, named customers, competitive status quo, and the narrowest wedge.
  • Shared context first: Check if synthesized context already exists.
  • Meetings: Search by topic keywords, customer names. Check last 3-6 months.
  • Competitors: Check competitor research for existing analysis.
  • Regulatory: Find applicable regulations.
  • Customers: Look for customer requests and pain points.
  • Existing specs: Check for related work and shipped features.
Step 3: Update Shared Context (if new knowledge found)

If your research produces synthesized knowledge useful beyond this one feature, write or update the appropriate shared context doc.

Step 4: Write background.md
markdown
---
title: "Background: [Feature Name]"
feature: [feature folder name]
updated: [today's date]
sources:
  meetings: [list of meeting file paths]
  competitive: [list of context/reference paths]
  regulatory: [list of relevant regulatory sources]
  customers: [list of customer context paths]
---

# Background: [Feature Name]

## Customer Drivers
[Who's asking and why. Key quotes and pain points.]

## Competitive Landscape
[How competitors handle this. Where we differentiate.]

## Regulatory Considerations
[Applicable regulations and compliance requirements.]

## Persona Context
[Which personas use this. Day-in-the-life context.]

## Internal Context
[Strategic alignment, stakeholder decisions, related initiatives.]

Guidelines

  • Reference, don't duplicate. Point to source files rather than copying content.
  • Distill, don't dump. background.md should be under 500 lines.
  • Include sources for everything. Every claim traces back to a meeting, report, or decision.
  • Highlight what's surprising or non-obvious.
  • Flag contradictions. If customers want different things, or data conflicts, call it out.
  • Date your sources. Context decays.

© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/_canonical/pm/context-builder of mvschwarz/openrig.

Open the folder on GitHubat commit a7fed63

Compare with similar skills

Context Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Context Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Context Builder this skillmvschwarz/openrig5.5k—~850Automated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official37k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k34 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official37k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    37k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 34 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    37k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    794 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from mvschwarz/openrig

All 49 skills in this repo
  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    5.5k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • OpenRig Software Factory

    mvschwarz/openrig

    Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.

    5.5k GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.

    5.5k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.

    5.5k GitHub stars~341 tokensUpdated today
    Auto-check passed
  • Vault User

    mvschwarz/openrig

    A skill your agent uses when checking the health of this rig's HashiCorp Vault or writing, reading, listing, deleting or explaining its secrets.

    5.5k GitHub starsUsed in 1 repo~451 tokens
    Auto-check passed
  • Agent Refocusing

    mvschwarz/openrig

    Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.

    5.5k GitHub stars~399 tokensUpdated today
    Auto-check passed

Categories

Questions about Context Builder

What does Context Builder do?

Gather and distill context from meetings, competitors, regulatory sources, and internal discussions. Context Builder is an agent skill from mvschwarz/openrig. Gather and distill context from meetings, competitors, regulatory sources, and internal discussions.

When should I use Context Builder?

Context Builder fits situations like: agent Workflows work in your project.

How do I install Context Builder in Claude Code?

Run `npx skills add mvschwarz/openrig --skill context-builder -a claude-code`. Or copy the skill folder (skills/_canonical/pm/context-builder in mvschwarz/openrig) into .claude/skills/context-builder in your project. Claude Code loads it when a task matches its description.

How do I install Context Builder in Codex?

Run `npx skills add mvschwarz/openrig --skill context-builder -a codex`. Or copy the skill folder (skills/_canonical/pm/context-builder in mvschwarz/openrig) into .agents/skills/context-builder in your project. Codex loads it when a task matches its description.

Can I use Context Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill context-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/context-builder, .gemini/skills/context-builder, .github/skills/context-builder and .opencode/skills/context-builder in your project.

What does Context Builder need to run?

SKILL.md names no scripts, command-line tools or credentials: Context Builder is instructions for the agent only.

Does Context Builder access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Context Builder safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Context Builder use?

Context Builder is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Context Builder use?

About 850 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Context Builder?

Skills that share tags, products or a category with Context Builder: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Context Builder?

mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 5,542 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 7, 2026.

Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.