From daily-metrics
This skill should be used when the user asks to "reduce friction", "simplify tracking", "make this easier", "audit my system", "why is this so hard", "I keep forgetting to log", "tracking is tedious", "streamline my habits", or when behaviors aren't happening consistently and the system needs friction analysis.
npx claudepluginhub mberto10/mberto-compoundThis skill uses the workspace's default tool permissions.
Systematically identify and reduce friction in any behavioral system.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.
Systematically identify and reduce friction in any behavioral system.
The friction hypothesis: most failures are friction failures, not knowledge failures. You know what to do. Friction stops you from doing it. This skill audits friction and applies the reduction hierarchy.
1. ELIMINATE — Remove the step entirely (best)
|
2. AUTOMATE — Make it happen without attention
|
3. REDUCE — Make it easier but still present
|
4. TOLERATE — Push through with willpower (worst)
Most people operate at "tolerate." Move up the hierarchy.
| Type | Definition | Examples |
|---|---|---|
| Activation | Cost to start | Decision fatigue, setup time, context switching |
| Execution | Cost to continue | Effort, complexity, time required |
| Feedback | Cost to learn | Delayed results, noisy data, unclear attribution |
Each type needs different interventions.
For each tracked behavior, identify friction at each stage:
| Behavior | Activation Friction | Execution Friction | Feedback Friction |
|---|---|---|---|
| [behavior] | [what stops starting] | [what makes continuing hard] | [what blocks learning] |
Focus on 4s and 5s first. These kill behaviors.
For each high-friction point:
ELIMINATE — Can we remove this entirely?
AUTOMATE — Can we make it happen without attention?
REDUCE — Can we make it simpler?
TOLERATE — Accept consciously
Tracking itself is friction.
Every input added is execution friction. The goal is minimum viable tracking — enough feedback to iterate, not so much that tracking becomes the obstacle.
Signs of over-tracking:
Solution: Eliminate low-value tracking. Keep only what gets reviewed.
Document transformations:
| Before | Friction Score | Intervention | After | New Score |
|---|---|---|---|---|
| [original] | [4-5] | [eliminate/automate/reduce] | [new version] | [1-2] |
friction_audit:
date: [date]
domain: [domain]
high_friction_items:
- behavior: [name]
friction_type: [activation|execution|feedback]
current_score: [4-5]
intervention: [eliminate|automate|reduce]
description: [what to change]
new_expected_score: [1-2]
eliminated:
- "[tracking/behavior removed and why]"
automated:
- "[what now syncs automatically]"
reduced:
- "[what was simplified and how]"
| Friction Source | Tolerate | Reduce | Automate | Eliminate |
|---|---|---|---|---|
| Deciding what to do | Think each time | Weekly planning | Fixed schedule | Same thing daily |
| Data entry | Manual each event | End-of-day batch | Device sync | Don't track it |
| Finding tools | Search each time | Dedicated location | Always ready | Fewer tools |
| Multiple apps | Switch between | Single dashboard | Unified system | One app |