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

doctor

Skill0 starsChanged 56 days agoMITView on GitHub

Diagnose StateNest itself when it seems not to be working — no context appearing at session start, checkpoints not saving, a project not being recognised. Use when the user reports StateNest misbehaving.

  • Installs packages

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use uninstall, cancel 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.
  • AnthropicSkill

    uninstall

    Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.

    Also in 6 projects that use this

  • woosikkimSkill

    cancel

    Clear any stale OMC-Slim state

    Also in 3 projects that use this

  • ibahgatSkill

    mode

    Inspect or switch omi operating mode/profile for speed, depth, autonomy, or strict quality gates.

    Also in 3 projects that use this

  • BlockSkill

    open

    Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.

    Also in 3 projects that use this

  • QinghongLinSkill

    editor

    Read analyst.json and detective.json, make all editorial decisions — what the blog argues, which findings matter, narrative arc and section structure. No visual design. Outputs editor.md (prose) and editor.json (structure with edt_xx IDs).

    Also in 3 projects that use this

  • MicrosoftSkill

    init

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Run statenest doctor with the Bash tool and show the user the result.

    line 8
  2. Distinctive:

    Every failing check prints the exact command that fixes it.

    line 9
  3. Very specific:

    If the user's current project is not being recognised, call statenest_current_project and check what it reports:

    line 11
  4. Distinctive:

    No git repository → confirm which directory they expect to be the project

    line 14
  5. Very specific:

    If statenest is not on the PATH at all, StateNest is not installed globally.

    line 16
  6. Very specific:

    If statenest doctor reports "Plugin build: compiled output missing", the plugin was installed from a source checkout that has not been …

    line 24

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

Diagnose StateNest

  1. Run statenest doctor with the Bash tool and show the user the result. Every failing check prints the exact command that fixes it.
  2. If the user's current project is not being recognised, call statenest_current_project and check what it reports:
    • "No registered project" with a git repository present → they need statenest add .
    • No git repository → confirm which directory they expect to be the project
  3. If statenest is not on the PATH at all, StateNest is not installed globally. The fix is npm install -g statenest, then statenest init.

Things worth knowing

  • The session-start brief only appears in a registered project. In an unregistered directory, staying silent is deliberate, not a bug.
  • Changes to what a session recorded appear at the next session start.
  • If statenest doctor reports "Plugin build: compiled output missing", the plugin was installed from a source checkout that has not been built. npm run build in that checkout fixes it.

Report what the checks actually said. Do not guess at causes beyond them.

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