SkillAgentSearch skills...

context-engineering-advisor

Diagnose context stuffing vs. context engineering

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill context-engineering-advisor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Category

Automation

Supported Platforms

Universal

Our assessment of context-engineering-advisor

context-engineering-advisor scores 88/100 on our quality scale, 1493rd of 2,780 Automation skills we index.

Its SKILL.md is 32 KB long, well organised into 45 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
18/20
Description
8/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so context-engineering-advisor is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

context-engineering-advisor compared with similar skills

All 4 of these similar skills score higher than context-engineering-advisor; compare them before choosing.

SkillScoreStarsUpdatedFormat
context-engineering-advisor (this skill)by deanpeters887.1k3mo agoSKILL.md
Agent-Reachby Panniantong100112.3k9d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install context-engineering-advisor?
Run npx skills add deanpeters/Product-Manager-Skills --skill context-engineering-advisor. The install tabs above show the steps for each supported agent.
Which AI agents does context-engineering-advisor work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is context-engineering-advisor safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is context-engineering-advisor still maintained?
The repository was last updated about 3 months ago, so context-engineering-advisor is actively maintained.

name: context-engineering-advisor argument-hint: "[AI workflow to diagnose]" description: Diagnose context stuffing vs. context engineering. Use when an AI workflow feels bloated, brittle, or hard to steer reliably. intent: >- Guide product managers through diagnosing whether they're doing context stuffing (jamming volume without intent) or context engineering (shaping structure for attention). Use this to identify context boundaries, fix "Context Hoarding Disorder," and implement tactical practices like bounded domains, episodic retrieval, and the Research→Plan→Reset→Implement cycle. type: interactive theme: ai-agents best_for:

  • "Diagnosing context stuffing vs. context engineering in your AI workflows"
  • "Building better memory and retrieval architecture for AI agents"
  • "Improving AI output quality through structured context design" scenarios:
  • "My AI outputs are mediocre even though I'm giving it lots of information — diagnose what's wrong"
  • "I want to architect context properly for a multi-step AI workflow in my product team" estimated_time: "15-20 min"

Purpose

Guide product managers through diagnosing whether they're doing context stuffing (jamming volume without intent) or context engineering (shaping structure for attention). Use this to identify context boundaries, fix "Context Hoarding Disorder," and implement tactical practices like bounded domains, episodic retrieval, and the Research→Plan→Reset→Implement cycle.

Key Distinction: Context stuffing assumes volume = quality ("paste the entire PRD"). Context engineering treats AI attention as a scarce resource and allocates it deliberately.

This is not about prompt writing—it's about designing the information architecture that grounds AI in reality without overwhelming it with noise.

Input

Works best with: A description of the AI workflow, agent, or prompt setup that feels bloated, brittle, or hard to steer. Also useful: What you've already stuffed into context (docs, transcripts, schemas) and where outputs go wrong.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. The advisor opens by asking what you're feeding the model today and what breaks.

Example invocation: Diagnose my setup: our support-triage agent gets the full 40-page policy manual per ticket and still misroutes edge cases.

Key Concepts

The Paradigm Shift: Parametric → Contextual Intelligence

The Fundamental Problem:

  • LLMs have parametric knowledge (encoded during training) = static, outdated, non-attributable
  • When asked about proprietary data, real-time info, or user preferences → forced to hallucinate or admit ignorance
  • Context engineering bridges the gap between static training and dynamic reality

PM's Role Shift: From feature builder → architect of informational ecosystems that ground AI in reality


Context Stuffing vs. Context Engineering

| Dimension | Context Stuffing | Context Engineering | |-----------|------------------|---------------------| | Mindset | Volume = quality | Structure = quality | | Approach | "Add everything just in case" | "What decision am I making?" | | Persistence | Persist all context | Retrieve with intent | | Agent Chains | Share everything between agents | Bounded context per agent | | Failure Response | Retry until it works | Fix the structure | | Economic Model | Context as storage | Context as attention (scarce resource) |

Critical Metaphor: Context stuffing is like bringing your entire file cabinet to a meeting. Context engineering is bringing only the 3 documents relevant to today's decision.


The Anti-Pattern: Context Stuffing

Five Markers of Context Stuffing:

  1. Reflexively expanding context windows — "Just add more tokens!"
  2. Persisting everything "just in case" — No clear retention criteria
  3. Chaining agents without boundaries — Agent A passes everything to Agent B to Agent C
  4. Adding evaluations to mask inconsistency — "We'll just retry until it's right"
  5. Normalized retries — "It works if you run it 3 times" becomes acceptable

Why It Fails:

  • Reasoning Noise: Thousands of irrelevant files compete for attention, degrading multi-hop logic
  • Context Rot: Dead ends, past errors, irrelevant data accumulate → goal drift
  • Lost in the Middle: Models prioritize beginning (primacy) and end (recency), ignore middle
  • Economic Waste: Every query becomes expensive without accuracy gains
  • Quantitative Degradation: Accuracy drops below 20% when context exceeds ~32k tokens

The Hidden Costs:

  • Escalating token consumption
  • Diluted attention across irrelevant material
  • Reduced output confidence
  • Cascading retries that waste time and money

Real Context Engineering: Core Principles

Five Foundational Principles:

  1. Context without shape becomes noise
  2. Structure > Volume
  3. Retrieve with intent, not completeness
  4. Small working contexts (like short-term memory)
  5. Context Compaction: Maximize density of relevant information per token

Quantitative Framework:

Efficiency = (Accuracy × Coherence) / (Tokens × Latency)

