self-improvement

Route agent-behavior feedback into durable fixes in hooks, skills, code, or instruction files.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill self-improvement-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-improvement
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/self-improvement/skills/self-improvement
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill self-improvement-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users correct an AI coding agent's behavior, the fix often lands in the nearest instruction file instead of the source that actually owns the behavior, so the same mistake recurs. This Skill turns feedback into durable improvements by choosing the right enforcement level and scope before editing anything. ## Core Features & Use Cases - Enforcement ladder: Prioritizes hooks and structural gates first, then skills, then project code, with instruction files as the last resort. - Scope ladder: Determines whether a rule applies cross-agent, cross-project, per-repo, or per-subproject before choosing a target. - Marketplace routing: Detects plugin marketplaces via manifest files and routes fixes to hook scripts, SKILL.md sources, or plugin metadata instead of runtime caches. - Pruning discipline: Deletes, merges, and simplifies duplicated or stale rules instead of only appending new ones. - Use Case: A user corrects the agent's commit message style for the third time. Instead of adding another line to CLAUDE.md, the Skill routes the fix into the git-discipline hook source so the rule is enforced structurally across all repos. ## Quick Start Tell the agent to apply this feedback as a durable fix: the agent keeps forgetting to run tests before committing, route it to the right source.

Frequently Asked Questions about self-improvement

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

FAQPage Schema
How do I make AI agent behavior fixes permanent?▼

Choose the strongest enforcement level first: hooks or structural gates, then skills, then project code, with instruction files as the last resort. Then pick the broadest scope where the rule still holds and edit the source that owns that behavior.

How do I fix feedback about a Claude Code plugin or skill?▼

Edit the plugin source, not runtime caches or user-level instructions. For skill behavior, edit the SKILL.md in the package source; for hook behavior, edit the hook script or manifest; caches under agent install directories are overwritten by updates.

When should I edit AGENTS.md or CLAUDE.md versus a hook?▼

Instruction files are the last resort, used only when no hook, skill, or code change can structurally address the feedback. Hooks are preferred because their reason text appears exactly when the mistake happens.

Why does the same agent mistake keep recurring after I added a rule?▼

The rule was likely pinned to a nearby instruction file instead of the source owning the behavior, or duplicated across multiple files. Consolidate into one owner source and prefer structural enforcement over prose reminders.

Can this skill delete or simplify existing agent instructions?▼

Yes, pruning is an explicit part of the workflow. It removes duplicated rules, stale plugin names, and procedural detail that belongs in a skill, keeping one clear source of truth instead of mirrored reminders.