war-of-art-pressfield

Name: war-of-art-pressfield
Author: simbajigege

11installs21forks

How to install war-of-art-pressfield?

simbajigege/book2skills/war-of-art-pressfield

$npx -y skills add simbajigege/book2skills --skill war-of-art-pressfield

Installs into the current project.

Summary

Apply Steven Pressfield resistance diagnosis for procrastination, turning

Files · 1

View on GitHub

SKILL.md

1	# The War of Art — Creative Resistance Skill
2
3	Knowledge source: The War of Art by Steven Pressfield.
4
5	## Overview
6
7	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.
8
9	## When to Use This Skill
10
11	Use this skill when the user asks:
12	- "Why can't I start?"
13	- "I keep procrastinating on my creative work."
14	- "How do I turn pro?"
15	- "Am I blocked by fear or laziness?"
16	- "How do I stop needing external validation?"
17	- "Give me a daily discipline plan."
18
19	## Core Principle
20
21	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.
22
23	## Workflow Inventory
24
25	\| Workflow \| User question pattern \| Inputs \| Steps \| Output \| Independent trigger? \| Distinct references? \| Triage score \| Should be subskill? \| Reason \|
26	\|---\|---\|---\|---\|---\|---\|---:\|---:\|---\|---\|
27	\| 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. \|
28	\| 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. \|
29	\| Validation shift \| "I need approval" \| Audience, metrics, motivation \| Separate hierarchy from territory \| Motivation reset \| Yes \| Yes \| 3 \| No \| Supports the same creative battle. \|
30	\| 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. \|
31
32	## Architecture Justification
33
34	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.
35
36	## DIMENSION 1: Resistance Diagnosis
37
38	The Rule: The more important a calling is, the stronger resistance tends to feel.
39
40	### Key questions to ask:
41	- What meaningful work is the user avoiding?
42	- What excuse, drama, distraction, or rationalization appears?
43	- Is resistance strongest near starting or finishing?
44	- What fear is fueling the avoidance?
45
46	### Decision criteria / Checklist:
47	- Identify procrastination, self-dramatization, self-medication, victimhood, rationalization, or sabotage.
48	- Treat resistance as impersonal and predictable.
49	- Use resistance as a compass toward important work.
50	- Separate real constraints from avoidance stories.
51
52	### Warning signals:
53	- "I'll start tomorrow."
54	- Elaborate reasonable explanations for not doing the work.
55	- Creating drama, distractions, or crises around the task.
56	- Quitting near the finish line.
57
58	### Agent instruction:
59	When the user describes avoidance, name the exact resistance pattern before offering productivity tactics.
60
61	## DIMENSION 2: Turning Pro
62
63	The Rule: A professional shows up, stays on the job, acts despite fear, and accepts no excuses.
64
65	### Key questions to ask:
66	- What would a professional do today regardless of mood?
67	- What is the fixed time, place, and work quota?
68	- What excuses must be rejected in advance?
69	- What skill or help is needed?
70
71	### Decision criteria / Checklist:
72	- Daily showing up.
73	- Long-haul commitment.
74	- Patience and order.
75	- Preparedness and technique.
76	- Willingness to ask for help.
77
78	### Warning signals:
79	- Waiting for inspiration.
80	- Overidentifying with praise or rejection.
81	- Showing off instead of practicing technique.
82	- Avoiding help out of pride.
83
84	### Agent instruction:
85	Turn the user's vague intention into a concrete professional protocol with time, place, quota, and no-excuse rule.
86
87	## DIMENSION 3: Fear, Ego, and Distance
88
89	The Rule: The professional acts in fear and keeps enough distance from the work to keep working.
90
91	### Key questions to ask:
92	- What fear is present?
93	- Is the user treating the work as proof of identity?
94	- What outcome is outside the user's control?
95	- How can the user focus on today's labor instead?
96
97	### Decision criteria / Checklist:
98	- Acknowledge fear without obeying it.
99	- Evaluate effort and process, not identity.
100	- Separate self-worth from work reception.
101	- Return to the next session.
102
103	### Warning signals:
104	- "If this fails, I am a failure."
105	- Perfectionism delaying shipping.
106	- Mood determining whether work happens.
107
108	### Ag

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

