How do I install the Assembling Context skill?

Run npx skillmds add majiayu000/assembling-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 Assembling Context safe to use?

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

Which AI agents work with Assembling 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 Assembling Context free to use?

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

Who published Assembling Context?

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

Assembling Context by majiayu000 — Agent Skill

Name: Assembling Context
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Assembling Context

Use when preparing context for subagents or managing token budgets. Triggers: "prepare context for", "assemble context", "what context does X need", "token budget", "context package", or automatically invoked by implementing-features Phase 3.5 (work packets) and Phase 4.2 (parallel subagents).

majiayu000 3b70249 2 files · 5.4 KB Updated Sep 9, 2026 567 repo stars

File contents

Context Assembly

Invariant Principles

Tier 1 Never Truncates: Essential context survives any budget pressure
Budget Before Assembly: Calculate budget FIRST, then select
Purpose Drives Selection: Design ≠ implementation ≠ review context
Recency Over Completeness: Recent feedback > historical context
Summarize, Don't Truncate: Intelligent summarization preserves signal
Integration Points are Tier 1: Interface contracts are essential

Inputs / Outputs

Input	Required	Description
`purpose`	Yes	`design`, `implementation`, `review`, `handoff`, `subagent`
`token_budget`	Yes	Maximum tokens available
`source_context`	Yes	Raw context to select from

Output	Type	Description
`context_package`	Structured	Tiered context ready for injection
`truncation_report`	Inline	What was excluded and why

Context Tiers

Over budget: remove Tier 3 first, then Tier 2. Never remove Tier 1.

Tier	Budget	Content	Examples
1: Essential	40-60%	Active instructions, user decisions, current artifact, interface contracts, blocking issues	Task spec, APIs, unresolved feedback
2: Supporting	20-35%	Recent learnings, patterns, prior feedback, success criteria	Last 2-3 iterations, codebase patterns
3: Reference	10-20%	Historical context, rejected alternatives, verbose docs	Early iterations, full docs (summarize instead)

Purpose-Specific Packages

Purpose	Tier 1 Focus	Budget Split	Use With
Design	Requirements, decisions, constraints, integration points	50/30/20	brainstorming, writing-plans
Implementation	Task spec, acceptance criteria, interfaces, test expectations	60/25/15	test-driven-development, executing-plans
Review	Code diff, requirements traced, test results	55/30/15	code-review, fact-checking
Handoff	Current position, pending work, active decisions, blocking issues	70/20/10	session boundaries, compaction
Subagent	Task, constraints, expected output format	65/25/10	dispatching-parallel-agents

Token Budget

Estimation: tokens ≈ chars / 4 (conservative)

Available budget: context_window - system_prompt - response_reserve - tool_overhead Example: 200000 - 8000 - 4000 - 2000 = 186000

Smart Truncation: Never blind head/tail. Preserve structure: keep intro (30%) + conclusion (20%), mark omitted middle.

Cross-Session Context

Action	Items
Persist	User decisions, validated assumptions, glossary, blocking issues
Regenerate	File contents, test results, code patterns (may have changed)
Discard	Exploration paths, rejected alternatives, verbose logs

Handoff format: Position → Pending work → Active decisions → Key learnings → Verification commands

Reasoning Schema

Self-Check

Calculated token budget explicitly
Identified Tier 1 for this purpose
Tier 1 fits within budget
Smart truncation applied (not blind)
Integration points included
Truncation report created

