Skip to content
Writing
Skill

/war-of-art-pressfield

Apply Steven Pressfield resistance diagnosis for procrastination, turning

BOOST
From plugin
book2skills
19238 skills
Install
$ npx -y skills add simbajigege/book2skills --skill war-of-art-pressfield --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/war-of-art-pressfield

Context preview

The summary Claude sees to decide when to auto-load this skill.

Apply Steven Pressfield resistance diagnosis for procrastination, turning

SKILL.md

war-of-art-pressfield.SKILL.md
name: war-of-art-pressfield
description: Apply Steven Pressfield resistance diagnosis for procrastination, turning
  pro, daily creative discipline, fear, hierarchy, and territory.
license: Skill distillation for personal/educational use. Do not reproduce source
  passages verbatim.

The War of Art — Creative Resistance Skill

**Knowledge source:** *The War of Art* by Steven Pressfield.

Overview

Use this skill to diagnose creative resistance, procrastination, avoidance, self-sabotage, amateur habits, and dependence on external validation. It helps writers, artists, founders, and anyone pursuing difficult long-term work shift from avoidance to professional daily action.

When to Use This Skill

Use this skill when the user asks:

  • "Why can't I start?"
  • "I keep procrastinating on my creative work."
  • "How do I turn pro?"
  • "Am I blocked by fear or laziness?"
  • "How do I stop needing external validation?"
  • "Give me a daily discipline plan."

Core Principle

Resistance is an internal force that opposes meaningful upward work. It cannot be reasoned away; it is beaten by turning pro: showing up daily, acting despite fear, accepting no excuses, and working from one's territory rather than hierarchy.

Workflow Inventory

| Workflow | User question pattern | Inputs | Steps | Output | Independent trigger? | Distinct references? | Triage score | Should be subskill? | Reason | |---|---|---|---|---|---|---:|---:|---|---| | Resistance diagnosis | "Why am I avoiding this?" | Goal, avoidance behavior, excuses, fear | Identify resistance form and compass signal | Resistance map | Yes | Yes | 3 | No | First step of one arc. | | Turn-pro plan | "How do I become disciplined?" | Schedule, work type, constraints | Convert amateur habits to pro conduct | Daily protocol | Yes | Yes | 3 | No | Treatment for same diagnosis. | | Validation shift | "I need approval" | Audience, metrics, motivation | Separate hierarchy from territory | Motivation reset | Yes | Yes | 3 | No | Supports the same creative battle. | | Start/finish push | "I can't begin/finish" | Project stage, fear, stakes | Use start magic, finish-line risk, daily action | Immediate action plan | Yes | Yes | 3 | No | Same output format. |

Architecture Justification

The book is structured as Resistance, Turning Pro, and Higher Realm, but those are stages of one executable workflow: diagnose avoidance, adopt professional behavior, and ground motivation internally. Single-file architecture keeps the battle sequence intact.

DIMENSION 1: Resistance Diagnosis

**The Rule:** The more important a calling is, the stronger resistance tends to feel.

Key questions to ask:

  • What meaningful work is the user avoiding?
  • What excuse, drama, distraction, or rationalization appears?
  • Is resistance strongest near starting or finishing?
  • What fear is fueling the avoidance?

Decision criteria / Checklist:

  • Identify procrastination, self-dramatization, self-medication, victimhood, rationalization, or sabotage.
  • Treat resistance as impersonal and predictable.
  • Use resistance as a compass toward important work.
  • Separate real constraints from avoidance stories.

Warning signals:

  • "I'll start tomorrow."
  • Elaborate reasonable explanations for not doing the work.
  • Creating drama, distractions, or crises around the task.
  • Quitting near the finish line.

Agent instruction:

When the user describes avoidance, name the exact resistance pattern before offering productivity tactics.

DIMENSION 2: Turning Pro

**The Rule:** A professional shows up, stays on the job, acts despite fear, and accepts no excuses.

Key questions to ask:

  • What would a professional do today regardless of mood?
  • What is the fixed time, place, and work quota?
  • What excuses must be rejected in advance?
  • What skill or help is needed?

Decision criteria / Checklist:

  • Daily showing up.
  • Long-haul commitment.
  • Patience and order.
  • Preparedness and technique.
  • Willingness to ask for help.

Warning signals:

  • Waiting for inspiration.
  • Overidentifying with praise or rejection.
  • Showing off instead of practicing technique.
  • Avoiding help out of pride.

Agent instruction:

Turn the user's vague intention into a concrete professional protocol with time, place, quota, and no-excuse rule.

DIMENSION 3: Fear, Ego, and Distance

**The Rule:** The professional acts in fear and keeps enough distance from the work to keep working.

Key questions to ask:

  • What fear is present?
  • Is the user treating the work as proof of identity?
  • What outcome is outside the user's control?
  • How can the user focus on today's labor instead?

Decision criteria / Checklist:

  • Acknowledge fear without obeying it.
  • Evaluate effort and process, not identity.
  • Separate self-worth from work reception.
  • Return to the next session.

Warning signals:

  • "If this fails, I am a failure."
  • Perfectionism delaying shipping.
  • Mood determining whether work happens.

Agent instruction:

For emotionally loaded creative questions, redirect from identity judgment to professional action.

DIMENSION 4: Territory Over Hierarchy

**The Rule:** Work from intrinsic territory, not external ranking, status, or applause.

Key questions to ask:

  • Is the user working for rank or for the work itself?
  • What territory gives energy even without applause?
  • Which metrics are useful feedback versus hierarchy addiction?

Decision criteria / Checklist:

  • Define the territory: work the user returns to for its own sake.
  • Reduce dependence on public ranking.
  • Use feedback without letting it become the motive.
  • Protect the work from status games.

Warning signals:

  • Chasing likes, prestige, or comparison.
  • Changing work only to please hierarchy.
  • Calling oneself a hack by optimizing solely for market applause.

Agent instruction:

When the user's motivation is external validation, reframe the plan around territory, practice, and controllable output.

##

Read more
Ships withbook2skills

Transform the wisdom of classic books into AI Agent Skills. book2skills is an open-source project focused on systematically distilling high-quality practical books into Agent Skills format, enabling AI agents like Claude and Claude Code to directly apply the

Get the whole plugin

Other skills on book2skills.