war-of-art-pressfield

11installs21forks

View on GitHub

How to install war-of-art-pressfield?

simbajigege/book2skills/war-of-art-pressfield

$npx -y skills add simbajigege/book2skills --skill war-of-art-pressfield

Installs into the current project.

Summary

Apply Steven Pressfield resistance diagnosis for procrastination, turning

Files · 1

View on GitHub

SKILL.md

1	# The War of Art — Creative Resistance Skill
2
3	Knowledge source: The War of Art by Steven Pressfield.
4
5	## Overview
6
7	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.
8
9	## When to Use This Skill
10
11	Use this skill when the user asks:
12	- "Why can't I start?"
13	- "I keep procrastinating on my creative work."
14	- "How do I turn pro?"
15	- "Am I blocked by fear or laziness?"
16	- "How do I stop needing external validation?"
17	- "Give me a daily discipline plan."
18
19	## Core Principle
20
21	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.
22
23	## Workflow Inventory
24
25	\| Workflow \| User question pattern \| Inputs \| Steps \| Output \| Independent trigger? \| Distinct references? \| Triage score \| Should be subskill? \| Reason \|
26	\|---\|---\|---\|---\|---\|---\|---:\|---:\|---\|---\|
27	\| 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. \|
28	\| 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. \|
29	\| Validation shift \| "I need approval" \| Audience, metrics, motivation \| Separate hierarchy from territory \| Motivation reset \| Yes \| Yes \| 3 \| No \| Supports the same creative battle. \|
30	\| 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. \|
31
32	## Architecture Justification
33
34	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.
35
36	## DIMENSION 1: Resistance Diagnosis
37
38	The Rule: The more important a calling is, the stronger resistance tends to feel.
39
40	### Key questions to ask:
41	- What meaningful work is the user avoiding?
42	- What excuse, drama, distraction, or rationalization appears?
43	- Is resistance strongest near starting or finishing?
44	- What fear is fueling the avoidance?
45
46	### Decision criteria / Checklist:
47	- Identify procrastination, self-dramatization, self-medication, victimhood, rationalization, or sabotage.
48	- Treat resistance as impersonal and predictable.
49	- Use resistance as a compass toward important work.
50	- Separate real constraints from avoidance stories.
51
52	### Warning signals:
53	- "I'll start tomorrow."
54	- Elaborate reasonable explanations for not doing the work.
55	- Creating drama, distractions, or crises around the task.
56	- Quitting near the finish line.
57
58	### Agent instruction:
59	When the user describes avoidance, name the exact resistance pattern before offering productivity tactics.
60
61	## DIMENSION 2: Turning Pro
62
63	The Rule: A professional shows up, stays on the job, acts despite fear, and accepts no excuses.
64
65	### Key questions to ask:
66	- What would a professional do today regardless of mood?
67	- What is the fixed time, place, and work quota?
68	- What excuses must be rejected in advance?
69	- What skill or help is needed?
70
71	### Decision criteria / Checklist:
72	- Daily showing up.
73	- Long-haul commitment.
74	- Patience and order.
75	- Preparedness and technique.
76	- Willingness to ask for help.
77
78	### Warning signals:
79	- Waiting for inspiration.
80	- Overidentifying with praise or rejection.
81	- Showing off instead of practicing technique.
82	- Avoiding help out of pride.
83
84	### Agent instruction:
85	Turn the user's vague intention into a concrete professional protocol with time, place, quota, and no-excuse rule.
86
87	## DIMENSION 3: Fear, Ego, and Distance
88
89	The Rule: The professional acts in fear and keeps enough distance from the work to keep working.
90
91	### Key questions to ask:
92	- What fear is present?
93	- Is the user treating the work as proof of identity?
94	- What outcome is outside the user's control?
95	- How can the user focus on today's labor instead?
96
97	### Decision criteria / Checklist:
98	- Acknowledge fear without obeying it.
99	- Evaluate effort and process, not identity.
100	- Separate self-worth from work reception.
101	- Return to the next session.
102
103	### Warning signals:
104	- "If this fails, I am a failure."
105	- Perfectionism delaying shipping.
106	- Mood determining whether work happens.
107
108	### Ag

People who liked this also viewed

6 picks

Type