daytona-companion
Daytona Companion
Daytona provides remote cloud sandboxes for running code, tests, and services in isolation. This skill manages the full sandbox lifecycle — create, push code, execute, pull results, preview, and tear down.
This skill is a runtime adapter. It documents how to drive Daytona sandboxes; it does not decide whether a given task should run remotely instead of locally. That decision belongs to the orchestration layer (team-lead-orchestration) and any local routing profile that captures host constraints such as memory pressure, secrets, or quota.
Set the manager script path from this skill path:
SCRIPT="${SKILL_ROOT}/scripts/daytona-manager.mjs"
${SKILL_ROOT} is the path to this daytona-companion skill directory. Set it from the loaded skill path; do not prepend another install root.
From the marketplace root, the direct manager entrypoint is skills/daytona-companion/scripts/daytona-manager.mjs.
Typical workflows
Create a sandbox, push code, run tests, pull results
More from atomlink-ye/my-claude-plugins
paseo-companion
Paseo CLI companion. Load whenever the user mentions paseo, paseo agents, paseo run/send/wait/logs/attach/ls, agent IDs, sending follow-ups to a running agent, loops, schedules, terminals, worktrees, chat, permits, daemon operations, or host/port targeting.
12google-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.
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