Agent skill

Context Builder

Generate interactive AI transformation context-builder prompts for consulting clients.

MITAuto-check passed

Install Context Builder

skills CLI

$ npx skills add glebis/claude-skills --skill context-builder -a claude-code

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

GitHub CLI

$ gh skill install glebis/claude-skills 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/glebis/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/

Paste into Claude Code

Install the "context-builder" agent skill from https://github.com/glebis/claude-skills/tree/main/context-builder into .claude/skills/context-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-builder", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/glebis/claude-skills/tree/main/context-builder

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add glebis/claude-skills --skill context-builder -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills context-builder --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/context-builder .agents/skills/context-builder && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "context-builder" agent skill from https://github.com/glebis/claude-skills/tree/main/context-builder into .agents/skills/context-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-builder", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add glebis/claude-skills --skill context-builder -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills context-builder --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/context-builder .cursor/skills/context-builder && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "context-builder" agent skill from https://github.com/glebis/claude-skills/tree/main/context-builder into .cursor/skills/context-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-builder", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/glebis/claude-skills.git --path context-builder

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add glebis/claude-skills --skill context-builder -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills context-builder --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/context-builder .gemini/skills/context-builder && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "context-builder" agent skill from https://github.com/glebis/claude-skills/tree/main/context-builder into .gemini/skills/context-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-builder", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install glebis/claude-skills context-builder

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add glebis/claude-skills --skill context-builder -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/context-builder .github/skills/context-builder && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "context-builder" agent skill from https://github.com/glebis/claude-skills/tree/main/context-builder into .github/skills/context-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-builder", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add glebis/claude-skills --skill context-builder -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills context-builder --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/context-builder .opencode/skills/context-builder && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "context-builder" agent skill from https://github.com/glebis/claude-skills/tree/main/context-builder into .opencode/skills/context-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "context-builder", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: context-builder
GitHub stars: 388
Token cost: ~1.6k tokens
SKILL.md length: 679 words
Files: 5 (incl. references)
Skills in repo: 91
Repo updated: Sep 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Generate interactive AI transformation context-builder prompts for consulting clients.

Works in 5 steps: Intake (AskUserQuestion) → Research (automated) → Section Selection (AskUserQuestion) → …
Creating structured discovery session prompts that guide a company through context gathering about their business
SKILL.md covers Workflow, Key Principles and Resources
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Context Builder is an agent skill from glebis/claude-skills. Generate interactive AI transformation context-builder prompts for consulting clients. Use when creating structured discovery session prompts that guide a company through context gathering about their business, pain points, tech stack, and AI opportunities. Produces a resumable, multi-section prompt with Express/Deep Dive modes.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `.claude-plugin/plugin.json`, `references/frameworks.md` and `references/prompt-template.md`).

The repository describes itself as: Collection of Claude Code skills for enhanced AI workflows. The licence is MIT.

When your agent uses it

Creating structured discovery session prompts that guide a company through context gathering about their business
AI opportunities

Example prompts

“/context-builder”

Workflow steps

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

Intake (AskUserQuestion)
Research (automated)
Section Selection (AskUserQuestion)
Generation
Delivery (AskUserQuestion)

What it can do on your machine

Read from SKILL.md and the folder at commit 7524dff. 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.
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 1.6k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 679 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~87
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~6.5k

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 glebis/claude-skills at commit 7524dff, republished under its MIT licence (© glebis). 679 words, ~1,592 tokens.

Download SKILL.mdSave it as .claude/skills/context-builder/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: context-builder
description: Generate interactive AI transformation context-builder prompts for consulting clients. Use when creating structured discovery session prompts that guide a company through context gathering about their business, pain points, tech stack, and AI opportunities. Produces a resumable, multi-section prompt with Express/Deep Dive modes.

Context Builder

Generate interactive context-building prompts for consulting clients. These prompts are designed to be run in Claude Code -- they guide a team through structured questions using AskUserQuestion, generate output files per section, and compile everything into a reusable CLAUDE.md.

Workflow

Phase 1: Intake (AskUserQuestion)

Ask all intake questions using AskUserQuestion with closed-list options. Gather:

Question 1: Company identifier

Options: "I have a website URL", "I have a company name", "I have both"
Follow up to get the actual URL/name

Question 2: Who will use this prompt?

Options: "Specific person (name + role)", "A team (no specific person)", "Unknown / TBD"
If specific person: follow up for name and role

Question 3: Primary consulting focus (multiSelect)

"AI automation of current operations"
"Existential strategy (what survives AI)"
"New business models / pivots"
"Product development with AI"

Question 4: Industry

"Marketing / Advertising"
"Manufacturing / Construction"
"SaaS / Software"
"Professional Services / Consulting"
(Other)

Question 5: Existing context in vault?

"Yes, there's a call transcript"
"Yes, there are notes/files"
"No existing context"
If yes: ask for filename or search term to locate it

Question 6: Session language

"Russian (questions in Russian, output in English)"
"English throughout"
"Other"

