shark-clean
Clean up shark state files (.shark-done, SHARK_LOG.md, pending.json, timings.jsonl)
Best use case
shark-clean is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Clean up shark state files (.shark-done, SHARK_LOG.md, pending.json, timings.jsonl)
Teams using shark-clean should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/shark-clean/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How shark-clean Compares
| Feature / Agent | shark-clean | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Clean up shark state files (.shark-done, SHARK_LOG.md, pending.json, timings.jsonl)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Shark Clean Remove shark state files from the skill base directory: - `.shark-done` - `SHARK_LOG.md` - `shark-exec/state/pending.json` - `state/timings.jsonl` (only if user confirms — timing history is valuable) Report what was cleaned.
Related Skills
shark-exec
No description provided.
shark-status
Check status of shark-exec background jobs, .shark-done, and SHARK_LOG.md
shark-loop
Run shark.ps1/shark.sh loop enforcer with OS-level timeout per turn
shark-autotune
Analyse shark timing history and recommend optimal SHARK_LOOP_TIMEOUT and SHARK_MAX_LOOPS settings
shark
No description provided.
performing-network-traffic-analysis-with-tshark
Automate network traffic analysis using tshark and pyshark for protocol statistics, suspicious flow detection, DNS anomaly identification, and IOC extraction from PCAP files
performing-network-forensics-with-wireshark
Capture and analyze network traffic using Wireshark and tshark to reconstruct network events, extract artifacts, and identify malicious communications.
analyzing-network-traffic-with-wireshark
Captures and analyzes network packet data using Wireshark and tshark to identify malicious traffic patterns, diagnose protocol issues, extract artifacts, and support incident response investigations on authorized network segments.
repo-cleanup
Use when a repository needs cleanup of dead code, build artifacts, unused dependencies, outdated docs, or stale tests - provides safe cleanup workflows, validation steps, and reporting templates for code, deps, docs, tests, and sprint archives.
clean-code
Write clean, readable, and maintainable code following principles from Robert C. Martin's "Clean Code" and Object Calisthenics. Use when writing, reviewing, or refactoring code to improve naming, function design, formatting, error handling, and class structure. Includes code smell detection and refactoring guidance.
clean-comments
Remove unnecessary, redundant, or obvious code comments while preserving valuable explanations. Use when cleaning up comments, removing verbose documentation, simplifying inline comments, or preparing code for review.
review-clean-code
Analyze code quality based on "Clean Code" principles. Identify naming, function size, duplication, over-engineering, and magic number issues with severity ratings and refactoring suggestions. Use when the user requests code quality checks, refactoring advice, Clean Code analysis, code smell detection, or mentions terms like code review, code quality, refactoring check.