friction-detector
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
npx skills add majiayu000/claude-skill-registry --skill friction-detector --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Friction-to-Learning Pipeline Detect friction signals during agent execution, track them across sessions, and graduate recurring patterns into permanent guidance. Bridges the gap between ephemeral session friction and durable CLAUDE.md rules. **Research backing**: Claude Coach (hook-based friction detection with SQLite storage), alirezarezvani's self-improving-agent (three-tier MEMORY to CLAUDE.md graduation), and the ACE framework (arXiv: evolving playbooks from execution feedback, +10.6% on agent tasks). **Current gap**: LEARNINGS.md exists but requires manual aggregation via `/abstract:aggregate-logs`. This skill adds automatic friction detection and a structured promotion path. ## Friction Signal Types | Signal | Detection Method | Weight | |--------|-----------------|--------| | Repeated corrections | User overrides same tool call 2+ times in session | High | | Command failures | Exit code != 0 patterns (same command type fails repeatedly) | Medium | | Permission denials | User denies tool call, indicating unexpected behavior | High | | Re-reads | Same file read 3+ times in session (lost context) | Low | | Retry loops | Same action attempted 3+ times with variations | Medium
- Friction Signal Types
- Three-Tier Storage Graduation
- Graduation Formula
- Detection Workflow
- Step 1: Scan Session for Signals
- Step 2: Compare Against Existing Log
- Step 3: Calculate Graduation Score
- Step 4: Propose Graduations
- Step 5: Store Results
- Anti-Noise Rules
- Friction Report Format
- Integration
- When NOT to Use
- Related
mkdir -p "$FRICTION_DIR" Count prior occurrences of similar signals if command -v rg &>/dev/null; then rg -c "$SIGNAL_TYPE" "$FRICTION_DIR"/*.json 2>/dev/null || echo "0" else grep -rc "$SIGNAL_TYPE" "$FRICTION_DIR"/*.json 2>/dev/null || echo "0" fi
What does the friction-detector skill do?
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill friction-detector --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
