agentleFS
chanukawijeratna-aichanukawijeratna-ai/claude-session-hub/skills/hub-wipe/SKILL.md

hub-wipe

Skill1 starsChanged 11 days agoMITView on GitHub

Permanently delete this project's Session Hub (all agents, hubs, messages, tasks and file claims). Use only when the user runs /hub-wipe or explicitly asks to wipe or delete the whole Session Hub for this project.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Run with the Bash tool, without --confirm:

    line 12
  2. Distinctive:

    If their message is exactly the hub name, run:

    line 27
  3. Distinctive:

    After a successful wipe:

    line 34
  4. Distinctive:

    do not start a hub listener, and do not run other hub commands.

    line 35
  5. Distinctive:

    if you saved a Session Hub memory for this project, delete it (and its line in your memory index).

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Wipe the Session Hub

This deletes everything the Session Hub knows about this project. It cannot be undone. The user must confirm by typing the project's hub name in the chat. Do not use AskUserQuestion for this, and never treat "yes", "ok" or "go ahead" as confirmation.

The hub CLI is bin/hub.js, two folders up from this skill's base directory (shown above as "Base directory for this skill").

  1. Run with the Bash tool, without --confirm:
    node "<plugin root>/bin/hub.js" wipe
    This deletes nothing. It prints what would be lost and the project's hub name (its slug, for example my-app-3f2a).
  2. Tell the user, in a few lines:

    • what will be deleted (use the numbers it printed) and that there is no undo;
    • that every agent's listener stops and the project leaves the Session Hub home page;
    • that to use the hub again they run /hub and start from nothing;
    • to confirm, they type the hub name exactly, as their whole message: show it on its own line in a code span.

    Then stop and wait for their reply. Do not run anything else.

  3. When they reply:
    • If their message is exactly the hub name, run:
      node "<plugin root>/bin/hub.js" wipe --confirm <slug>
      The CLI checks that the user typed it (a hook records the user's message), so it refuses if you try to confirm on their behalf.
    • Anything else, including a near miss: say the wipe is cancelled and nothing was deleted.
  4. After a successful wipe:
    • do not start a hub listener, and do not run other hub commands;
    • if you saved a Session Hub memory for this project, delete it (and its line in your memory index);
    • tell the user it's gone and that /hub starts a fresh hub.

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.