agentleFS
michalparkolamichalparkola/tapestry-skills-for-claude-code/unblock-action/SKILL.md

unblock-action

Skill557 starsChanged 12 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    It must fit in a day: If it's a multi-day project, carve off today's slice.

    line 14
  2. Distinctive:

    Good enough for now, safe enough to try: Don't obsess over long-term optimization.

    line 15
  3. Distinctive:

    Ask ONE question to make the output concrete:

    line 29
  4. Distinctive:

    If the user gives a fuzzy answer, sharpen it once.

    line 35
  5. Distinctive:

    If the output is clearly bigger than a day:

    line 39
  6. Distinctive:

    If it already fits in a day, skip this step.

    line 45
  7. Distinctive:

    Before moving to the next action, do a quick sanity check — but frame it correctly:

    line 49
  8. Distinctive:

    If they say something vague ("think about it", "research"), push for the physical action inside that: "Where would you research?

    line 63
  9. Distinctive:

    Direct: No motivational fluff, no "great question!", no "I love that idea!"

    line 80
  10. Distinctive:

    If the user gives clear answers, collapse steps: Don't ask questions you already know the answer to.

    line 83
  11. Distinctive:

    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.

    line 84

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. michalparkola/tapestry-skills★ 538100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.