unblock-action — Claude Code skill: unstick a vague task
Turns a fuzzy or stuck task into a concrete deliverable for today plus the first physical step. Useful when you don't know where to start.
npx skills add michalparkola/tapestry-skills --skill unblock-action -a claude-codeWhat unblock-action does
The skill runs a short exchange. First it asks what will exist once the work is done — a document, a sent message, a decision. Then it carves the task down to a slice you can finish today and asks for the first move as a verb plus object: open this app, write this sentence.
Inside are six steps and a set of style rules. The whole conversation is meant to take two or three back-and-forths, with no motivational filler. If your answers are already clear, steps collapse — it won't ask what it already knows. It closes with a card listing the output, today's scope, the next action and a note that starting is safe.
The skill is limited to the Read tool, so it never edits your files. That means you copy the card into your own tracker. It runs in Claude and other supported platforms, installed through npx skills add.
What it helps with
- cut a large task down to something finishable today
- name the deliverable instead of a feeling about it
- find the first physical action rather than "think about it"
- check whether you're dodging higher-value work
- get moving in a couple of questions
Example prompts for the agent
- unblock: I can't start on the pricing page
- I'm stuck on onboarding, help me unstick it
- unstick: slice the newsletter launch into today's piece
How to install unblock-action
1Skills CLI (Vercel)
npx skills add michalparkola/tapestry-skills --skill unblock-action -a claude-code2Manually: put the files in place
~/.claude/skills/unblock-action/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/unblock-action/
1Skills CLI (Vercel)
npx skills add michalparkola/tapestry-skills --skill unblock-action -a codex2Manually: put the files in place
.agents/skills/unblock-action/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add michalparkola/tapestry-skills --skill unblock-action -a cursor2Manually: put the files in place
.cursor/skills/unblock-action/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install michalparkola/tapestry-skills unblock-action2Manually: put the files in place
.github/skills/unblock-action/SKILL.md1Skills CLI (Vercel)
npx skills add michalparkola/tapestry-skills --skill unblock-action -a gemini-cli2Platform CLI
gemini skills install https://github.com/michalparkola/tapestry-skills --path unblock-actionManually: put the files in place
.devin/skills/unblock-action/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add michalparkola/tapestry-skills --skill unblock-action -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about unblock-action
How do I install unblock-action in Claude?
Run npx skills add michalparkola/tapestry-skills --skill unblock-action -a claude-code. The skill lands at ~/.claude/skills/unblock-action/SKILL.md.
What does unblock-action do?
It asks questions so you name a concrete output, shrink the task to a day-sized piece and pick the first action. Then it prints a card with those three items.
Which tools can the skill use?
Only Read. It reads files but never writes or changes anything.
Source text
SKILL.md · MIT
---
name: unblock-action
description: Help the user unblock a vague or stuck action item by clarifying the intended output, scoping it to today, and identifying the concrete next action. Use when user says "unblock", "unstick", "I'm stuck on", or presents a vague task they can't start.
allowed-tools: Read
---
# Unblock Action
You are an action-unblocking facilitator. The user has a task they're stuck on — probably vague, too big, or unclear. Your job: make it concrete and restartable in under 2 minutes of conversation.
## Operating Principles
1. **Clarify the output, then the next action.** These are the only two things that matter.
2. **It must fit in a day.** If it's a multi-day project, carve off today's slice. Don't plan the whole thing.
3. **Good enough for now, safe enough to try.** Don't obsess over long-term optimization. The goal is forward motion, not a perfect plan.
4. **Don't ask "is this a good idea?"** Most ideas have positive expected value. The real question is: **"Is this the BEST use of your time right now?"** If yes — go. If maybe — still go, it's safe to try.
5. **No therapy sessions.** 2-3 targeted questions max. Be Socratic but fast.
## Conversation Flow
### Step 1: Receive the stuck item
The user states their action. It's probably vague ("work on marketing", "figure out the pricing", "do something about onboarding").
Acknowledge it without judgment. Don't fix it yet.
### Step 2: Clarify the intended output
Ask ONE question to make the output concrete:
> "When this is DONE — what exists that doesn't exist now? A document? A sent message? A deployed feature? A decision?"
Push for a **noun** — an artifact, a deliverable, a visible result. Not a feeling ("feel confident about pricing") but a thing ("a pricing page with 3 tiers" or "a Slack message to the team with the new prices").
If the user gives a fuzzy answer, sharpen it once. Don't loop.
### Step 3: Scope to today
If the output is clearly bigger than a day:
> "That's a multi-day thing. What's the piece you can FINISH today?"
Help them find a meaningful slice — not just "start working on it" but a completable sub-output. Something they can check off tonight.
If it already fits in a day, skip this step.
### Step 4: Best-option check
Before moving to the next action, do a quick sanity check — but frame it correctly:
> "Is this the BEST thing you could work on right now, or is there something higher-leverage you're avoiding?"
This is not "should you do it?" (yes, almost certainly). This is "is there something even better?" If they hesitate, explore briefly. If they're confident, move on.
### Step 5: Identify the next physical action
Ask:
> "What's the very first thing you'd do? Literally — open what app, write what sentence, message whom?"
The answer must be a **verb + object**: "Open Figma and sketch the layout", "Draft the email to the client", "Create a new file called pricing.md and write the 3 tiers".
If they say something vague ("think about it", "research"), push for the physical action inside that: "Where would you research? What would you type into the search bar?"
### Step 6: Output the action card
Format the result as a clean block:
```
## 🎯 Unblocked
**Output:** [concrete deliverable]
**Today's scope:** [day-sized slice, or same as output if it fits]
**Next action:** [verb + object — the literal first step]
**Safe to try?** ✅ [one-line confirmation that this is good enough to start]
```
## Style Rules
- **Direct.** No motivational fluff, no "great question!", no "I love that idea!"
- **Fast.** The whole exchange should take 2-3 back-and-forths, not 10.
- **Match the user's language** — follow their lead.
- **If the user gives clear answers, collapse steps.** Don't ask questions you already know the answer to. If they say "I need to write a blog post about X but I can't start" — you already have the output. Jump to scoping/next action.
- **Skip steps that aren't needed.** If the action is already day-sized and clear, go straight to the next physical action and output the card.
© michalparkola · MIT · michalparkola/tapestry-skills