Phase 2: Research (automated)

Run these research steps in parallel where possible:

Web research: Use WebSearch and WebFetch (via Task agent) to gather:
- What the company does, products/services
- Target market, company size, geography
- Tech stack, partnerships
- Recent news, funding, team info
- Competitive landscape
Vault search: Search the Obsidian vault for:
- Transcripts mentioning the company name (Grep in vault root and Daily/)
- People files for contacts at the company (People/ folder)
- Any existing notes or research
Transcript analysis (if found): Extract from call transcripts:
- Team members and their roles
- Current AI tool usage
- Pain points and concerns mentioned
- Specific processes described
- Questions raised by the team

Phase 3: Section Selection (AskUserQuestion)

Present a curated set of sections based on the consulting focus. Use AskUserQuestion with multiSelect to let the user pick which sections to include.

Section Library

Draw from references/section-library.md for the full section catalog. Default section sets by focus:

AI Automation focus:

Process Inventory, 2. Pain Points & Waste, 3. Current Tech Stack, 4. AI Opportunity Mapping, 5. People & Org, 6. Data Reality Check, 7. Quick Wins

Existential Strategy focus:

Revenue & Service Map, 2. The Existential Question, 3. Client Value Chain, 4. New Business Models, 5. Data & Knowledge Assets, 6. People & Org, 7. Quick Wins & Pilots

Full Assessment (both): All 10 sections from the library.

After section selection, ask:

Express mode grouping: Present a suggested grouping of selected sections into 4 Express mega-sections. Let user confirm or adjust.

Show full SKILL.md (249 more words)Show less

Phase 4: Generation

Generate two files:

1. The Context-Builder Prompt

Save to: Claude-Drafts/{company-slug}-context-prompt.md

Structure (follow the template in references/prompt-template.md):

---
created_date: '[[YYYYMMDD]]'
type: draft
topic: consulting, AI transformation, {industry}
for: {contact person or team name}
---

# AI Transformation Context Builder -- {Company Name}

## About {Company}
  [Generated from research -- company description, size, market, positioning]

## Current State
  **What's working:** [from research + transcript]
  **The gap:** [from research + transcript]
  [If existential concerns found: **Existential context:**]

## Mode Selection
  [Express vs Deep Dive with section descriptions]

## How This Works
  [Standard interactive session instructions]

## Session Resumability
  [Standard resumability logic]

## Interactive Flow
  [Selected sections with tailored questions]

## Output Files
  [One file per section + final CLAUDE.md]

## Relevant Frameworks
  [Selected from references/frameworks.md based on focus]

2. Instruction File (optional)

If the prompt will be sent to someone external, generate a short instruction file: Claude-Drafts/{company-slug}-context-instructions.md

Containing:

What this file is and how to use it
Prerequisites (Claude Code or similar)
The two modes explained simply
What they'll get on output
Privacy note (they can share as much or as little as they want)

Phase 5: Delivery (AskUserQuestion)

Question: What to do with the generated files?

"Save to vault only"
"Save and send via Telegram"
"Save and let me review first"

If Telegram: ask for the recipient handle/name, then send using the telegram skill (intro message + file).

Key Principles

Maximize closed-list questions: Every AskUserQuestion should have concrete options. Minimize free-text input.
Research before asking: Don't ask the user things that can be found via web search or vault search.
Tailor sections to context: If the transcript reveals specific concerns (e.g., existential fears, specific tech stack), customize the section questions to reference those specifics.
Bake in discovered context: The generated prompt's "About" and "Current State" sections should be rich with researched details so the person running the prompt gets a warm start.
Language awareness: If session language is Russian, all AskUserQuestion interactions during prompt execution should be in Russian, but output files in English.

Resources

references/

section-library.md -- Full catalog of available sections with question templates
prompt-template.md -- Structural template for the generated prompt
frameworks.md -- Consulting frameworks to selectively include

Files

SKILL.md and 4 other files (references) in context-builder of glebis/claude-skills.

SKILL.md
.claude-plugin/plugin.json
references/frameworks.md
references/prompt-template.md
references/section-library.md

Open the folder on GitHubat commit 7524dff

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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Context Builder this skillglebis/claude-skills	388	—	~1.6k	Automated safety check: Pass	MIT	11 days ago
TransformersK-Dense-AI/scientific-agent-skills	48k	1 repos	~2.8k	Automated safety check: Notes	Apache-2.0	2 days ago
Team Builderaffaan-m/ECC	274k	1 repos	~1.8k	Automated safety check: Pass	MIT	2 days ago
Remotion Interactivityremotion-dev/remotion	62k	5 repos	~4.7k	Automated safety check: Pass	Custom licence	today
Firecrawl Interact Integrationfirecrawl/firecrawl	189k	1 repos	~731	Automated safety check: Pass	ISC	today
Hugging Face Transformers Usagedavila7/claude-code-templates	32k	12 repos	~1.2k	Automated safety check: Pass	MIT	today

Similar skills

