agentleFS
Sign inStart free
kernelkernel/hypeman/skills/optimize-initializing-speed/SKILL.md

optimize-initializing-speed

Skill373 starsChanged 22 days agoMITView on GitHub

Use when optimizing VM Initializing-to-Running latency while preserving functionality and low implementation complexity.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    Keep Running gated only on program-start + agent-ready markers.

    line 12
  2. Distinctive:

    Add fast-path checks (skip work when already installed/valid).

    line 15
  3. Very specific:

    Keep guest-agent gate strict unless skip_guest_agent=true.

    line 19

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

Optimize Initializing Speed

Goal

Minimize Create/Start -> Running latency without removing functionality. Base your decisions on what to optimize by using real measurements.

Priority Levers

  1. Keep Running gated only on program-start + agent-ready markers.
  2. Replace readiness polling with event-driven signaling
  3. Move heavy non-critical setup (kernel headers) off the critical path (ask permission from user if moving logic to async / could be still processing after Running is set).
  4. Add fast-path checks (skip work when already installed/valid).
  5. Parallelize independent init stages with simple barriers (no DAG engine). Avoid parallel tasks that are likely to conflict.

Guardrails

  • Keep guest-agent gate strict unless skip_guest_agent=true.
  • Preserve lifecycle semantics and blocked/allowed operations in Initializing.

Measurement Protocol

  1. Measure baseline and candidate on the same host with the same 5-run harness.
  2. Report per-run samples + median/mean/min/max.
  3. Validate full regression suite before merge.

Required Outputs

  • Exact before/after latency numbers.
  • Short breakdown of biggest contributors.
  • Risk notes, if any

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