shark-clean

Remove Shark pattern state files while preserving timings.jsonl on confirmation.

12|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/keugenek/shark --skill shark-clean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shark-clean
Source: https://github.com/keugenek/shark/tree/main/commands/shark-clean
Command: npx skills add https://github.com/keugenek/shark --skill shark-clean

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about shark-clean

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up leftover state files from parallel agent execution?

To clean up leftover workspace state files from parallel agent execution, remove accumulated files like .shark-done, SHARK_LOG.md, and pending.json to eliminate clutter and reset between project runs.

What is the Shark non-blocking agent execution pattern?

The Shark non-blocking agent execution pattern is a development workflow for parallel task execution that generates state files like .shark-done, SHARK_LOG.md, and pending.json to track active and completed work sessions.

How do I preserve timing history data when clearing workspace clutter?

To preserve timing history data when clearing workspace clutter, you must explicitly confirm before deleting the timings.jsonl file, ensuring valuable performance metrics are retained by default during state cleanup.

Can I use an automated cleanup tool to reset my development workspace state?

Yes, you can use an automated cleanup tool to reset your development workspace state by automatically deleting standard Shark execution files without extra input, requiring confirmation only for protected timing history.

Do I need to manually delete pending.json and SHARK_LOG.md files between project runs?

No, you do not need to manually delete pending.json and SHARK_LOG.md files between project runs; automated state file removal handles these standard Shark execution artifacts to instantly reset your workspace.