Skip to main content
plugin

adaptive-agent — Claude Code plugin: skills that improve with use

A Claude plugin that lets your agent learn from its own runs: skill audits, a user profile, and always-on rules in CLAUDE.md.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/claude-plugins-community
/plugin install adaptive-agent@claude-community
Open on GitHub

What adaptive-agent does

Two skills ship in the package. /skill-review walks through every skill you have, checks it against the agent's memory, and patches what went stale. /build-user-profile reads your workspace — git history, project layout, tech stack — and writes a profile to memory, so later sessions open with your role and preferences already known.

The third piece is behavioral rules. You paste the "Adaptive Behavior" section of CLAUDE.md into your project's CLAUDE.md, and from then on the agent edits a skill file when a step breaks on an API change, pulls known gotchas out of memory before hitting the same wall, and notices workflows that repeat often enough to deserve their own skill. Skill patches wait for your approval.

Cross-session search over past conversations is not here — Claude's architecture does not allow it. Neither does background review: you invoke /skill-review yourself, usually after a batch of tasks. The profile comes from what sits in the workspace, so on a fresh project with little git history there is not much to synthesize.

What it helps with

  • spot skills that went stale after an API change
  • write a known gotcha back into the skill that hit it
  • build a user profile from git history and project layout
  • turn a repeating workflow into a skill
  • apply a known workaround before a step fails

Example prompts for the agent

  • Run /skill-review and show me which skills are out of date
  • Build my profile with /build-user-profile
  • We keep fixing the same thing — check whether it needs its own skill

How to install adaptive-agent

Plugin marketplace

/plugin marketplace add anthropics/claude-plugins-community
/plugin install adaptive-agent@claude-community

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about adaptive-agent

How do I install adaptive-agent in Claude Code?

From the marketplace: run /plugin marketplace add anthropics/claude-plugins-community, then /plugin install adaptive-agent@claude-community.

What does adaptive-agent do?

It adds two skills and a set of behavioral rules. /skill-review audits your skills and patches stale ones, /build-user-profile synthesizes a profile from workspace context, and the CLAUDE.md rules turn on skill self-patching and memory-to-skill flow.

Why is the skill audit manual?

Claude cannot spawn background model calls, so you trigger /skill-review yourself, typically after a batch of tasks. The CLAUDE.md rules stay active in between.

Source text

SKILL.md · MIT
# Adaptive Agent

