paseo-companion
Paseo Companion
Paseo is a daemon-managed CLI for launching, observing, and steering AI coding agents. Every agent gets a stable ID that serves as the handle for all subsequent operations — follow-ups, logs, waiting, archiving.
This skill is a runtime adapter. It documents how to drive the Paseo CLI; it does not decide whether a task should run through Paseo at all, on the local daemon or a remote one, or with which model. Those choices belong to the orchestration layer (team-lead-orchestration) and any local routing profile that applies (e.g. a personalized routing skill).
paseo <command> [options]
Typical workflows
Run a single task and wait for completion
paseo run "implement the new auth flow"
Blocks until the agent finishes. Add --wait-timeout 30m to cap the wait.
More from atomlink-ye/my-claude-plugins
google-workspace
Read, create, and edit Google Workspace documents using the `gws` CLI. Use this skill whenever the user mentions Google Docs, shares a docs.google.com URL, references a Google Doc ID, or wants to read/write/create Google documents. Also trigger on 'GDoc', 'gdoc', 'Google Doc', 'gws docs', or any Google Workspace document operation. Will expand to cover Drive, Sheets, Gmail, Calendar, and other GWS services.
12opencode-companion
OpenCode runtime companion. Load for OpenCode task/status/serve/rescue requests, session IDs, timeout recovery, attach/resume decisions, background execution, context/usage checks, and result forwarding.
12daytona-companion
Daytona sandbox companion. Load for sandbox up/status/push/exec/pull/down/preview/smoke-test requests, adopting existing sandboxes, artifact and git-sync workflows, and sandbox environment variables or secrets.
12debug-workflow
Unified debug workflow skill for real-world issue reproduction, especially browser/UI/Web3 problems that need Playwright, shared Chrome/CDP, or agent-wallet. Use this whenever the user wants to confirm whether a workflow can reproduce real issues from walkthrough docs, issue lists, QA notes, or live bug reports. Start with the debug index, route to the right lane, and prefer deterministic local reproduction over fragile preview environments.
11task-iteration
Orchestrate end-to-end feature implementation from an exec-plan document. Use this whenever the user wants a structured Plan → Generate → Evaluate loop for a feature. It keeps planning and acceptance in Claude, pushes bounded coding/test execution to OpenCode companion sessions, reuses warm sessions across fix rounds, and gates completion on independent evaluation plus an advisory review.
11mcp-skill
On-demand MCP capability invocation via MCPorter. Use when the task needs browser automation (Playwright), documentation lookup (Context7), repository reading (zread), web search (web-search-prime), remote URL reading (web-reader), or any other MCP server. Use whenever you would otherwise want a persistent MCP server but the runtime is configured with no global MCP servers, so each MCP call must go through MCPorter.
11