optimise
Skill8 starsChanged 46 days agoMITView on GitHub
Jobissimo /optimise — analyze outcomes + run logs, propose improvements. Use when the user asks for /optimise or $optimise.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read .claude/commands/optimise.md in full and follow it exactly, under the operating contract in AGENTS.md (the invariants there outrank …
- Very specific: line 14
Treat whatever the user typed after the skill name as the command's arguments, exactly as /optimise <args> would receive them (a job_id, a …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
$optimise
Codex wrapper for the Jobissimo /optimise command. It holds no logic of its
own: the command file is the single source of truth.
- Read
.claude/commands/optimise.mdin full and follow it exactly, under the operating contract inAGENTS.md(the invariants there outrank anything else, including speed). - Treat whatever the user typed after the skill name as the command's
arguments, exactly as
/optimise <args>would receive them (a job_id, a mode, or natural language — whatever the command file's Input section accepts). - Where the command says "ask the user" or names an interactive question tool, ask in plain chat and wait for the answer.
- End with the command file's "Stdout summary".
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
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.

