agentleFS
tovrleaftovrleaf/openkata/.agents/skills/openkata-optimize-skills/SKILL.md

openkata-optimize-skills

Skill1 starsChanged 17 days agoMITView on GitHub

Improve skills to 95%+ review score with passing evals. Use when the user says "optimize skills", "fix scores", "get skills to 95%", or wants to batch-improve skill quality across the repo.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    When multiple skills are selected, run them as parallel subagents.

    line 29
  2. Very specific:

    Run tessl commands without asking for confirmation.

    line 38
  3. Very specific:

    Do not add repo-internal boundaries (publishing, releasing, tagging) to distributable skills.

    line 40
  4. Very specific:

    After optimization, persist the final score to .tessl-plugin/plugin.json.

    line 43
  5. Very specific:

    Read scores from plugin.json to find targets

    line 49
  6. Distinctive:

    Run tessl lint, review, optimize

    line 50
  7. Distinctive:

    Update create-skill with learned patterns

    line 52
  8. Distinctive:

    Commit improvements per skill

    line 53

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

Optimize Skills

Improve skills to 95%+ review score with passing evals.

Usage

optimize skills

Workflow

  1. Select targets — Ask the user: "All skills below 95%, or a specific skill?" If all, read the score field from each skills/*/.tessl-plugin/plugin.json and list those below 95%. If specific, use the named skill.
  2. Optimize — For each target, follow openkata-review-skill (lint, review, optimize, checklist) then openkata-eval-runner (generate scenarios, run evals). Iterate until both pass 95%+, maximum 3 iterations. If still below after 3 rounds, report the final score and stop. When multiple skills are selected, run them as parallel subagents.
  3. Learn — If you discovered a pattern that consistently improves scores, update skills/create-skill/SKILL.md so future skills benefit.
  4. Commit — One commit per skill.

Constraints

  • Run tessl commands without asking for confirmation.
  • Maximum 3 optimization iterations per skill.
  • Do not add repo-internal boundaries (publishing, releasing, tagging) to distributable skills. Those belong in openkata-skill-conventions.
  • After optimization, persist the final score to .tessl-plugin/plugin.json.

Boundaries

DOES:

  • Read scores from plugin.json to find targets
  • Run tessl lint, review, optimize
  • Generate eval scenarios and run evaluation
  • Update create-skill with learned patterns
  • Commit improvements per skill

Does NOT:

  • Create new skills
  • Publish or release skills
  • Modify skills scoring 95%+

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.