park Skill
Capture unfinished work, list parked items, or resume parked work.
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
park is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around utility skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is Claude Code Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in liamlin/claude-skill-park, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
---
name: park
description: >-
Capture unfinished work, list parked items, or resume parked work.
Use when the user says "park this", "save remaining tasks", "handoff",
"what's parked", "resume parked work", "park done", "what's left to do",
"save progress before clearing", or invokes /park.
user-invokable: true
args:
- name: subcommand
description: >-
"list" to show parked items, "resume" to pick up parked work,
"done <slug>" to mark complete, or a summary string to park new work.
If omitted, interactively captures current work.
required: false
---
# /park — Capture, View & Resume Unfinished Work
Persist structured parked files so any future agent (in any session or worktree) can discover and resume work.
## Routing
Inspect the `subcommand` argument and run the matching flow:
| Argument | Flow |
|---|---|
| *(none)* | **Park** — infer from context, draft, confirm, write |
| `"quoted text"` or any text that isn't `list`/`resume`/`done` | **Park** — use text as title |
| `list` | **List** — show all parked items |
| `resume` | **Resume** — pick an item, create tasks, mark in-progress |
| `done` or `done <slug>` | **Done** — mark a parked item completed |
---
## Park Flow
This is often the **last action before the user clears the session**. Be aggressive about inferring — do not ask open-ended questions. One confirmation round max.
### Step 1: Gather Context
Run in parallel: `git log --oneline -20`, `git diff --stat HEAD`, `git branch --show-current`
Also:
- Glob the project memory directory for existing `parked_*.md` files to av
...