agentleFS
Sign inStart free
ViaknoxViaknox/tune-up/skills/set-up-tune-up/SKILL.md

set-up-tune-up

Skill0 starsChanged 22 days agoMITView on GitHub

Use when the user says "set up Tune-Up", or wants a bot that evaluates and improves their other Grok bots. Confirm first, ask four short questions, create the bot, verify its instructions, then run one supervised review.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create anything before the user says yes.

    line 22
  2. Distinctive:

    Delete, rename, or change any existing bot during setup.

    line 23
  3. Distinctive:

    Create a routine without a separate yes.

    line 26
  4. Very specific:

    Fill in the answers: Read tune-up/INSTRUCTIONS.md.

    line 38
  5. Very specific:

    Create the bot: Use Grok Bot's create-bot tool if you have one.

    line 40
  6. Very specific:

    Offer a routine: Ask if Tune-Up should run a review on the schedule the user chose.

    line 46
  7. Very specific:

    Supervised first review: Ask Tune-Up to review one bot the user picks.

    line 48

≈ “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

Set up Tune-Up

Tune-Up is a bot that checks the user's other Grok bots and suggests small fixes. It uses the skill index to keep their instructions short. Its full instructions are in tune-up/INSTRUCTIONS.md in this plugin (the text inside the box).

Do not

  • Create anything before the user says yes.
  • Delete, rename, or change any existing bot during setup.
  • Invent click paths in the Grok Bot app. Use the bot-creation ability Grok Bot gives you.
  • Shorten, summarize, or send part of the instructions. Send the full text.
  • Create a routine without a separate yes.

Steps

  1. Confirm. Say in one or two lines what Tune-Up is: a new bot, named Tune-Up, that reviews the user's bots and shows proposed changes before anything is applied. Ask if you should create it. Stop until they say yes.
  2. Ask four short questions. Offer the defaults so the user can just say "defaults".
    • Which bots may it review? Default: all of them.
    • What behavior is sacred and must never change? Default: each bot's purpose.
    • How much freedom? Suggest only, or apply after a yes. Default: suggest only.
    • How often should it review? Default: weekly.
  3. Fill in the answers. Read tune-up/INSTRUCTIONS.md. Take the full text inside the box. Replace only the four lines under SETUP CHOICES with the user's answers. Change nothing else. Write the result to a file. Check it is under 20,000 characters.
  4. Create the bot. Use Grok Bot's create-bot tool if you have one. If not, ask Grok Bot to create a new bot. Name: Tune-Up. Title: Bot that tunes up other bots. Instructions: the full text from your file.
  5. Give it its mascot. Set the new bot's profile picture to tune-up/brand/tune-up-avatar-512.png (the Tune-Up raven sticker, which reads on dark and light screens). Use Grok Bot's avatar or profile tool if you have one. If you can't set it, tell the user where the file is so they can set it. Never redraw, recolor, or crop the raven.
  6. Verify. Re-read the new bot's live instructions. Pass means an exact match with your file. If it does not match, say so and fix it before going on. Do not call setup done until this passes.
  7. Offer a routine. Ask if Tune-Up should run a review on the schedule the user chose. Create the routine only after a yes. Before scheduling, run one review by hand and show the output.
  8. Supervised first review. Ask Tune-Up to review one bot the user picks. Show every proposed change in full. Apply nothing until the user says yes to that change.

Success check

Worked if: a bot named Tune-Up exists with the raven mascot as its picture (or the user was told where the file is), its live instructions exactly match the filled-in text, no other bot changed, and the user saw the first review's proposed changes before anything was applied.

Fail if: a bot was created without a yes, the instructions were cut or summarized, or any existing bot was changed, renamed, or deleted.

Tune-Up, by Viaknox™. Code and text MIT licensed; brand art is not. Viaknox and Agent Tune-Up are trademarks of Viaknox Holding LLC; see TRADEMARK.md. Not affiliated with or endorsed by SpaceXAI (xAI).

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