agentleFS
Emin4ikEmin4ik/StateNest/skills/projects/SKILL.md

projects

Skill0 starsChanged 55 days agoMITView on GitHub

List the user's projects, or find ones matching a condition — active, paused, stale, deployed. Use when they ask "what projects do I have", "which ones haven't I touched", "show my active work", or are trying to remember whether a project exists.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tasks.

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.
  • genomewalkerSkill

    tasks

    Browse and resume tasks, threads, and background jobs across sessions

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    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_list_projects.

    line 9
  2. Very specific:

    If the user is looking for something specific and cannot remember the name, use statenest_search instead — it searches their own …

    line 14
  3. Distinctive:

    Never suggest archiving or deleting a project on your own.

    line 18

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

List projects

  1. Call statenest_list_projects. Use status or stale_days to narrow it rather than listing everything and filtering in your reply.
  2. Present the result compactly: name, when it was last active, and the current focus if there is one.

If the user is looking for something specific and cannot remember the name, use statenest_search instead — it searches their own checkpoints, decisions and notes.

Never suggest archiving or deleting a project on your own. Staleness is information, not a recommendation; the user decides.

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.