coach

Detect friction signals and propose rule updates for Claude's learning.

51|13|Updated Oct 18, 2025

Search Tags:#workflow #learning #improvement #prompt-engineering #friction #coach

Ready to run

npx skills add https://github.com/netresearch/claude-code-marketplace --skill coach

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coach
Source: https://github.com/netresearch/claude-code-marketplace/tree/main/plugins/coach/skills/coach
Command: npx skills add https://github.com/netresearch/claude-code-marketplace --skill coach

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Coach enables Claude to learn from friction signals and improve over time. It detects user corrections, repeated instructions, tool failures, and tone escalations, then proposes concrete improvement candidates that require explicit user approval before being applied.

Core Features & Use Cases

Detect learning opportunities from user corrections, repeated instructions, tool failures, and tone escalations
Aggregate signals into candidates with fingerprints for deduplication
Decide scope (project vs global) based on usage patterns
Review via /coach review and apply via /coach approve
Local storage of events and proposals in ~/.claude-coach

Quick Start

Use /coach review to view pending improvement candidates and /coach approve to apply approved changes.

Frequently Asked Questions about coach

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

FAQPage Schema

How does Claude learn from my corrections and feedback?▼

Coach detects friction signals—corrections, repeated instructions, tool failures, and tone changes—then proposes concrete rule updates to improve Claude's behavior. You review and approve changes via /coach review and /coach approve before they're applied to your CLAUDE.md file.

What counts as a friction signal that Coach can detect?▼

Friction signals include user corrections of Claude's responses, repeated instructions you give multiple times, tool failures or errors, and tone escalations indicating frustration. Coach aggregates these into improvement candidates with deduplication fingerprints.

How do I review and apply improvements Coach proposes?▼

Use /coach review to see pending improvement candidates organized by signal type. Select candidates to approve, then use /coach approve to apply them. Coach decides whether changes are project-scoped or global before updating CLAUDE.md.

Can Coach distinguish between project-specific and global improvements?▼

Yes. Coach performs scope decisions based on usage patterns to determine whether a friction signal should update your local project rules or apply globally across all interactions, ensuring improvements match their context.

Where does Coach store friction signals and improvement candidates?▼

Coach stores all detected events and proposed improvements locally in ~/.claude-coach. This local storage lets you review, manage, and control which signals become rule updates without external dependencies.

Does Coach require explicit approval before changing my rules?▼

Yes. Coach requires explicit user approval via /coach approve before any improvement candidate is applied to CLAUDE.md. You retain full control over which friction-derived rules actually take effect.