Retrieve aggregated task context metadata for coding agent workflows.
npx skills add https://github.com/ma08/botfiles --skill get-task-details
Please help me install this Agent Skill. Skill: get-task-details Source: https://github.com/ma08/botfiles/tree/main/claude/skills/get-task-details Command: npx skills add https://github.com/ma08/botfiles --skill get-task-details
Users working with long-running coding agents across multiple machines and sessions often lose track of critical task context, including status file locations, tracker links, session identifiers, and task progress, leading to wasted time manually searching for relevant information when resuming work.
Use the get-task-details skill to retrieve the full context and status details for your current coding agent task.
High-intent search queries and answers about installing and using this skill.
You retrieve coding agent task context by running a single read-only operation that checks machine-local task pointers first, then falls back to the latest same-session task. This automatically surfaces status file paths, tracker URLs, and session identifiers for your active workflow.
You can resume a coding agent session by pulling up comprehensive task metadata, which includes a concise task recap covering goals, current status, and next steps. This allows you to instantly pick up where you left off without manually navigating task folders.
When task pointers are missing or stale during coding agent status tracking, the system automatically falls back to the latest same-session task in the current project. This ensures you still retrieve relevant task metadata without manual file navigation.
Yes, cross-machine and cross-session task status tracking is fully supported. The system outputs machine name, coding agent session ID, transcript path, and zellij session links, enabling you to verify task status and access resources across different environments.
Retrieving context for zellij coding sessions outputs comprehensive metadata including task folder path, status file path, primary tracker URL, machine name, session ID, transcript path, and zellij session link. It also generates a concise task recap covering goals, current status, and next steps.
You find historical task context by providing a task slug to surface related tasks matching that pattern. The system also automatically surfaces stale tasks older than 7 days, making it easy to locate and access historical coding agent workflow metadata.
ma08Persist task status files and reconcile session metadata across machines.
ma08Create Linear tickets and launch detached zellij/Codex worker sessions.
ma08Retrieve task metadata and transcript history for live coding agent sessions.
MjxOroList and search Droid session JSONL files across project directories.
