Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Activation Energy

ASecurity

Lower the initial energy barrier required to start new behaviors, projects, or changes to make initiation effortless and inevitable

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
educationgoreacttestingapi

Works with

api

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill activation-energy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Activation Energy?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Activation Energy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-activation-energy/badge)](https://www.skillsdirectory.com/skills/lev-os-activation-energy)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: activation-energy
description: Lower the initial energy barrier required to start new behaviors, projects, or changes to make initiation effortless and inevitable
---

# Activation Energy

## Overview

Activation energy is the minimum energy required to initiate a chemical reaction. Even exothermic reactions (which release energy overall) require an initial energy input to start. In chemistry, catalysts lower activation energy, making reactions occur more easily. As a mental model, activation energy explains why starting is disproportionately harder than continuing. The initial barrier - psychological, logistical, or cognitive - prevents action even when the action would be beneficial. Getting started requires overcoming inertia; once moving, momentum takes over. This applies to habit formation (first gym visit hardest), product adoption (signup friction), and organizational change (initial resistance). The key insight: Most failure happens at the starting line. Lower the barrier, increase success.

## When to Use

- **Habit formation**: Making new behaviors automatic by reducing startup friction
- **User onboarding**: Minimizing barriers to first product experience
- **Team productivity**: Removing obstacles to starting important work
- **Behavior change**: Designing environments that make good choices effortless
- **Product launches**: Reducing initial adoption barriers for early users
- **Organizational change**: Lowering resistance to new processes or tools
- **Personal productivity**: Eliminating decision friction that delays action

## The Process

### Step 1: Identify the Activation Energy Barrier
Diagnose what's preventing initiation. The barrier is usually invisible to those who've already overcome it.

**Common barriers**:
- **Cognitive load**: Too many decisions required before starting
- **Psychological resistance**: Fear, uncertainty, intimidation
- **Logistical friction**: Missing tools, unclear process, setup required
- **Social pressure**: Judgment concern, asking for help required
- **Time perception**: Seems like it will take longer than it does
- **Complexity**: Unclear where to start or what first step is

**Example**: Want to exercise daily
- Barrier isn't physical effort (that's maintenance energy)
- Barriers: deciding what workout, finding gym clothes, driving to gym, feeling self-conscious, etc.
- Activation energy = sum of these pre-workout obstacles

### Step 2: Measure Current Initiation Rate
Quantify how often people start vs. how often they intend to start. The gap reveals activation barrier strength.

**Metrics**:
- Signup completion rate (started vs. finished)
- Time from intent to first action
- Drop-off rate at beginning vs. middle
- Repeat attempts needed before success
- Support requests about "how to start"

**Example**: SaaS product
- 1,000 signups started → 300 completed onboarding = 70% abandoned at start
- High activation energy (signup form too long, value unclear, setup complex)

### Step 3: Deploy Catalysts - Lower the Barrier
Use strategies that reduce required initiation energy without changing the core action.

**Catalyst techniques**:

**1. Pre-decision (eliminate choice friction)**:
- Provide defaults, recommendations, or single path
- Remove "what should I do?" paralysis
- Example: "Start with recommended template" vs. "Choose from 50 templates"

**2. Pre-setup (eliminate logistical friction)**:
- Do preparatory work in advance
- Remove "I need to find/configure X first" obstacles
- Example: Pack gym bag night before, sleep in workout clothes

**3. Simplify first step (reduce scope)**:
- Make starting absurdly easy (2-minute version)
- Separate initiation from completion
- Example: "Just put on running shoes" (not "run 5 miles")

**4. Environmental design (proximity reduction)**:
- Place tools/triggers in path of least resistance
- Remove physical/mental distance to starting
- Example: Leave book on pillow, guitar on stand (not in case in closet)

**5. Social accountability (external catalyst)**:
- Public commitment, partner, or scheduled time
- Converts intention into obligation
- Example: Class at 6am (paid, social) vs. "I'll work out sometime today"

**6. Trigger linkage (habit stacking)**:
- Attach new behavior to existing automatic action
- Piggyback on established momentum
- Example: "After coffee, I meditate" (coffee is trigger)

### Step 4: Separate Initiation from Continuation
Recognize that starting and maintaining require different strategies. Optimize each separately.

**Framework - The Two-Minute Rule**:
- Initial action should take <2 minutes
- Goal is to start, not complete
- Once started, continuing is natural (momentum)

**Examples**:
- Want to write book → "Open laptop and write one sentence"
- Want to eat healthy → "Cut one vegetable"
- Want to learn coding → "Open code editor and type 'Hello World'"

The full action (writing chapter, cooking meal, building app) happens automatically after low-activation start.

### Step 5: Test and Iterate on Barrier Height
Experiment with different catalyst approaches. Measure which reduce activation energy most effectively.

**A/B testing activation energy**:
- Version A: Traditional signup (5-field form)
- Version B: Single-field start (just email, defer rest)
- Measure completion rates

**Personal experiments**:
- Try different trigger times (morning vs. evening)
- Test various environment designs (visible vs. hidden)
- Vary initiation scope (30 min vs. 2 min)

**Optimization rule**: If >80% of attempts result in starting, activation energy is low enough. If <50%, barrier is still too high.

