cog-evolve

Audits memory system architecture and proposes rule changes without inspecting content.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/bketelsen/max --skill cog-evolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cog-evolve
Source: https://github.com/bketelsen/max/tree/main/skills/cog-evolve
Command: npx skills add https://github.com/bketelsen/max --skill cog-evolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill performs architecture-level self-evaluation of the memory subsystem and rule execution, identifying bottlenecks, drift, and opportunities to improve governance without touching memory content.

Core Features & Use Cases

  • Architecture review: analyzes the hot-memory → patterns → observations → glacier pipeline for coherence and stability.
  • Rule-change proposals: suggests governance adjustments to improve performance and safety without editing data.
  • Scope management: focuses on system-level organization when users request "evolve", "system audit", or "audit yourself".

Quick Start

To start an architecture audit, trigger the cog-evolve workflow with your system prompt by saying "evolve" to begin the assessment.

Frequently Asked Questions about cog-evolve

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

FAQPage Schema
How do I perform an architecture review of my memory system governance?

Trigger an architecture audit by saying "evolve" to begin the assessment. The system evaluates the hot-memory to glacier pipeline, proposes non-destructive rule changes, and records observations in memory meta files to improve governance.

What is rule drift in memory system architecture?

Rule drift occurs when memory system governance rules gradually deviate from their original design. An architecture audit identifies this drift by analyzing the hot-memory to glacier pipeline and proposing governance adjustments to restore stability without editing data.

How do I audit memory system rules without modifying stored content?

An architecture audit focuses on system-level organization rather than data inspection. It evaluates the hot-memory, patterns, observations, and glacier flow to propose non-destructive governance adjustments and route fixes to the appropriate skill.

When do I need to evolve my memory system rules?

You need to evolve memory system rules when you request an architecture review, system audit, or notice rule drift affecting the hot-memory to glacier pipeline. This indicates governance adjustments are needed to improve performance and safety without touching data.

Can I use an architecture audit to route fixes to other skills?

Yes, an architecture audit routes fixes to the appropriate skill rather than applying them directly. It performs a non-destructive analysis of the memory system, proposes governance rule changes, and records observations in memory meta files for downstream execution.