agentleFS
Sign inStart free
AgentLTLAgentLTL/agentltl-claude-code/skills/status/SKILL.md

status

Skill1 starsChanged 32 days agoMITView on GitHub

Show the rules in force and what they blocked

183 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list 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.
  • StakeholderSenseiSkill

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 4 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 6 projects that use this

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 15 projects that use this

  • stotihvSkill

    knowledge

    Extracts knowledge from Amp threads and updates project docs. Use when asked to document recent work, sync docs after an epic, summarize what changed, or update AGENTS.md from thread history.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 151 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Run agentltl validate, then agentltl trace.

    line 11
  2. Distinctive:

    If the rule file has errors, show them first.

    line 16
  3. Very specific:

    trace: run agentltl trace and show the output.

    line 17
  4. Very specific:

    check <steps>: run agentltl check <steps> and explain each outcome.

    line 22

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

Report on the AgentLTL for Claude Code. Requested: $ARGUMENTS (empty means status).

  • status:
    1. Run agentltl validate, then agentltl trace.
    2. Summarise in a few lines:
      • which rules are in force, and their modes;
      • how many calls are recorded;
      • the recent interventions, and why.
    3. If the rule file has errors, show them first. Until they are fixed, nothing is enforced.
  • trace: run agentltl trace and show the output.
  • reset:
    1. Confirm with the user first, because it forgets which calls already happened. For example, tests already run will no longer count toward before rules.
    2. Then run agentltl reset.
  • check <steps>: run agentltl check <steps> and explain each outcome.

To pick packaged rules, use the /agentltl:setup skill. To add, change or remove rules, use the /agentltl:rules skill.

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