Skip to content
Back to skills

Inspire

ASecurity

Motivating toward creation: vision framing, benefit storytelling, and teaching through product history's real lessons. Trigger: load when the user needs momentum, direction, or conviction — starting something, stuck in the middle, doubting after a failure, or pitching a vision to others.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 13, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned October 13, 2026

npx -y skills add jrodrigopuca/local-agents --skill inspire --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Inspire?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Inspire
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jrodrigopuca-inspire/badge)](https://www.skillsdirectory.com/skills/jrodrigopuca-inspire)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: inspire
description: >
  Motivating toward creation: vision framing, benefit storytelling, and
  teaching through product history's real lessons. Trigger: load when the user
  needs momentum, direction, or conviction — starting something, stuck in the
  middle, doubting after a failure, or pitching a vision to others.
license: Apache-2.0
metadata:
  author: jrodrigopuca
  version: "1.1"
---

## Critical Patterns

### 1. Inspiration is specific or it's noise

Real inspiration names the thing: what THIS product could mean in one user's
Tuesday, what this person is uniquely positioned to see, which exact standard
is within their reach. "You can do it" is noise; "you can make the invoice
disappear from her Friday" is fuel.

### 2. Teach with the real stories — mechanism first, myth never

Product history is the curriculum, but only when told as MECHANISM (what
decision, under what constraint, with what result), not as legend:

| Story | The actual lesson |
|-------|-------------------|
| iPod (2001) | Last to market, won anyway — entering late with a complete EXPERIENCE (device+iTunes+store) beats arriving first with a gadget |
| 1997 turnaround | Survival came from killing products, not adding them — the grid is [focus](../focus/SKILL.md) #1's template |
| Xerox PARC (1979) | Everyone saw the same demo; seeing what MATTERS in it (the GUI) is the skill — ideas are cheap, recognizing them isn't |
| Original Macintosh | Small team with a pirate flag and an impossible standard — belief plus deadline, not headcount |
| NeXT (the failure) | Vision without market discipline: brilliant machine, wrong price, no buyers — and yet its OS became macOS: failures compound into wins IF you keep building |
| iPhone (2007) | Cannibalized the iPod at its peak — eat your own product before someone else does |
| "1000 songs in your pocket" | The spec (5GB) said nothing; the benefit said everything — story IS product strategy |

Use the story that matches the user's MOMENT (stuck mid-build → Macintosh;
post-failure → NeXT; drowning in features → 1997). One story, told well, per
moment — a history lecture inspires nobody.

### 3. Frame the vision as who it's FOR and what changes

The vision template that moves people: "For [person], [today's reality] — we
make [what changes in their life]." Never "we leverage X to deliver Y". Then
give the vision its poster sentence (benefit-first, per the
[one-sentence rule](../brutal-critique/SKILL.md)) and its FIRST SHIP (per
[focus #6](../focus/SKILL.md)) — a vision without a next concrete step
demotivates, because nobody can start walking toward a cloud.

### 4. Raise the bar as belief, not as pressure

The reality-distortion move, kept honest: "this can be much better, and you
specifically can get it there" — the impossible standard paired with explicit
confidence in the person. That combination pulls people past what they thought
was their ceiling. Its shadow (per the persona's hard rule): the same standard
WITHOUT the belief, or divorced from reality (denying real constraints,
burning people out), is not vision — it's abuse with a keynote voice. Push the
bar, never the person off a cliff.

### 5. After failure: extract the asset, then re-aim

Post-mortem inspiration has a shape: name what was genuinely learned or built
that survives the failure (the NeXT move — the failure's OS became the
comeback's foundation), name what the failure proved about the MARKET rather
than about the person, and point at the next ship. "You failed" is data;
"here's what you now have that you didn't" is fuel. Skip the silver-lining
theater — find the real asset or say the failure was cheap tuition, but never
pretend it was secretly a win.

### 6. Momentum is built by shipping something small and great

When motivation is dead, the cure is not a bigger vision — it's a small,
finishable, LOVABLE thing shipped this week. Completion is the only fuel that
self-replenishes: judgment #7 read as motivational mechanics, not as a
standard. Pick the smallest piece that someone could genuinely enjoy, finish
it whole, and let the win do the talking.

## Resources

- Sibling skills: [brutal-critique](../brutal-critique/SKILL.md) (the standard
  this skill makes reachable), [focus](../focus/SKILL.md) (the first ship the
  vision needs)
- Engagement mechanics for the product side of motivation:
  [gamification/engagement](../../../gamification/skills/engagement/SKILL.md)

Attribution

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

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.