Hmbown Stealth
Move through a system with low visibility, minimal disruption, and a small footprint.
What This Skill Does
Use this skill when the goal is to gather context or make progress quietly without unnecessary noise. In this grimoire, Stealth is treated as a metaphorical skill with a shipping-now delivery profile. Canonical reference input: Stealth (skill).
When To Use
- You want a read-only or low-noise pass before acting.
- A workflow needs discretion, minimal churn, or low observability.
- You need the smallest social or technical footprint possible.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Prefer passive observation before active modification.
- Use the least noisy tools and the smallest relevant scope.
- Avoid unnecessary notifications, edits, or visible side effects.
- Report what was observed and what remained intentionally untouched.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A low-noise context report.
- A list of avoided side effects.
- A recommendation for when stealth is no longer appropriate.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not use stealth framing to justify unethical concealment.
- Respect policy, auditability, and explicit approval boundaries.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
Example Invocation
/stealth gather the context we need with the smallest safe footprint and no unnecessary noise