
Context Engineering Collection
Install this bundle when you need production-grade context and harness patterns for Claude Code, Cursor, or Codex agents—not one-off prompts.
Overview
Context Engineering Collection is a journey-wide agent skill marketplace that packages context and harness engineering sub-skills plus a file-based research-to-skill operating system—usable whenever a solo builder needs
Install
npx skills add https://github.com/muratcankoylan/agent-skills-for-context-engineering --skill context-engineering-collectionWhat is this skill?
- Bundled context-engineering and harness-engineering skills covering fundamentals, degradation, compression, optimization
- File-based autonomous research-to-skill operating system with rubrics, mechanism registry, claim provenance, and run sta
- Measured router-benchmark results across four frontier models for skill routing decisions
- Sub-skills for memory systems, filesystem context, hosted agents, evaluation, advanced evaluation, and latent briefing (
- Marketplace plugin layout (v2.3.0) with strict mode off for flexible composition in agent workflows
- Marketplace metadata version 2.3.0
- Router-benchmark measurements reported across four frontier models
- 12+ bundled context-engineering sub-skills in the marketplace plugin list
Adoption & trust: 2.2k installs on skills.sh; 16.4k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent works in demos but loses thread, misuses tools, or burns tokens because context windows, memory, and harness rules were never engineered as a system.
Who is it for?
Solo and indie builders building or operating multi-step coding agents who want named procedures for context degradation, compression, memory, tools, and evaluation instead of improvised system prompts.
Skip if: Builders who only need a single integration skill for one API, or teams that already maintain a locked internal harness spec and do not want to adopt an external skill marketplace layout.
When should I use this skill?
You are designing or hardening production AI agent systems and need systematic context fundamentals, degradation handling, compression, multi-agent coordination, memory, tool design, evaluation, or the bundled research-t
What do I get? / Deliverables
You adopt a structured skill library and operating-system patterns for context lifecycle, multi-agent coordination, and evaluation so agent runs stay attributable, compressible, and improvable across projects.
- Composable context-engineering sub-skills wired into your agent plugin layout
- Harness-oriented workflows for evaluation, mechanism registry, and claim provenance when using the research operating sy
- Router-benchmark-informed model routing decisions for skill selection
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Compare router-benchmark results across four frontier models before locking a default model for your agent harness.
Install sub-skills for tool design and filesystem context when structuring what the agent can read and write each turn.
Run advanced-evaluation and adversarial benchmark flows from the collection before merging agent workflow changes.
Apply context-degradation and compression skills when production sessions drift or token costs spike.
Use memory-systems patterns so recurring user issues surface as durable agent-accessible context without stuffing the whole ticket history into every prompt.
How it compares
Use this as a coordinated skill package and harness methodology—not a lone MCP connector or a generic productivity checklist.
Common Questions / FAQ
Who is context-engineering-collection for?
It is for solo and indie developers who ship with agentic IDEs and need production-grade context engineering: window management, memory, tools, multi-agent patterns, and evaluation—not casual chat-only coding.
When should I use context-engineering-collection?
Use it during Build when wiring agent-tooling and skills; during Ship when reviewing harness quality and evals; during Operate when debugging context degradation and monitoring agent behavior; and during Validate when you need measured router benchmarks before picking a model rou
Is context-engineering-collection safe to install?
Treat it like any third-party skill bundle: review the Security Audits panel on this Prism page, inspect sub-skill permissions (filesystem, network, shell) before enabling autonomous runs, and run eval harnesses in a sandbox repo first.
SKILL.md
READMESKILL.md - Context Engineering Collection
{ "name": "context-engineering-marketplace", "owner": { "name": "Muratcan Koylan", "email": "muratcan.koylan@outlook.com" }, "metadata": { "description": "Context engineering and harness engineering skills plus a file-based autonomous research-to-skill operating system with measured router-benchmark results across four frontier models", "version": "2.3.0" }, "plugins": [ { "name": "context-engineering", "description": "Comprehensive context engineering and harness engineering skills for production-grade AI agent systems: fundamentals, degradation patterns, compression, optimization, multi-agent coordination, memory systems, tool design, filesystem context, hosted agents, evaluation, autonomous harnesses, latent briefing (KV cache sharing between agents), project development, and cognitive architecture. Ships with a researcher operating system (rubrics, mechanism registry, claim provenance, run state machine, adversarial benchmarks, continuous loop).", "source": "./", "strict": false, "skills": [ "./skills/context-fundamentals", "./skills/context-degradation", "./skills/context-compression", "./skills/context-optimization", "./skills/multi-agent-patterns", "./skills/memory-systems", "./skills/tool-design", "./skills/filesystem-context", "./skills/hosted-agents", "./skills/evaluation", "./skills/advanced-evaluation", "./skills/harness-engineering", "./skills/project-development", "./skills/bdi-mental-states", "./skills/latent-briefing" ] } ] } { "name": "context-engineering", "description": "Context engineering and harness engineering skills for production-grade AI agent systems: fundamentals, degradation patterns, compression, optimization, latent briefing (KV cache sharing between agents), multi-agent coordination, memory systems, tool design, evaluation, autonomous harnesses, and a file-based researcher operating system with deterministic gates, a continuous loop, and measured router-benchmark results across four frontier models.", "version": "2.3.0", "author": { "name": "Muratcan Koylan" } } # Don't index SpecStory auto-save files, but allow explicit context inclusion via @ references .specstory/** --- name: context-engineering-collection description: A comprehensive collection of Agent Skills for context engineering, harness engineering, multi-agent architectures, and production agent systems. Use when building, optimizing, evaluating, or debugging agent systems that require effective context management and reliable operating loops. --- # Agent Skills for Context Engineering This collection provides structured guidance for building production-grade AI agent systems through effective context engineering. ## When to Activate Activate these skills when: - Building new agent systems from scratch - Optimizing existing agent performance - Debugging context-related failures - Designing multi-agent architectures - Creating or evaluating tools for agents - Implementing memory and persistence layers - Designing autonomous research or evaluation harnesses ## Skill Map ### Foundational Context Engineering **Understanding Context Fundamentals** Context is not just prompt text—it is the complete state available to the language model at inference time, including system instructions, tool definitions, retrieved documents, message history, and tool outputs. Effective context engineering means understanding what information truly matters for the task at hand and curating that information for maximum signal-to-noise ratio. **Recognizing Context Degradation** Language models exhibit predictable degradation patterns as context grows: the "lost-in-middle" phenomenon where information in the center of context receives less attention; U-shaped attention curves that prioritize beginning and end; context poisoning when errors comp