What problem does it solve?
When using the Shark non-blocking execution pattern for AI agents, manually checking multiple separate files to track running background remora jobs, view completed job results, and review recent execution logs is slow and disrupts workflow.
Core Features & Use Cases
- Active Job Monitoring: Reads pending job data to report all running background jobs, including their labels, commands, elapsed runtime, and whether they are overdue past their maximum allowed runtime.
- Completion Result Access: Displays the full contents of the
.shark-done file if it exists, so you can immediately see results from finished jobs.
- Log Review: Shows the last 10 lines of the
SHARK_LOG.md file if present, giving you quick insight into recent execution events.
- Use Case: If you have spawned multiple remora jobs for parallel web search, server health checks, and build tests, use this skill to get a single consolidated view of all job statuses, results, and recent logs without navigating to each file individually.
Quick Start
Ask the shark-status skill to check the current status of all running shark background jobs, view any completed job results, and display the most recent log entries.