ck:context-engineering

Analyze LLM context token utilization and detect degradation or poisoning.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-context-engineering-nam3886
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:context-engineering
Source: https://github.com/nam3886/golang-echo-boilerplate/tree/main/.claude/skills/context-engineering
Command: npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-context-engineering-nam3886

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Identifies and remediate context-related failures in LLM workflows by measuring token utilization, detecting degradation and poisoning, and recommending compaction, masking, or partitioning so tasks remain accurate and cost-effective.

Core Features & Use Cases

  • Context health analysis: Estimate tokens, utilization, and generate a health score with actionable recommendations.
  • Degradation & poisoning detection: Find lost-in-middle issues and error-dense regions that harm reasoning.
  • Compression evaluation & probes: Generate probe sets and evaluate summaries to measure retention and continuity.
  • Runtime awareness: Integrate usage and context window monitoring to trigger warnings and compaction.
  • Multi-agent & memory guidance: Patterns and guidelines for isolating work across sub-agents and designing persistent memory.
  • Use Cases: Debugging agent failures, optimizing long-running sessions, reducing token costs, and designing robust memory systems.

Quick Start

Run the context analyzer on your session export to receive token utilization, health score, and recommended compaction actions.

Frequently Asked Questions about ck:context-engineering

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

FAQPage Schema
How do I optimize LLM context to reduce token consumption in multi-agent systems?▼

To optimize LLM context, analyze token utilization to detect degradation, then apply compaction, masking, or partitioning. This reduces token consumption while preventing reasoning degradation in long-running sessions and multi-agent coordination.

What causes lost-in-middle context degradation and how do I detect it?▼

Lost-in-middle degradation occurs when an LLM ignores central information in long inputs. Detect this issue and error-dense poisoning regions by running a context health analysis to generate a health score and actionable recommendations.

Can I evaluate context compression and summary retention using probes?▼

Yes, you can evaluate context compression by generating probe sets and evaluating summaries. This measures information retention and continuity, ensuring compaction strategies preserve critical reasoning details.

How do I design persistent memory layers for long-running agent sessions?▼

Design persistent memory layers by applying multi-agent and memory guidance patterns that isolate work across sub-agents. This maintains context health and prevents reasoning degradation during extended operational sessions.

When should I trigger context compaction to prevent agent failures?▼

Trigger context compaction when runtime awareness monitoring detects operational thresholds approaching context limits. This prevents agent failures by executing warnings and compaction actions before task quality degrades.