agentleFS
aldisfaldisf/sg-stay-where/skills/uninstall/SKILL.md

uninstall

Skill2 starsChanged 14 days agoMITView on GitHub

Shut sg-stay-where down and remove it from the user's machine: background services, scheduled polls, the WhatsApp link and session, remote access, data and the repo. Use when the user wants to stop using it, start over, or clean up.

  • Deletes or force-pushes

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use doctor, config and 2 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.
  • MicrosoftSkill

    doctor

    Diagnose an Amplifier CLI environment through the CLI doctor agent. USE WHEN a user requests CLI runtime, settings or missing-capability inspection. DO NOT USE for project bugs or other hosts.

    Also in 6 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

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 7 projects that use this

  • +1 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    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. Distinctive:

    Ask what the user wants removed and confirm each deletion before running it.

    line 8
  2. Very specific:

    Stop any npm start still running.

    line 21
  3. Very specific:

    Remote access: If they set up Tailscale for their phone: tailscale serve status, then tailscale serve --https=8431 off (or the port it …

    line 27
  4. Distinctive:

    Browser and agents: Remove the bookmarklet if they added one, and any browser tool they configured only for polls.

    line 31

“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

Shut down and remove

Ask what the user wants removed and confirm each deletion before running it. Nothing here can be undone without a backup.

  1. Backup, if they want one. data/ holds projects, listings, chats and photos: cp -R data ~/sg-stay-where-backup-$(date +%Y%m%d). Tell them it contains private chats.
  2. Stop polls and the server.
    • macOS: launchctl bootout gui/$(id -u)/sg-stay-where.poll, launchctl bootout gui/$(id -u)/sg-stay-where.server, then rm ~/Library/LaunchAgents/sg-stay-where.*.plist.
    • Linux: systemctl --user disable --now sg-stay-where-poll.timer sg-stay-where.service, then delete those unit files in ~/.config/systemd/user/ (or remove a cron line).
    • Windows: Unregister-ScheduledTask sg-stay-where-poll, sg-stay-where-server -Confirm:$false.
    • Stop any npm start still running.
  3. Unlink WhatsApp. The user does this on their phone: WhatsApp → Settings → Linked devices → the sg-stay-where device → Log out.
  4. Delete the WhatsApp session. The user runs this themselves; agents never open or touch that folder: rm -rf ~/.config/sg-stay-where/, plus the folder in SSW_WA_AUTH_DIR if they set one.
  5. Remote access. If they set up Tailscale for their phone: tailscale serve status, then tailscale serve --https=8431 off (or the port it shows).
  6. Delete the data. rm -rf data data-demo.
  7. Browser and agents. Remove the bookmarklet if they added one, and any browser tool they configured only for polls. Chrome itself stays.
  8. Delete the repo last, from outside it: rm -rf <path>/sg-stay-where. The user runs this if you are working inside the folder.
  9. Report what was removed, what is left, and where the backup is.

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.