Invisible

Invisible

Create a brief invulnerable window to observe or pass through danger.

What This Skill Does

Use Invisible when you need a short protected interval to inspect, move, or recover without drawing fire. In this chip pack, Invisible is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Invisible. Hermes shelf: Defense and Recovery.

When To Use

• You need a quick read of a hostile or noisy system.
• The safest move is to pass through danger without engaging it.
• A temporary pause in exposure is enough to regain control.

Prerequisites

• These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.

Operator Inputs

• Name what you need to inspect, traverse, or validate during the low-exposure window.
• Say how long the safe window needs to last in practical terms.
• Describe what risks you are trying to avoid drawing attention from.
• State what you plan to do immediately after the window closes.

Procedure

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Collect the operator inputs below so the chip lands on the right panel.
3. Define the short window you need.
4. Use that window for observation or passage, not for grandstanding.
5. Drop the cloak before the protection becomes false confidence.
6. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A brief protected observation or transit step.
• A note on what was learned or traversed during the window.

Output Contract

• A short, explicit protected window for observation, transit, or careful action.
• A named purpose for the window and the exact step to perform inside it.
• An expiry condition so the operator does not overtrust the cloak.
• Verification that still shows what was learned or traversed.

Do Not Use For

• Long-running work that needs durable safety rather than a brief opening.
• Avoiding validation, logging, or accountability.
• Plans that depend on staying unseen indefinitely.

Pair With

• Invisible + Area Grab: cross the risky gap first, then take space once you are in position.
• Invisible + Repair: create a brief safe interval to patch the damaged panel.
• Invisible + Killer Eye: move through danger now, then leave a watcher behind on the lane.

Pitfalls / Guardrails

• Keep the metaphor anchored to a real operator move instead of drifting into lore.
• Invisible is temporary. Do not build a plan that assumes permanent immunity.
• Use it to reduce exposure, not to avoid necessary verification.
• Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.

Verification

• Check that the response includes every promised deliverable and leaves an inspectable audit trail.
• Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
• Confirm the window has a concrete start, purpose, and end condition.
• Confirm the task inside the window is small enough to finish before false confidence sets in.
• Confirm the response does not describe immunity beyond the stated short interval.
• Check that the metaphor still maps cleanly to a real operator mechanism.

Example Invocation

Use Invisible to give me a short low-exposure window to inspect this noisy system without triggering a bigger response.
Use Invisible so I can pass through the risky part of this workflow, verify one thing, and get out.