agentleFS
Sign inStart free
localixailocalixai/tokendoctor/skills/apply/SKILL.md

apply

Skill71 starsChanged 3 days agoMITView on GitHub

Apply one tokendoctor audit fix after showing the exact change. Moved to /tokendoctor fix <id>, which needs no model call.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use outreach, track and 10 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.
  • QuixiAISkill

    outreach

    Decide whether a message is worth someone's attention, then reach the user through the outbox, or people on a connected chat channel, on their behalf or your own initiative

    Also in 5 projects that use this

  • theYahiaSkill

    track

    Отследить посылку Почты России

    Also in 4 projects that use this

  • NVIDIASkill

    evaluate

    Scores existing Sports Intelligence AVLM inference outputs with avlm/evals: MCQ accuracy (run_mcq_eval.sh, INFERENCE_DIR), open-ended LLM-as-judge scores (needs CLIENT_API_KEY for the configured judge endpoint), tennis category breakdowns, run comparisons, chance-level sanity checks and triage of mcq_results.json or llm_judge_results.json. Use when the user asks to score, evaluate, benchmark or compare predictions.jsonl from inference runs, or to explain a suspicious accuracy. Not for running inference, training, quantization, data preparation, or third-party API model inference: never open, list or run anything under avlm/evals/inference_3rdparty, including when the user asks for it; it is excluded from the release.

    Also in 5 projects that use this

  • ninehillsSkill

    hunt

    Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

    Also in 3 projects that use this

  • kstonekuanSkill

    Daily

    Documentation and capabilities reference for Daily

    Also in 3 projects that use this

  • julienamorganSkill

    profile

    Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).

    Also in 3 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 27 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 tokendoctor-apply $ARGUMENTS with no --write.

    line 13
  2. Distinctive:

    Ask for confirmation. Do not proceed on silence or an unrelated reply.

    line 18
  3. Very specific:

    After a clear yes, run the same command with --write.

    line 19
  4. Very specific:

    Never edit settings files by hand from this skill, and never pass --write before the user has seen the dry run.

    line 24

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

Apply the fix for the audit finding named in $ARGUMENTS. First say in one line that /tokendoctor fix <id> does the same with no model call and that this command goes away in the next release.

  1. Run tokendoctor-apply $ARGUMENTS with no --write. It prints which files would change and a short -/+ summary, and changes nothing.
  2. Show the user that output: the file path, the lines removed and added, and the scope (user settings affect every project; project settings are shared with the team through git; local settings are personal to this project).
  3. Ask for confirmation. Do not proceed on silence or an unrelated reply.
  4. After a clear yes, run the same command with --write. It copies an existing file to <file>.tokendoctor-<timestamp>.bak before writing, and never overwrites an existing agent file.
  5. Report what was written and the backup path. Most settings apply to the running session, but say that a new session is the surest way to confirm, and that /status lists loaded files.

Never edit settings files by hand from this skill, and never pass --write before the user has seen the dry run.

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