Transformers
K-Dense-AI/scientific-agent-skills
Hugging Face Transformers for loading Hub models, running pipeline inference, text generation, and Trainer fine-tuning on NLP, vision, audio, and multimodal tasks.
48k GitHub starsUsed in 1 repo~2.8k tokens
AI & LLM EngineeringAuto-check: notes
Team Builder
affaan-m/ECC
Interactive picker that discovers available agent personas via the claude agents command and agents/ markdown globs, groups them into domains, has the user select up to five, dispatches them in…
274k GitHub starsUsed in 1 repo~1.8k tokens
Agent WorkflowsAuto-check passed
Remotion Interactivity
remotion-dev/remotion
Official
Structure Remotion markup for interactivity. An agent skill from remotion-dev/remotion.
62k GitHub starsUsed in 5 repos~4.7k tokens
Media & CreativeAuto-check passed
Firecrawl Interact Integration
firecrawl/firecrawl
Guides adding Firecrawl's /interact endpoint to product code for pages that need clicks, forms, pagination or logged-in flows beyond plain scraping.
189k GitHub starsUsed in 1 repo~731 tokens
Data & AnalyticsAuto-check passed
Hugging Face Transformers Usage
davila7/claude-code-templates
Loads pre-trained Hugging Face Transformers models for text, vision and audio tasks, runs inference with pipelines and fine-tunes on custom datasets.
32k GitHub starsUsed in 12 repos~1.2k tokens
AI & LLM EngineeringAuto-check passed
Team Builder
affaan-m/ECC
用于组合和派遣并行团队的交互式代理选择器
274k GitHub starsUsed in 1 repo~808 tokens
Auto-check passed

More from glebis/claude-skills

All 91 skills in this repo

PII Annotation and Agreement Scorer
glebis/claude-skills
Runs a human-first workflow for labeling PII spans in a transcript, then scores inter-annotator agreement and drafts an adjudicated gold set.
388 GitHub stars~1.3k tokensUpdated 11 days ago
Auto-check passed
Non-Destructive Chrome Automation
glebis/claude-skills
Automates a dedicated, logged-in Chrome instance per profile without ever closing the user's own open tabs or browser windows.
388 GitHub stars~973 tokensUpdated 11 days ago
Auto-check passed
Deep Research
glebis/claude-skills
This skill should be used when conducting comprehensive research on any topic using the OpenAI Deep Research API.
388 GitHub stars~2.6k tokensUpdated 11 days ago
Auto-check: notes
Elimination Research
glebis/claude-skills
This skill should be used for elimination-style research where the user wants to choose from a shortlist of products, tools, services, vendors, or other options using explicit criteria, numeric…
388 GitHub stars~1.6k tokensUpdated 11 days ago
Auto-check passed
Narrated HTML Presentations
glebis/claude-skills
Generates a self-contained HTML presentation with article and slides modes, ElevenLabs voiceover narration and optional GPT Image 2 illustrations.
388 GitHub stars~2.3k tokensUpdated 11 days ago
Auto-check: notes
Synthetic Coaching Session Generator
glebis/claude-skills
Writes fictional but realistic coaching or therapy session transcripts for evals, demos and few-shot examples, in several modalities and export formats.
388 GitHub stars~2.9k tokensUpdated 11 days ago
Auto-check passed

Questions about Context Builder

What does Context Builder do?

Generate interactive AI transformation context-builder prompts for consulting clients. Context Builder is an agent skill from glebis/claude-skills. Generate interactive AI transformation context-builder prompts for consulting clients.

When should I use Context Builder?

Context Builder fits situations like: creating structured discovery session prompts that guide a company through context gathering about their business; AI opportunities.

How do I install Context Builder in Claude Code?

Run `npx skills add glebis/claude-skills --skill context-builder -a claude-code`. Or copy the skill folder (context-builder in glebis/claude-skills) 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 glebis/claude-skills --skill context-builder -a codex`. Or copy the skill folder (context-builder in glebis/claude-skills) 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 glebis/claude-skills --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 MIT 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 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.9k tokens, read only when the agent opens those files.

What are the alternatives to Context Builder?

Skills that share tags, products or a category with Context Builder: Transformers (K-Dense-AI/scientific-agent-skills, 48k stars), Team Builder (affaan-m/ECC, 274k stars), Remotion Interactivity (remotion-dev/remotion, 62k stars) and Firecrawl Interact Integration (firecrawl/firecrawl, 189k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Context Builder?

glebis (a GitHub user) maintains it in glebis/claude-skills, which has 388 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on September 26, 2026.

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

Install Context Builder

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Context Builder

Workflow

Phase 1: Intake (AskUserQuestion)

Phase 2: Research (automated)

Phase 3: Section Selection (AskUserQuestion)

Section Library

Phase 4: Generation

1. The Context-Builder Prompt

2. Instruction File (optional)

Phase 5: Delivery (AskUserQuestion)

Key Principles

Resources

references/

Files

Compare with similar skills

Similar skills

More from glebis/claude-skills

Questions about Context Builder