context-budget-audit

Audit prompt size distribution and directive coverage across orchestration phases.

9|4|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/learn-ukrainian/learn-ukrainian.github.io --skill context-budget-audit-learn-ukrainian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-budget-audit
Source: https://github.com/learn-ukrainian/learn-ukrainian.github.io/tree/main/claude_extensions/skills/context-budget-audit
Command: npx skills add https://github.com/learn-ukrainian/learn-ukrainian.github.io --skill context-budget-audit-learn-ukrainian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit prompt sizes across build orchestration dirs. Surfaces sections that dominate the prompt (>40%), tracks per-phase budget vs the model's context window, and checks whether directives in the prompt were actually covered in the response.

Core Features & Use Cases

  • Surface dominant prompt sections (>40%) to identify noise and opportunities for trimming.
  • Compare per-phase budgets against model context windows to detect overflow risks.
  • Validate directive coverage across phases and provide actionable guidance for prompt engineering.
  • Use Case: Debug a failing build by auditing the write and wiki sections and ensuring directives map to outputs.

Quick Start

Provide a track/slug path or a range to audit, and run the audit to generate a context-budget report.

Frequently Asked Questions about context-budget-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit prompt size distribution across build orchestration phases?

Prompt budget auditing tracks per-phase prompt sizes against the model's context window to detect overflow risks. It surfaces sections dominating the prompt over 40 percent and validates whether directives in the prompt were actually covered in the response.

How do I identify which prompt sections are dominating my context window budget?

Identify dominant prompt sections by running an audit that flags sections consuming over 40 percent of the prompt. The audit compares per-phase budgets against the model context window and highlights oversized sections suitable for trimming.

How do I check if directives in my build prompt are covered in the response?

Check directive coverage by applying the audit to targeted modules or ranges. The audit validates whether directives in the prompt were actually covered in the response and provides actionable guidance for prompt engineering.

Can I audit specific modules or ranges within a build orchestration track?

Yes, you can audit specific modules or ranges by providing a track and slug path. The audit applies to the targeted sections and returns metrics including per-phase budgets, oversized sections, directive coverage summaries, and context window headroom.

What is context window headroom and how do I calculate it for my prompts?

Context window headroom is the remaining capacity in the model's context window after accounting for prompt sizes. The audit calculates it by comparing per-phase prompt budgets against the model's context window and reports it in the structured metrics.

Why does my build prompt fail to map directives to outputs during orchestration?

Build prompts fail to map directives to outputs when directive coverage across phases is incomplete. Auditing the write and wiki sections identifies gaps where directives in the prompt were not actually covered in the response, providing guidance for prompt engineering.