1.3K skills · sorted by relevance
Manage coding-agent sessions across connected machines through Herdr, tmux, and MSP. See which sessions need attention, review their output, open sessions with a brief, send instructions, answer approval dialogs, and stop or close sessions.
Search past coding sessions across Claude Code, Codex, and Cursor to recover earlier attempts, failed approaches, decisions, and findings. It filters history by topic and time, then summarizes technical details relevant to the question.
Guides agents in choosing Cherry Studio tools for research, document conversion, memory, notifications, and other tasks. It explains when to use app tools or local runtimes, with checks for availability, configuration, and approval.
Shows recent work sessions for the current project as a timeline, newest first. It includes session identifiers, start times, status, recorded observation counts, and available highlights or decisions, using only history returned by the memory tool.
Summarize recent agent sessions for the current project, grouped by date with highlights from recorded observations. Review today, the last seven days, or a chosen number of sessions, with totals for sessions, days, and observations.
Track multiple Claude sessions working on one project, check that changes reached main with screenshots and changelog entries, verify the live site, and identify finished sessions, interrupted work, and questions awaiting the user.
Browse, inspect, create, and update exploratory testing sessions in TestDino, where testers investigate behavior beyond fixed test steps. Filter sessions by assignee, release, tags, or status, then assign work or change a session’s state using its ID.
Manage Claude Code sessions — search by topic or ID, browse recent sessions with full metadata (tags, summaries, titles, cost), view title/nickname history timelines, resume in Ghostty tabs, spawn interactive or headless sessions, monitor live sessions, and bootstrap new setups. Triggers on resume session, find session, list sessions, recent sessions, spawn session, session history, what was I working on, open in ghostty, title history, session nicknames.
The English summary is being prepared. Showing the original description.
Operate and extend NanoClaw, an interactive command environment with sessions stored in Markdown. Resume, branch, search, compact, and export sessions, or switch models and load skills through slash commands.
Keep project context across Claude Code sessions by saving progress, decisions, blockers, and next steps. Commands retrieve project briefings, while a session-start hook loads a compact summary to help resume previous work.
Prepare a repository for Claude Code on the web by creating a startup hook that installs project dependencies. Register the hook and check that it runs successfully, along with a sample test and code quality check.
List Git commits linked to agent work sessions, with branch or repository filters. See each commit’s message, date, linked sessions, and observation counts to review recorded changes alongside their session context.
Find running or paused Ouroboros sessions after an MCP server disconnect. The skill lists saved sessions and provides commands to inspect recorded events, open a monitor, or resume execution with the original Seed specification file.
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.
The English summary is being prepared. Showing the original description.
MUST USE when asked to find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across Codex, Claude Code/Desktop, Aside, OpenCode, Senpi/pi, OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Kiro, Goose, Hermes, Crush, Zed, or unknown local agent logs. Uses the repo-backed TypeScript coding-agent-sessions CLI for transcripts, session IDs, rollout JSONL, state SQLite, Claude histories, Aside messages.jsonl, OpenCode sessions, child linkage, cwd/model/time/token filters, archives, and cost clues.
The English summary is being prepared. Showing the original description.
Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.
Save an agent session’s state, settings, memory, and task progress, then restore it in another conversation. List saved sessions, inspect their details, and remove old ones when managing checkpoints for ongoing work.
Identify individual sessions with unusually high or low spending using the median and MAD, a measure of spread around it. Filter by time period, adjust detection thresholds, and optionally return a failure exit code for automated checks.
Compare two recorded browser sessions at matching step IDs using screenshots and accessibility snapshots, which describe page elements. Report the first difference and overall similarity to check interface changes or verify replayed sessions.
Search local session histories across Codex, Claude Code, OpenCode, and other coding agents. Find earlier requests, inspect transcripts and child sessions, and reconstruct past work using recorded evidence, with filters for dates, projects, platforms, and models.
Check opencode commands, HTTP server behavior, lifecycle events, and terminal startup with purpose-built scripts. Find stored sessions by ID, title, or scoped message searches, and export conversations as JSON for further inspection.
Follow practical agent-browser workflows to inspect pages, click elements, fill forms, extract information, and take screenshots. The guide also covers waiting for page changes, saving login state, and keeping separate browser sessions for different tasks.
Inspect OpenCode sessions with helper scripts that list sessions and retrieve their latest messages. Use the last message’s sender as a rough guide to task status when checking activity across multiple OpenCode sessions.
Control interactive command-line tools through tmux by sending keystrokes, capturing terminal output, and waiting for prompts. Supports session management and running multiple coding agents in parallel, with helper scripts for finding sessions and detecting text.