[![GitHub](https://img.shields.io/github/stars/truenorth-lj/adaptive-agent-skill?style=social)](https://github.com/truenorth-lj/adaptive-agent-skill)
[![skills.sh](https://img.shields.io/badge/skills.sh-install-blue)](https://skills.sh/truenorth-lj/adaptive-agent-skill)
[![ClawHub: skill-review](https://img.shields.io/badge/ClawHub-skill--review-purple)](https://clawhub.ai/skills/adaptive-agent-skill-review)
[![ClawHub: build-user-profile](https://img.shields.io/badge/ClawHub-build--user--profile-purple)](https://clawhub.ai/skills/adaptive-agent-build-user-profile)
[![Anthropic Plugin](https://img.shields.io/badge/Anthropic_Plugin-pending_review-orange)](https://github.com/truenorth-lj/adaptive-agent-skill)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

Make your AI coding agent get stronger with use — skill self-improvement, memory-skill feedback loops, and automatic user profiling.

Inspired by [Hermes Agent](https://github.com/NousResearch/hermes-agent)'s four-layer memory architecture, adapted for Claude Code and other AI coding agents through prompt engineering.

## Install

```bash
# skills.sh (Claude Code, Codex, Gemini CLI, Copilot, 45 agents)
npx skills add truenorth-lj/adaptive-agent-skill

# ClawHub
clawhub install adaptive-agent-skill-review
clawhub install adaptive-agent-build-user-profile

# Manual (any agent)
git clone https://github.com/truenorth-lj/adaptive-agent-skill.git
cp -r adaptive-agent-skill/skills/skill-review ~/.claude/skills/
cp -r adaptive-agent-skill/skills/build-user-profile ~/.claude/skills/
```

## Directory Structure

```
adaptive-agent-skill/
├── CLAUDE.md                          # Always-on behavioral rules (paste into your project)
├── .claude-plugin/
│   └── plugin.json                    # Claude Code plugin manifest
├── skills/
│   ├── skill-review/
│   │   └── SKILL.md                   # Periodic skill audit and improvement
│   └── build-user-profile/
│       └── SKILL.md                   # Build user profile from workspace context
├── templates/
│   └── user_profile.md                # Memory template for user profile
├── meta.json                          # Skill metadata
├── LICENSE
└── README.md
```

## The Idea

AI agents treat skills and memory as separate systems. They shouldn't.

- **Skills** = procedural memory ("how to do things" — muscle memory)
- **Memory** = declarative memory ("what I know" — conscious memory)
- They should feed each other in a loop

When a skill fails, the lesson should flow back into the skill AND into memory. When memory contains a relevant gotcha, it should be applied proactively before the skill hits the same wall.

### Three-Layer Architecture

```
┌────────────────────────────────────────────────┐
│  CLAUDE.md — Always-On Rules                    │
│  Auto-patch skills on friction                  │
│  Apply memory lessons proactively               │
│  Detect skill gaps from repeated workflows      │
├────────────────────────────────────────────────┤
│  Skills — Procedural Memory                     │
│  /skill-review: audit and improve all skills    │
│  /build-user-profile: build who-you-are memory  │
├────────────────────────────────────────────────┤
│  Memory — Declarative Memory                    │
│  user_profile.md: role, strengths, preferences  │
│  (agent's memory system, auto-loaded)           │
└────────────────────────────────────────────────┘
```

## Setup

### 1. Add behavioral rules to your project

Copy the "Adaptive Behavior" section from `CLAUDE.md` into your project's CLAUDE.md. This enables the always-on rules:

- Skill self-improvement (auto-patch on friction)
- Memory → Skill flow (apply gotchas proactively)
- Skill gap detection (create skills for repeated workflows)

### 2. Build your user profile

Run `/build-user-profile` in your first session. The agent will:

1. Scan your workspace (git history, project structure, tech stack)
2. Synthesize a profile (role, strengths, work style, preferences)
3. Ask you to validate
4. Save to memory — every future session starts knowing who you are

### 3. Review skills periodically

Run `/skill-review` after a batch of tasks. The agent will:

1. Inventory all skills with last-modified dates
2. Cross-reference with memory and gotchas
3. Patch stale skills, flag gaps
4. Report summary

## How It Works

### Skill Self-Improvement (Always-On)

```
You run /deploy → a step fails (API changed)
  → Agent fixes the immediate problem
  → Agent patches the skill file (adds ## Gotchas or updates steps)
  → Agent saves lesson to memory if cross-skill
  → Next session: skill has the fix baked in
```

### Memory → Skill Flow (Always-On)

```
Memory has: "Zeabur CLI domain create needs GraphQL fallback"
You run /deploy with Zeabur step
  → Agent checks memory before executing
  → Agent applies the workaround proactively
  → You never hit the known issue
```

### User Profile (On Demand)

```
First session: /build-user-profile
  → Gathers context from git, config files, memory
  → Writes structured profile to memory
  → Every future session starts knowing who you are
```

## Background: Hermes Agent's Memory Architecture

This project is based on a [source-code analysis](https://zengineer.blog/blog/deeptech/hermes-agent-deep-dive-nous-research-ai-agents-2026/) of Hermes Agent v0.9.0, which implements a four-layer memory system:

| Layer | Hermes Implementation | Our Adaptation |
|-------|----------------------|----------------|
| L4: Procedural Memory | Skills with auto-create + auto-patch | Skills with CLAUDE.md auto-patch rules |
| L3: Semantic Memory | FTS5 cross-session search | Not possible (architecture constraint) |
| L2: Declarative Memory | MEMORY.md + USER.md (bounded) | Agent memory files (no char limit) |
| L1: External Plugins | Honcho, mem0, 11 backends | Not possible (architecture constraint) |

We can't replicate L1 and L3 (they require infrastructure changes), but L2 and L4 are achievable through prompt engineering alone. The key insight: **Opus 4.6's instruction-following ability compensates** — a smart agent that follows behavioral rules reliably is equivalent to a less-smart agent with built-in memory infrastructure.

## Constraints

| Limitation | Why | Workaround |
|-----------|-----|------------|
| No cross-session search | Agent can't search past conversations | Memory files persist key lessons |
| No background review | Can't spawn background LLM calls | Manual `/skill-review` invocation |
| No proactive memory saves | Only saves when rules trigger | CLAUDE.md rules cover common cases |
| Permission gates | Skill patches need user approval | Expected — user controls the boundary |

## Compatibility

| Agent | Status |
|-------|--------|
| Claude Code | Full support (primary target) |
| Codex CLI | Skills work, CLAUDE.md → AGENTS.md |
| Gemini CLI | Skills work, CLAUDE.md equivalent varies |
| OpenClaw | Skills work via agentskills.io standard |
| Cursor | Skills work via .cursorrules |

## License

MIT

© truenorth-lj · MIT · truenorth-lj/adaptive-agent-skill

Similar plugins

All plugins for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor