Mmcp.market

context-management skill

by a5c-ai·a5c-ai/babysitter·1.8k stars·MIT

No description in the SKILL.md.

A94/100content scan

Is the context-management skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

  • lowSKILL.md:1

    The name should be 1 to 64 lowercase letters, digits or hyphens.

    (missing)
  • lowSKILL.md:1

    No description, so an agent cannot tell when to use the skill.

    (missing)

Install the context-management skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/a5c-ai/babysitter.git /tmp/babysitter
mkdir -p ~/.claude/skills
cp -r /tmp/babysitter/library/methodologies/ccpm/skills/context-management ~/.claude/skills/context-management
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Context Management

Project context loading, isolation, and persistent state management across CCPM sessions.

Capabilities

  • Load project context from .claude/ directory structure
  • Maintain persistent context across sessions (PRD, epic, task states)
  • Isolate agent contexts per work stream
  • Context handoff between phases
  • Session state recovery

Context Sources

.claude/
  prds/              # PRD documents
  epics/             # Epic and task documents
  agents/            # Agent definitions
  context/           # Project-wide context
  commands/          # Command definitions
  rules/             # Reference rules

Context Flow

  1. Phase 1 (PRD): Loads project description, creates PRD context
  2. Phase 2 (Epic): Loads PRD, creates architecture context
  3. Phase 3 (Tasks): Loads PRD + Epic, creates task context
  4. Phase 4 (Sync): Loads all artifacts, syncs to GitHub
  5. Phase 5 (Exec): Loads stream-specific context per agent

Isolation

Each parallel agent receives only the context relevant to its stream, preventing context pollution and keeping agents focused.

More skills from a5c-ai/babysitter

  • Aadversarial-reviewFresh adversarial code review with binary PASS/FAIL verdicts, evidence citations, and anchoring bias prevention via fresh reviewer spawning.
  • Aagent-boosterWASM-based instant code transforms for simple tasks, achieving 352x speedup over LLM inference with zero cost.
  • Aagent-coordinationCoordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
  • Aagent-dispatch
  • Aanti-driftHierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.
  • Aarchitecture-design
  • Aarchitecture-patternsSystem and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
  • Aassimilate-popular-workflowsThis skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
  • Aaudit-trail
  • AbabysitOrchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
  • Ababysit-babysitter-issuesThis skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
  • Abehavior-contractBug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.

All agent skills → · MCP servers