Skip to main content
skill CX Codex

context-builder · glebis — Claude Code skill: generates AI discovery prompts

context-builder — a skill for Claude Code, Codex, Cursor and other platforms that generates interactive discovery prompts for AI transformation consulting.

MIT 226 installs ★ 414 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add glebis/claude-skills --skill context-builder -a claude-code
Open on GitHub

What context-builder does

Operates in five phases: first asks the consultant for the company name, industry, project focus (automation, existential strategy or new models), session language and whether any transcripts exist in the vault; searches the web for company data and analyzes call transcripts if found; offers a choice of questionnaire sections (from references/section-library.md) and Express mode grouping; generates a prompt in Claude-Drafts/{company-slug}-context-prompt.md with tailored questions, baked-in research and resumability logic; sends the file via Telegram or saves it to the vault.

The prompt the skill creates runs at the client's end: asks questions via AskUserQuestion, produces one file per section and a final CLAUDE.md. Express mode groups all sections into four blocks; Deep Dive goes through each separately. Questions can be in Russian, output files are always in English. Installation requires Node.js and access to npx; for platforms like GitHub Copilot, use gh skill install.

What it helps with

  • gather structured context about a client's business before AI consulting
  • generate a questionnaire with questions about processes, tech stack and pain points
  • automatically find client information on the web and in the vault before a meeting
  • create a resumable prompt that the client can fill out in parts
  • send a ready questionnaire to the client via Telegram in one command

Example prompts for the agent

  • Generate a context-builder prompt for Acme Corp, focus on operations automation
  • Run context-builder for a new SaaS startup client, there's a call transcript
  • Create an AI transformation questionnaire, questions in Russian, output in English

How to install context-builder

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/context-builder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/context-builder/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about context-builder

How to install context-builder in Claude Code?

Run npx skills add glebis/claude-skills --skill context-builder -a claude-code. The skill will appear at ~/.claude/skills/context-builder/SKILL.md.

What does context-builder do?

Generates discovery prompts for gathering client context in AI consulting. Searches for company data on the web and in the vault, offers section choices (processes, tech stack, pain points, AI opportunities), creates a prompt with questions and resumability logic. The prompt runs at the client's end and outputs section files.

Which sections can be included in the questionnaire?

Sections are stored in references/section-library.md. For automation, default sections include Process Inventory, Pain Points & Waste, Current Tech Stack, AI Opportunity Mapping, People & Org, Data Reality Check, Quick Wins. For strategy: Revenue & Service Map, The Existential Question, Client Value Chain, New Business Models, Data & Knowledge Assets. You can select all ten or customize manually.

Source text

SKILL.md · MIT
---
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:

1. **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

2. **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

3. **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:**
1. 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:**
1. 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.

### 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

© glebis · MIT · glebis/claude-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

context-builder by other authors comes first.

context-builder mvschwarz context-builder gathers feature background from meetings, competitor research, and regulations. Generates a concise background.md and updates shared team context. CX Codex +1 ★ 8,928repo stars ae-kb-discovery ThinkingAIAgenticEngine ae-kb-discovery evaluates accessible Agentic Engine knowledge bases and picks relevant sources for business context. Hands off retrieval to the companion skill. CX Codex +1 729installs bmad-project-context bmad-code-org bmad-project-context is a Claude Code skill that builds, audits, and maintains verified agent instructions in AGENTS.md. It records past agent mistakes as explicit pitfalls. CX Codex +1 17,200installs maintaining-agent-context sentimony maintaining-agent-context audits the instruction files a repo hands to coding agents, catching duplicates, contradictions and wasted always-loaded tokens. CX Codex +1 3,200installs domain-context ryan-price domain-context maintains a domain knowledge base in .tasks/domain.md across sessions. Tracks internal terms, entity relationships, and core business rules. CX Codex +1 2,700installs wiki-context-pack Ar9av wiki-context-pack — a skill for Claude Code, Codex, Cursor, GitHub Copilot and Gemini CLI that cuts a token-bounded, citation-ready slice from an Obsidian vault and hands it to a downstream agent. Works by topic or by recent notes. CX Codex +1 1,700installs openspec-context-loading forztf The openspec-context-loading skill finds specs, active changes and requirements in a project and hands the agent a ready summary. Useful when you need to know what OpenSpec already describes. CX Codex +1 1,100installs

From the same set51

The whole set →
llm-cli Skill to process text and files through the llm CLI, supporting OpenAI, Anthropic, Google Gemini, and local Ollama models. Selects a model interactively, persists settings, and runs in chat or one-off mode. CX Codex +1 235installs granola Use this skill to retrieve Granola notes and transcripts, then save meeting notes to Obsidian. It suits workflows that need searchable records or follow-up analysis. CX Codex +1 234installs chrome-history chrome-history is a Claude Code skill that searches Chrome history in natural language and filters results by date, content type, and keywords. CX Codex +1 234installs meta Registers a /meta handler to run Claude Code Agent SDK sessions inside the telegram_agent directory and edit the bot from chat. CX Codex +1 228installs wispr-analytics wispr-analytics connects to your local Wispr Flow database to review voice dictation trends, track speech prosody, and manage custom dictionaries. CX Codex +1 218installs nano-banana The nano-banana skill generates and edits images with Gemini models, using style presets, reference images, variants, and platform sizes. Use it for thumbnails, slides, or article artwork. CX Codex +1 216installs gpt-image-2 Guides image generation through OpenAI's GPT Image 2 API using structured style presets, cost-saving drafts, and automated prompt validation. CX Codex +1 213installs tufte-report tufte-report is a Claude Code skill that builds HTML reports with interactive charts and tables in Edward Tufte’s style, for presenting data with minimal decoration. CX Codex +1 202installs

Project sponsors

Companies that keep this analytics open