agentleFS
Sign inStart free
DeepusleepyDeepusleepy/t3-tots/skills/t3-checkup/SKILL.md

t3-checkup

Skill110 starsChanged 17 days agoMITView on GitHub

Health check of T3 Code and the computer it runs on. Use for "health", "checkup", "is T3 ok", "is my computer ok", "why is T3 slow", or the Weekly health check routine.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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 t3q.py health on every computer.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Follow the t3-tots-rules skill (skills/t3-tots-rules/SKILL.md). Steps that use the box, ListMachines, routines, cards or SendToUser are Grok Bot only; other agents follow t3-tots-rules "Grok Bot only". Read-only. For the Weekly health check routine, t3-getting-started section 6 says when to add the t3-cleanup scan.

  1. Run t3q.py health on every computer.
  2. Per computer, give one line with these parts:
    • T3 running (pid), port and bind address
    • stuck runs (live over 1 hour with no activity for 30 minutes), held queues, and stale pending requests (over 24 hours)
    • T3 data folder size, disk free, memory available, and CPU load against the core count
  3. Warn when one of these is true:
    • T3 listens on 0.0.0.0 or ::, which makes it reachable from the network. Suggest 127.0.0.1. If the user says network access is fine, save that and don't warn again.
    • Disk free is under 10%, memory available is under 10%, load is above the core count, or the data folder is over 20 GB.
  4. On macOS, report free space only. For used space that matches System Settings, offer t3-cleanup.
  5. Suggest fixes. Apply none. A held queue isn't stuck: someone held it on purpose, so offer to resume or cancel it. Stale requests on agent-spawned threads usually belong to finished work; suggest dismissing them in T3.

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