agentleFS
Sign inStart free
AlenroyfeildAlenroyfeild/ai-dev-workspace/skills/pickup/SKILL.md

pickup

Skill0 starsChanged 26 days agoMITView on GitHub

Show where a workspace task stands (saved next action, blockers, evidence) when the user asks to resume or asks for status without giving a concrete task.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-review, discover and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SkyWalker2506Skill

    ai-review

    This skill should be used when the user asks to "review a PR", "code review", "AI review", "check the pull request", or asks about automated review via OpenRouter or Gemma. Also activates when setting up GitHub Actions for PR review.

    Also in 3 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 3 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 5 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Before continuing, compare the repository and environment state against the saved handoff to check for drift:

    line 9
  2. Distinctive:

    verify whether uncommitted work or unpushed commits have changed

    line 11
  3. Distinctive:

    check whether failing checks or broken tests noted in the handoff have been resolved or new failures appeared If the branch changed, …

    line 12
  4. Distinctive:

    If the branch changed, uncommitted work drifted, or test status differs from the saved Evidence, flag the drift to the user before resuming.

    line 13
  5. Distinctive:

    If the user asked you to continue or finish the task, go on and do the saved next action (noting any detected drift first).

    line 15

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “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

If a "Saved task memory" brief is already in context, do not run ws brief again; treat its Next action and Blockers as already read, and request only missing sections such as Evidence or Handoff. Otherwise run ws brief, then read Next action, Blockers and Handoff by default: ws task show <ID> --section "Next action" --section Blockers --section Handoff, or call MCP read_task (which selects those sections by default). Request the full record only when needed: omit --section for ws task show, or pass sections: [] to MCP read_task. Do not reread the whole vault.

Before continuing, compare the repository and environment state against the saved handoff to check for drift:

  • compare the current branch and working tree (git status -sb) with the saved handoff
  • verify whether uncommitted work or unpushed commits have changed
  • check whether failing checks or broken tests noted in the handoff have been resolved or new failures appeared If the branch changed, uncommitted work drifted, or test status differs from the saved Evidence, flag the drift to the user before resuming.

If the user asked you to continue or finish the task, go on and do the saved next action (noting any detected drift first). Otherwise state the next action, blockers, relevant evidence, and any detected drift, and ask whether to continue.

Download now (ZIP)

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.

Check your setup, free