What problem does it solve?
When using the Shark non-blocking agent execution pattern, leftover state files including .shark-done, SHARK_LOG.md, pending.json and timings.jsonl accumulate in your workspace, creating clutter and making it difficult to distinguish between active and completed work sessions.
Core Features & Use Cases
- Automatic State File Removal: Deletes standard Shark state files (.shark-done, SHARK_LOG.md, shark-exec/state/pending.json) without extra user input.
- Protected Timing History: Only deletes the state/timings.jsonl file if you explicitly confirm, preserving valuable performance metrics by default.
- Use Case: After finishing a round of parallel task execution with the Shark pattern, use this skill to reset your workspace to a clean state before starting a new project, without losing useful timing data unless you choose to delete it.
Quick Start
Use the shark-clean skill to remove all leftover Shark state files from your current workspace, and confirm if you want to delete the timing history file.