---name: assembling-contextdescription: Use when preparing context for subagents or managing token budgets. Triggers: "prepare context for", "assemble context", "what context does X need", "token budget", "context package", or automatically invoked by implementing-features Phase 3.5 (work packets) and Phase 4.2 (parallel subagents).--- # Context Assembly <ROLE> Context Curator. Deliver precisely the right information at the right time. Too little causes failures. Too much burns tokens and buries signal. Every token must earn its place. </ROLE> ## Invariant Principles 1. **Tier 1 Never Truncates**: Essential context survives any budget pressure 2. **Budget Before Assembly**: Calculate budget FIRST, then select 3. **Purpose Drives Selection**: Design ≠ implementation ≠ review context 4. **Recency Over Completeness**: Recent feedback > historical context 5. **Summarize, Don't Truncate**: Intelligent summarization preserves signal 6. **Integration Points are Tier 1**: Interface contracts are essential ## Inputs / Outputs | Input | Required | Description | |-------|----------|-------------| | `purpose` | Yes | `design`, `implementation`, `review`, `handoff`, `subagent` | | `token_budget` | Yes | Maximum tokens available | | `source_context` | Yes | Raw context to select from | | Output | Type | Description | |--------|------|-------------| | `context_package` | Structured | Tiered context ready for injection | | `truncation_report` | Inline | What was excluded and why | --- ## Context Tiers <CRITICAL>Over budget: remove Tier 3 first, then Tier 2. Never remove Tier 1.</CRITICAL> | Tier | Budget | Content | Examples | |------|--------|---------|----------| | **1: Essential** | 40-60% | Active instructions, user decisions, current artifact, interface contracts, blocking issues | Task spec, APIs, unresolved feedback | | **2: Supporting** | 20-35% | Recent learnings, patterns, prior feedback, success criteria | Last 2-3 iterations, codebase patterns | | **3: Reference** | 10-20% | Historical context, rejected alternatives, verbose docs | Early iterations, full docs (summarize instead) | --- ## Purpose-Specific Packages | Purpose | Tier 1 Focus | Budget Split | Use With | |---------|--------------|--------------|----------| | **Design** | Requirements, decisions, constraints, integration points | 50/30/20 | brainstorming, writing-plans | | **Implementation** | Task spec, acceptance criteria, interfaces, test expectations | 60/25/15 | test-driven-development, executing-plans | | **Review** | Code diff, requirements traced, test results | 55/30/15 | code-review, fact-checking | | **Handoff** | Current position, pending work, active decisions, blocking issues | 70/20/10 | session boundaries, compaction | | **Subagent** | Task, constraints, expected output format | 65/25/10 | dispatching-parallel-agents | --- ## Token Budget **Estimation:** `tokens ≈ chars / 4` (conservative) **Available budget:** `context_window - system_prompt - response_reserve - tool_overhead` Example: `200000 - 8000 - 4000 - 2000 = 186000` **Smart Truncation:** Never blind `head`/`tail`. Preserve structure: keep intro (30%) + conclusion (20%), mark omitted middle. --- ## Cross-Session Context | Action | Items | |--------|-------| | **Persist** | User decisions, validated assumptions, glossary, blocking issues | | **Regenerate** | File contents, test results, code patterns (may have changed) | | **Discard** | Exploration paths, rejected alternatives, verbose logs | **Handoff format:** Position → Pending work → Active decisions → Key learnings → Verification commands --- ## Reasoning Schema <analysis> Before assembling: PURPOSE? TOKEN BUDGET? TIER 1 for this purpose? RECIPIENT? </analysis> <reflection> After assembling: Tier 1 fits? Essential excluded? Room for Tier 2? Truncation report accurate? </reflection> --- <FORBIDDEN> - Assembling without calculating budget first - Blind truncation (`head`, `tail -n`, arbitrary limits) - Truncating Tier 1 to fit budget - Same package for different purposes - Omitting integration points - Including exploration paths in handoff - Persisting raw command output across sessions </FORBIDDEN> ## Self-Check - [ ] Calculated token budget explicitly - [ ] Identified Tier 1 for this purpose - [ ] Tier 1 fits within budget - [ ] Smart truncation applied (not blind) - [ ] Integration points included - [ ] Truncation report created <FINAL_EMPHASIS> Context assembly is invisible infrastructure. Calculate budget. Prioritize by tier. Truncate intelligently. Every token earns its place. </FINAL_EMPHASIS>

Frequently asked questions