Key Finding: Using RAG with 25% of available tokens preserves 95% accuracy while significantly reducing latency and cost.


The 5 Diagnostic Questions (Detect Context Hoarding Disorder)

Ask these to identify context stuffing:

  1. What specific decision does this support? — If you can't answer, you don't need it
  2. Can retrieval replace persistence? — Just-in-time beats always-available
  3. Who owns the context boundary? — If no one, it'll grow forever
  4. What fails if we exclude this? — If nothing breaks, delete it
  5. Are we fixing structure or avoiding it? — Stuffing context often masks bad information architecture

Memory Architecture: Two-Layer System

Short-Term (Conversational) Memory:

  • Immediate interaction history for follow-up questions
  • Challenge: Space management → older parts summarized or truncated
  • Lifespan: Single session

Long-Term (Persistent) Memory:

  • User preferences, key facts across sessions → deep personalization
  • Implemented via vector database (semantic retrieval)
  • Two types:
    • Declarative Memory: Facts ("I'm vegan")
    • Procedural Memory: Behavioral patterns ("I debug by checking logs first")
  • Lifespan: Persistent across sessions

LLM-Powered ETL: Models generate their own memories by identifying signals, consolidating with existing data, updating database automatically.


The Research → Plan → Reset → Implement Cycle

The Context Rot Solution:

  1. Research: Agent gathers data → large, chaotic context window (noise + dead ends)
  2. Plan: Agent synthesizes into high-density SPEC.md or PLAN.md (Source of Truth)
  3. Reset: Clear entire context window (prevents context rot)
  4. Implement: Fresh session using only the high-density plan as context

Why This Works: Context rot is eliminated; agent starts clean with compressed, high-signal context.


Anti-Patterns (What This Is NOT)

  • Not about choosing AI tools — Claude vs. ChatGPT doesn't matter; architecture matters
  • Not about writing better prompts — This is systems design, not copywriting
  • Not about adding more tokens — "Infinite context" narratives are marketing, not engineering reality
  • Not about replacing human judgment — Context engineering amplifies judgment, doesn't eliminate it

When to Use This Skill

✅ Use this when:

  • You're pasting entire PRDs/codebases into AI and getting vague responses
  • AI outputs are inconsistent ("works sometimes, not others")
  • You're burning tokens without seeing accuracy improvements
  • You suspect you're "context stuffing" but don't know how to fix it
  • You need to design context architecture for an AI product feature

❌ Don't use this when:

  • You're just getting started with AI (start with basic prompts first)
  • You're looking for tool recommendations (this is about architecture, not tooling)
  • Your AI usage is working well (if it ain't broke, don't fix it)

Facilitation Source of Truth

Use workshop-facilitation as the default interaction protocol for this skill.

It defines:

  • session heads-up + entry mode (Guided, Context dump, Best guess)
  • one-question turns with plain-language prompts
  • progress labels (for example, Context Qx/8 and Scoring Qx/5)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include Other (specify) when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

Application

This interactive skill uses adaptive questioning to diagnose context stuffing, identify boundaries, and provide tactical implementation guidance.


Step 0: Gather Context

Agent asks:

Before we diagnose your context practices, let's gather information:

Current AI Usage:

  • What AI tools/systems do you use? (ChatGPT, Claude, custom agents, etc.)
  • What PM tasks do you use AI for? (PRD writing, user research synthesis, discovery, etc.)
  • How do you provide context? (paste docs, reference files, use projects/memory)

Symptoms:

  • Are AI outputs inconsistent? (works sometimes, not others)
  • Are you retrying prompts multiple times to get good results?
  • Are responses vague or hedged despite providing "all the context"?
  • Are token costs escalating without accuracy improvements?

System Architecture (if applicable):

  • Do you have custom AI agents or workflows?
  • How is context shared between agents?
  • Do you use RAG, vector databases, or memory systems?

You can describe briefly or paste examples.


Step 1: Diagnose Context Stuffing Symptoms

Agent asks:

Let's assess whether you're experiencing context stuffing. Which of these symptoms do you recognize?

Select all that apply:

  1. "I paste entire documents into AI" — Full PRDs, complete user interview transcripts, entire codebases
  2. "AI gives vague, hedged responses despite having 'all the context'" — Responses like "it depends," "consider these options," non-committal
  3. "I have to retry prompts 3+ times to get usable output" — Inconsistency is normalized
  4. "Token costs are escalating but accuracy isn't improving" — Spending more, getting same or worse results
  5. "I keep adding more context hoping it'll help" — Reflexive expansion without strategy
  6. "My agents pass everything to each other" — Agent A → Agent B → Agent C with full context chain
  7. "I don't have clear criteria for what to include/exclude" — No context boundary definitions
  8. "None of these—my AI usage is working well" — Skip to advanced optimization

User response: [Select symptoms]

Agent analyzes:

Based on your selections:

  • 0-1 symptoms: Healthy context practices; proceed to optimization
  • 2-3 symptoms: Early context stuffing; address before it scales
  • 4+ symptoms: Active Context Hoarding Disorder; immediate intervention needed

Agent proceeds to diagnostic questions.


Step 2: Diagnostic Question 1 — What Specific Decision Does This Support?

Agent asks:

Let's start with the most critical question: For each piece of context you're including, what specific decision does it support?

Example Context Analysis:

Imagine you're asking AI to "help with discovery planning." You're providing:

  • Entire PRD (20 pages)
  • 50 user interview transcripts (full)
  • Competitive analysis doc (15 pages)
  • Team meeting notes from last 3 months

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryAutomation
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium