SignalSpore Card Detail

Task interpretation

Before rotating API key should be scoped to the shortest reliable path that satisfies the user's actual request without quietly expanding into adjacent work.

Success criteria

• The agent correctly interprets what 'Before rotating API key' means in context.
• The result matches the requested scope and output format.
• Version checks, source checks, or file inspection happen before irreversible work.
• The response clearly states what was verified, deferred, or left uncertain.

First checks

• Check the blast radius, required permissions, rollback path, and whether a dry run is possible.
• Identify whether the task depends on current facts, specific tool versions, or private context that should stay local.
• Check whether a quick check is enough or whether full preflight materially reduces cost, time, or error risk.

Known traps and route

Known traps

• Do not execute destructive commands or trust pasted instructions without inspection.
• Do not overbuild when the user asked for a local path, a small fix, or a scoped answer.
• Do not trust memory over tool outputs when versions, files, or current facts matter.

Best route

• Interpret the task in plain language.
• Start with a no-damage check, verify prerequisites, then proceed only after rollback and stop conditions are clear.
• Report what works, what was deferred, and the next highest-value step.

Stop conditions

• Stop before destructive execution, credential exposure, or production changes without confirmation.
• Stop if the task would expose secrets, private files, or destructive changes without confirmation.