### Step 6: Design Self-Lowering Systems
Create mechanisms that automatically reduce activation energy over time (practice, familiarity, environmental optimization).

**Auto-catalyst strategies**:
- **Progressive disclosure**: Show more complexity only after basic competence
- **Learned patterns**: Repeated starts create mental shortcuts (less cognitive load)
- **Environmental accumulation**: Tools naturally migrate to convenient locations through use
- **Social normalization**: First time awkward, tenth time automatic

**Example**: Learning to code
- Day 1: High activation (don't know where to start, IDE intimidating)
- Week 2: Medium activation (know how to open files, run code)
- Month 3: Low activation (IDE open by default, muscle memory for basic tasks)
- Year 1: Near-zero activation (coding is default problem-solving mode)

## Example Application

**Scenario**: Person wants to build daily writing habit but consistently fails to start. Intention is high, execution is zero. Diagnosis: activation energy too high.

**Step 1 - Identify barrier**:
- Opens laptop → sees email/Slack → gets distracted
- Blank page intimidating (what to write?)
- Writing feels like "big task" (psychological barrier)
- No clear trigger or time (when should I write?)

**Step 2 - Measure**:
- Intends to write 7 days/week
- Actually writes 0.5 days/week
- Gap = 93% failure rate at initiation, not during writing (once started, completes)

**Step 3 - Deploy catalysts**:

**Catalyst 1 - Pre-decision**: Create "Writing Prompts" doc with 30 pre-written prompts. No more "what should I write?" paralysis.

**Catalyst 2 - Pre-setup**: Before bed, open laptop, load writing app, place on desk with coffee mug. Morning trigger: see setup, start.

**Catalyst 3 - Simplify first step**: Reframe goal from "write 500 words" to "write one sentence." Lower target removes intimidation.

**Catalyst 4 - Environmental design**: Use separate user account on laptop (no email/Slack), only writing app installed. Eliminates distraction friction.

**Catalyst 5 - Social accountability**: Text friend when starting. Social pressure converts intention to action.

**Catalyst 6 - Trigger linkage**: "After morning coffee, open laptop and write one sentence." Coffee is automatic trigger, writing becomes automatic response.

**Step 4 - Separate initiation from continuation**:
- Goal: Start writing (write one sentence)
- Not: Complete full article
- Result: 90% of days, after one sentence, writes for 20+ minutes (momentum takes over)

**Step 5 - Test and iterate**:
- Week 1: Write 4 days (57% success) - still too much friction
- Week 2: Add "Writing Setup" ritual (coffee + prompt + laptop position) → 6 days (86% success)
- Week 3: Reduce target to "10 words" instead of "one sentence" → 7 days (100% success)

**Step 6 - Self-lowering system**:
- Month 1: Requires all catalysts (prompts, setup, ritual)
- Month 2: Only needs laptop + coffee (prompts internalized)
- Month 3: Automatic - writing is default morning behavior, no conscious decision needed

**Result**: Habit established through activation energy reduction, not willpower increase. Changed environment, not person.

## Anti-Patterns

**Willpower dependency**: Relying on motivation to overcome high activation energy. Willpower is finite; low activation energy is permanent.

**Over-scoping initiation**: Setting first step too large. "Write chapter" fails; "write one sentence" succeeds.

**Ignoring environmental design**: Trying to start from disadvantaged position (tools hidden, distractions present). Environment beats intention.

**Optimization without measurement**: Guessing what lowers activation energy instead of testing actual initiation rates.

**Conflating starting with completing**: Judging success by completion, not initiation. Starting is the hard part; momentum handles the rest.

**Adding activation energy accidentally**: Creating systems that increase friction to starting (complex onboarding, unclear instructions, tool setup required).

## Related Frameworks

- **Inertia**: Objects at rest stay at rest; activation energy is the force needed to overcome inertia
- **Momentum**: Once started (activation achieved), continuing becomes easy
- **Friction**: Activation energy is a special case of friction (resistance to starting)
- **Habit Formation**: Building automaticity by reducing activation energy to near-zero
- **Two-Minute Rule**: Make starting so easy (2 min) that resistance disappears
- **Environment Design**: Shaping surroundings to lower activation barriers
- **Catalysts**: Substances/strategies that lower required energy for reactions/actions
- **Choice Architecture**: Designing decisions to minimize cognitive activation cost

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Math Olympiad

1. **Strip thinking before verifying** — a verifier that sees the reasoning is biased toward agreement. Fresh context, cleaned proof only. 2. **"Does this prove RH?"** — if your theorem's specialization to ζ is a famous open problem, you have a gap. Most reliable red flag. 3. **Short proof → extract the general lemma** — try 2×2 counterexamples. If general form is false, find what's special about THIS instance. 4. **Same gap twice → step back** — the case split may be obscuring a unifie

358070 votes

Mcore Split Pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

177030 votes

Mcore Onboard Gb200 1node Tests

Onboard 1-node GitHub MR functional tests for GB200 from existing mr-scoped 2-node tests.

177030 votes

Seedance Recipes

This skill should be used when the user asks for a Seedance 2.0 template, genre recipe, product ad, lifestyle video, drama scene, music video, landscape shot, commercial, animation scene, or reusable production pattern.

71130 votes

Root Finding

Problem-solving strategies for root finding in numerical methods

39350 votes
View all in education →