Skill lifecycle
The installer adds a lifecycle helper at~/.miles/bin/miles-skill.
Use
miles help for the installed CLI’s summary. Agents should run doctor --json when setup or capability support is unclear.
Compatibility aliases
These older names remain supported, but new scripts and docs should use the canonical command.status, sites, and use remain supported convenience commands. Use site-state when an agent needs the richer state, recovery, approval, plan, and connection details.
Agent hooks
The installed Miles skill can use host-agent hooks to surface interrupted runs and current authentication state. These hooks are part of the installed skill, not commands for a user or integration to call directly.Keeping integrations reliable
Use canonical names, request--json when your agent needs to branch on results, and handle the shared exit codes from Miles CLI reference. Run an update check at the start of a new session, but ask the user before installing an update or removing the skill.