effort-reduction
Skill208 starsChanged 3 months agoMITView on GitHub
Reduce friction and effort in an offer to increase its perceived value. Use when users feel overwhelmed, drop-off is high, or the offer feels too complex. Maps friction points, removes unnecessary steps, adds templates, and suggests automation and done-for-you elements.
In this repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-offerSkill
- bonus-stackSkill
- business-modelSkill
- create-pluginSkill
- dfy-dwy-diySkill
- hormozi-hooksSkill
- hormozi-offerSkill
- hormozi-pitchSkill
- idea-to-productSkill
- landing-page-copySkill
- market-researchSkill
- objection-destroyerSkill
- offer-anglesSkill
- pricing-strategySkill
- productizeSkill
- value-acceleratorSkill
- value-perceptionSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 119
default paths to introduce
- Distinctive: line 156
When possible, remove work entirely.
- Distinctive: line 176
Create a cleaner path.
- Distinctive: line 196
If the offer requires skill, lower the barrier.
- Distinctive: line 202
remove need for prior knowledge
- Distinctive: line 297
Before vs After Example
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Effort Reduction (Friction Killer)
Purpose
Reduce how hard the offer feels to complete.
This skill lowers:
- effort
- confusion
- overwhelm
- required discipline
It directly improves:
Effort & Sacrifice ↓ → Value ↑
The goal: make the offer feel easy to start, easy to follow, easy to finish.
When to Use
Activate this skill when:
- users feel overwhelmed
- drop-off is high after purchase
- execution requires too many steps
- customers need “motivation” to continue
- the offer feels complex or heavy
- results depend too much on user discipline
Inputs
This skill works with:
- an
OFFER.md - a course, product, or service
- onboarding flow
- user journey description
- step-by-step process of the offer
Core Outcome
The assistant produces:
- a simplified execution path
- reduced cognitive load
- fewer decisions for the user
- automation opportunities
- done-for-you elements
- a smoother, easier experience
Assistant Behavior
1. Map the effort required
Break down the full journey:
Purchase → Start → Progress → Result
Identify:
- number of steps
- decisions required
- skills needed
- time investment
- discipline required
Then summarize:
Right now, the user must do X steps, make Y decisions, and figure out Z alone.
This creates friction and slows progress.
2. Identify friction points
For each step, find:
- where users hesitate
- where confusion appears
- where they need to “think too much”
- where they need extra tools or skills
- where they procrastinate
Map it like:
Step → Friction → Why it feels hard
3. Remove unnecessary steps
Simplify aggressively.
Ask:
- Is this step required for the result?
- Can it be skipped?
- Can it be merged with another step?
- Can the outcome be achieved faster?
Output:
- steps to remove
- steps to merge
- steps to delay until later
4. Reduce decisions
Too many choices = paralysis.
Replace:
- open-ended tasks → guided actions
- multiple options → default path
- “figure this out” → “do this exact thing”
Output:
- decisions to eliminate
- default paths to introduce
- clearer instructions
5. Replace blank work with templates
Blank pages create friction.
Convert:
- “create X” → “fill this template”
- “plan Y” → “use this structure”
- “write Z” → “use this swipe file”
Output:
- templates to add
- where they fit in the flow
- what they replace
6. Automate repetitive work
Identify what can run without effort.
Examples:
- pre-built systems
- auto-generated outputs
- plug-and-play tools
- integrations
Output:
- what to automate
- how it reduces effort
- tools or systems to use
7. Add done-for-you elements
When possible, remove work entirely.
Convert:
- DIY → DWY (done with you)
- DWY → DFY (done for you)
Examples:
- audits
- setup services
- pre-filled assets
- custom feedback
Output:
- what to do for the customer
- where it removes friction
- impact on perceived value
8. Simplify execution flow
Create a cleaner path.
Instead of:
- complex sequence
- scattered resources
- unclear next steps
Design:
- step-by-step path
- clear order
- visible progress
Output:
- new simplified flow
- number of steps reduced
- clearer progression
9. Reduce skill requirements
If the offer requires skill, lower the barrier.
Ways:
- break tasks into smaller actions
- provide examples
- give exact instructions
- remove need for prior knowledge
10. Improve perceived ease
Make it feel easier, not just be easier.
Techniques:
- use simple language
- show how little work is needed
- highlight shortcuts
- emphasize “no experience needed”
- show completed examples
Output Format
# EFFORT_REDUCTION.md
## 1. Current Effort Analysis
- Total steps
- Key effort points
- Where users struggle
## 2. Friction Map
- Step → Friction → Why it’s hard
## 3. Steps to Remove
- Step
- Why it’s unnecessary
## 4. Steps to Simplify
- Step
- How to simplify
## 5. Decisions to Eliminate
- Decision
- Default replacement
## 6. Templates to Add
- Template name
- What it replaces
- Where it’s used
## 7. Automation Opportunities
- Task
- Automation idea
- Impact
## 8. Done-for-You Additions
- What is done for the user
- Where it helps
- Value added
## 9. Simplified Execution Flow
- New step-by-step path
## 10. Effort Perception Improvements
- Messaging changes
- Structural changes⸻
Decision Rules
Remove steps when: • they don’t directly impact the result • they create delay without value • they add complexity
Add templates when: • users start from scratch • output is predictable • structure is repeatable
Automate when: • tasks are repetitive • tools can replace manual work • speed matters
Add done-for-you when: • the task is difficult • mistakes are costly • users lack skill or time
Simplify when: • users must think too much • instructions are unclear • execution feels heavy
⸻
Before vs After Example
Before • Watch lessons • Plan strategy • Create assets from scratch • Execute manually
After • Use pre-built template • Follow guided checklist • Plug into system • Execute with minimal decisions
⸻
Style Guidelines • cut complexity • favor action over thinking • reduce decisions • remove friction first, add value second • make everything feel simple and doable
⸻
Success Criteria
The skill works when: • the offer feels easy to start • users don’t get stuck early • fewer steps are needed • decisions are minimal • execution feels guided • completion rates increase • results feel easier to achieve
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

