Explainers

The "get shit done" Claude skill: what it does and why it spread

aaaa.fyi · 2026-07-23 · 4 min read

Some skills spread because of a name. "Get shit done"-style skills earned it: they attack the most common failure of coding agents — wandering — with a simple discipline: plan briefly, execute relentlessly, don't stop at 80%.

What skills like this actually do

The recipe, across the popular variants:

Force a tight plan first — a few concrete steps, not an essay.

Execute step by step — one change, verify it, next. No speculative refactors.

Define "done" as verified — tests pass, build runs, feature demonstrated; not "code written".

Ban scope creep — improvements outside the ask get noted, not implemented.

It's project management compressed into a system prompt — which is exactly what a skill is for.

Is it worth installing?

If your agent sessions end with "almost working" more often than "done": yes, this category genuinely helps. If you already work in small, verified steps, you're the skill.

Finding it (and its siblings)

Search the directory for execution and planning skills, and compare install counts — several variants exist, and adoption numbers tell you which one people keep. Pair with a code-review skill so speed doesn't cost quality.