agentleFS
Zack-GroganZack-Grogan/agentos-foundation/.agents/skills/optimize/SKILL.md

optimize

Skill0 starsChanged 2 months agoMITView on GitHub

Improve responsiveness without hiding work or weakening truth.

76 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use policy-init.

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.
  • open-coder-aiSkill

    policy-init

    Create conformant Chock policy from request. args(request, target_path,

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 73 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the spatial contract.

    line 7
  2. Distinctive:

    Verify interaction latency and unchanged data/failure semantics after the change.

    line 11

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

Original AgentOS-specific procedure; not a vendored upstream skill. Read the spatial contract. Use visual grammar for styling and interactions for behavior; load only the relevant reference.

  1. Measure the actual slow action or rendering path before changing it.
  2. Bound graph neighborhoods, lazy-load inspectors and avoid provider calls during render.
  3. Verify interaction latency and unchanged data/failure semantics after the change.

Deliver changed artifacts or a concrete review with evidence. Preserve canonical state and permission boundaries. Do not make the screenshot more attractive by hiding real failures.

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.