Operational Framework
PassAudited by ClawScan on May 8, 2026.
Overview
This instruction-only skill provides a coherent local change-documentation workflow, with expected persistence and file-copy examples that users should apply carefully.
This skill appears safe to install as a local workflow aid. Before using it, decide what files belong in snapshots, avoid recording secrets in logs or briefings, and review any restore command before running it because it may overwrite workspace files.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A careless restore could replace current workspace files with older snapshot contents.
The restore example can overwrite files in the workspace. It is clearly presented as an example for the rollback workflow, but users should review paths before running it.
cp -r rollbacks/2026-05-08_2005/* <workspace>/
Use restore commands only after confirming the snapshot name, target directory, and files to be overwritten.
Private implementation details or mistakes could remain in local logs and influence later work if stored without review.
The framework intentionally stores decisions, TODOs, snapshots, and briefings for later reuse. This is aligned with the purpose, but persistent context can retain sensitive or outdated information.
"Never lose context" - Everything survives session restarts
Keep secrets out of decision logs and briefings, periodically prune old snapshots, and review persistent notes before relying on them.
