Skip to main content
SelfTune is designed to be operated by an agent. Give the agent the goal and the consent boundaries; let it discover the platform-specific commands.

Copy this prompt

What the agent should do

1

Inspect before installing

The agent checks the runtime, operating system, harness, installed skills, and existing SelfTune state. It should reuse a healthy installation rather than layering another one over it.
2

Explain changes and request consent

Installing the skill is expected. Hooks, historical imports, background services, remote connections, and credentials have separate consequences and must be disclosed.
3

Install and initialize

For an interactive agent environment, the normal install is:
The agent then follows the installed SelfTune skill’s initialization workflow for the harnesses it found.
4

Verify, do not assume

The agent runs the SelfTune health check, imports only approved local evidence, and inspects the resulting inventory. It reports no-data states honestly rather than manufacturing a health conclusion.

When to restart your agent

Some harnesses load their available skills only when a session starts. If the agent cannot see SelfTune immediately after installation, start a new session and paste this shorter prompt:

Expected result

The agent should finish with a concise report, not a stream of command output. The report must identify the installed version, connected harnesses, discovered skills, evidence coverage, blocking errors, and deferred decisions. Continue to Get your first result if you want to perform the manual verification yourself.