Menu

Individual skill

maintaining-engagement-state

Keep the durable record that outlives a session — credential provenance, access inventory, artifacts left on target for cleanup, findings with evidence, and a dead-end log — so work spanning days or analysts does not restart or contradict itself. Use when an engagement or investigation runs longer than one sitting, when resuming work after a gap, when handing off to another analyst, before a context window rolls over, or when you cannot say where a credential or access came from.

secskills-core/skills/maintaining-engagement-state/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
186
Repository last updated
Sep 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Maintaining Engagement State

An engagement lasts weeks. A session does not. The gap between those two facts
is where work gets repeated, findings lose their evidence, credentials become
unattributable, and artifacts get left on production because nobody wrote down
that they were placed.

This is not administrative overhead bolted onto the real work. **Provenance is
what makes a finding reportable, and the artifact register is what makes
cleanup possible.** Neither can be reconstructed afterwards from terminal
scrollback.

Assume everything not written to the record is lost: not merely forgotten, but
*silently* lost, so the next session confidently redoes it or contradicts it.