agentleFS
n2nsn2ns/hyper-hand/.agents/skills/dev-install/SKILL.md

dev-install

Skill5 starsChanged 24 days agoApache-2.0View on GitHub

Installs the current HyperHand checkout on the Windows host without UAC and brings the guest agents up to date — scripts/dev-install.sh, the recovery steps for its failures, vm_update_agent and the version and hash checks. Use whenever a changed build must run for real (before a VM check, an acceptance run or after a fix), and when a tool returns agent_outdated.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. yusufalikync/ccs★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never kill HyperHand processes by name.

    line 29
  2. Very specific:

    When the installer changed: /mnt/c/Windows/System32/sc.exe qfailure HyperHandService shows RESET_PERIOD 86400 and restarts after 5000, …

    line 45

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Installing a development build

The running service and tray are the installed copies under %ProgramFiles%\HyperHand, and each guest runs its own agent; a build in build/ changes nothing until it is installed. Rules: AGENTS.md; details: Building.

1. Install on the host

From the repository root in WSL:

scripts/dev-install.sh             # extra arguments go to dev-install, e.g. --timeout 300

It prints built <version>; remember the version for step 3. Exit code 0 means the installed files equal the build, the service runs and one tray is up. Installing interrupts MCP connections, so finish running tool calls first. On failure:

MessageWhat to do
the task is not registeredStop and ask the user to run scripts\dev-install-setup.ps1 once from an elevated PowerShell. Never install with a UAC prompt instead.
the task runs <other path>, not ...\HyperHandDev\hyperhand.exeStop and ask the user to run, elevated, schtasks /Delete /TN "HyperHand Dev Install" /F and then scripts\dev-install-setup.ps1.
a development install is queued or runningWait and run the script again; never stop the task.
the installer failed, with log linesRead the lines. If the service is left stopped, build/dev-install/hyperhand.exe dev-install --no-build reinstalls the same build and restores it.
the install task did not finish within N sInspect it in the log (%LOCALAPPDATA%\HyperHand\hyperhand.log) before retrying; it was not stopped.

Never kill HyperHand processes by name; the installer replaces the service and the tray.

2. Update the guest agents

For each VM the work will use (the argument, or the VMs named in AGENTS.md) that is running:

python3 client/hyperhand_client.py --vm <vm> vm_update_agent

An agent that does not answer needs vm_install_agent instead. A VM that is off keeps its old agent; tools refuse it with agent_outdated after it starts, and this step is repeated then.

3. Check

  • python3 client/hyperhand_client.py --vm <vm> vm_status: agent.version is the version printed in step 1.
  • python3 client/hyperhand_client.py --vm <vm> vm_doctor: every check ok.
  • When the installer changed: /mnt/c/Windows/System32/sc.exe qfailure HyperHandService shows RESET_PERIOD 86400 and restarts after 5000, 30000 and 60000 ms, and sc.exe qfailureflag HyperHandService shows TRUE (Host tray). Ending the service process to watch the restart needs an elevated prompt; ask the user (taskkill /PID <pid> /F, then sc query HyperHandService after 5 s).

For an acceptance run, also compare the hashes as described in the vm-acceptance skill.

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.