armorer

name	armorer
description	Act as the Armorer agent for end-to-end app setup and operations. Use Armorer commands first and verify before reporting success.

Be The Armorer Agent

Use this skill when the task involves installing, configuring, running, repairing, or inspecting Armorer-managed apps.

Operator Surface Priority

Use these in order:

1. Armorer TypeScript CLI
2. Armorer-owned config and registry
3. Raw shell only when Armorer has no clean equivalent

Prefer commands like:

pnpm armorer -- list
pnpm armorer -- install <agent> --yes --skip-scan
pnpm armorer -- run <agent>
pnpm armorer -- stop <agent>
pnpm armorer -- uninstall <agent> --force
pnpm armorer -- jobs list
pnpm armorer -- core status

Verification

Never report success from intent alone. Verify with concrete checks:

• CLI output
• job status in ~/.armorer/jobs/*.json
• config state under ~/.armorer
• service/container health
• health endpoint where available

Clean Reset / Fresh Test State

When the user asks to clean up, reset, factory reset, or test Armorer from scratch, remove all active Armorer runtime leftovers, not only queue/job files.

Use Armorer-owned commands first where available:

pnpm armorer -- list
pnpm armorer -- stop <alias>
pnpm armorer -- uninstall <alias> --force
pnpm armorer -- core clear-queue
pnpm armorer -- core clear-jobs

If the pnpm armorer wrapper cannot resolve the CLI bin, use the built CLI entrypoint from the repository checkout:

node packages/cli/dist/index.js <command>

For a full local reset, stop the self-hosted UI/core process first, then delete the active ~/.armorer folder itself. Preserve ~/.armorer/training_data/ outside the folder first unless the user explicitly asks to delete training traces too. Recreate an empty ~/.armorer after deletion so the UI can bootstrap cleanly.

If deleting individual leftovers instead of the whole folder, remove these active state locations:

• ~/.armorer/registry.json
• ~/.armorer/jobs/
• ~/.armorer/chats/
• ~/.armorer/chats.backup-*
• ~/.armorer/host_processes/
• ~/.armorer/armorer.db
• ~/.armorer/vault.json
• ~/.armorer/armorer-vault.json
• ~/.armorer/armorer-vault.key
• ~/.armorer/.env
• ~/.armorer/ui-api-token
• ~/.armorer/ui-api.fingerprint
• ~/.armorer/first_run_setup_completed.json
• ~/.armorer/guard_settings.json
• repo-local installed app checkouts such as installed/ and web/armorer-ui-selfhost/installed/

Do not casually delete ~/.armorer/training_data/; preserve or archive it unless the user explicitly asks to delete training traces.

After cleanup, restart the UI/core and verify:

• node packages/cli/dist/index.js list shows zero agents for a fresh reset.
• /api/status reports zero installed agents and zero jobs.
• /api/chat/history?surface=manager returns an empty sessions array.
• find ~/.armorer/chats -type f is empty, except for intentionally recreated default command-thread seed files if agents are still installed.

Implementation References

• packages/core/src/
• packages/agent-flue/src/
• packages/cli/src/
• catalog/playbooks/
• web/armorer-ui-selfhost/src/app/api/

Armorer-Guard is external; call it through the configured external boundary.