agentleFS
Sign inStart free
Emin4ikEmin4ik/StateNest/skills/resume/SKILL.md

resume

Skill0 starsChanged 56 days agoMITView on GitHub

Pick a project back up. Use when the user says "resume X", "what was I doing in X", "where did I leave off", "catch me up on X", or returns to a project after a break. Loads what the project is, what was recently done, what is blocked, what is next, and where it lives.

58 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pause, report and 9 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.
  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 7 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 7 projects that use this

  • MicrosoftSkill

    config

    Show or change TokenEconomizer's settings: turn micro-skills, tool pruning or the loop guard on or off, or tune them, for this repository or (with --global) every repository. Use when the user asks to configure, enable or disable TokenEconomizer or one of its mechanisms.

    Also in 3 projects that use this

  • sahinSkill

    execute

    Also in 4 projects that use this

  • u9401066Skill

    bug-fix

    Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.

    Also in 3 projects that use this

  • GitHubSkill

    state-management

    CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.

    Also in 3 projects that use this

  • +2 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call statenest_get_resume_context with the project name the user gave.

    line 13
  2. Very specific:

    If they gave no name, call statenest_current_project first to see which project this directory belongs to.

    line 14
  3. Distinctive:

    Never pick one for them.

    line 18
  4. Distinctive:

    Read the result and tell the user, in a few sentences:

    line 20
  5. Distinctive:

    Write the summary for someone who has genuinely forgotten.

    line 30
  6. Distinctive:

    If the context mentions a decision, mention it too — decisions exist specifically so a later session does not undo them by accident.

    line 34
  7. Distinctive:

    If there is no recorded history yet, say so plainly rather than padding.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 51 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

Resume a project

Load everything needed to continue work on a project, then summarise it for the user.

Steps

  1. Call statenest_get_resume_context with the project name the user gave.
    • If they gave no name, call statenest_current_project first to see which project this directory belongs to.
    • Partial names work: "world" resolves "world-war-rts". If the tool reports the name is ambiguous, show the user the candidates and ask which they meant. Never pick one for them.
  2. Read the result and tell the user, in a few sentences:
    • what this project is, if it is not obvious
    • what was last done, and when
    • what is blocked
    • what the next action is
  3. Then offer to start on the top next action. Do not start without being asked.

What matters

Write the summary for someone who has genuinely forgotten. "Last worked on the refinery AI three weeks ago; it still fails to rebuild after being destroyed, and that is the next thing" is useful. "This project has 4 checkpoints" is not.

If the context mentions a decision, mention it too — decisions exist specifically so a later session does not undo them by accident.

If there is no recorded history yet, say so plainly rather than padding.

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