skills.rest
avdi
avdiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

clouddev

Adapt devcontainer-based projects to run on cloud agent platforms via a portable manifest contract.

Updated May 9, 2020
Search Tags:#github actions#docker-compose#devcontainer#ci automation#platform adapters#environment provisioning#cloud agents
One-click install
npx skills add https://github.com/avdi/purse --skill clouddev-avdi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clouddev
Source: https://github.com/avdi/purse/tree/main/home/dot_agents/skills/clouddev
Command: npx skills add https://github.com/avdi/purse --skill clouddev-avdi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Cloud agent platforms hand you a Linux box and a checkout and assume your project's commands just work — an assumption that fails for anything with backing services like Postgres, Redis, CouchDB, or Vault. This Skill reuses your existing devcontainer investment instead of re-deriving environment setup per platform, by splitting the toolchain (a dev image) from backing services (a services-only compose file your boot script runs). ## Core Features & Use Cases - Tier model and fitness assessment: Classify platforms (Ona, Cursor, Copilot, Claude Code cloud, Amp, Devin, Factory, Jules, Cosmos, Codespaces, and more) by adaptation cost and by fitness axes like mission boards and worktree models before committing. - The clouddev.yml contract: A single repo-root manifest declaring prepare/boot/refresh/verify/exec/shell/path/doctor scripts, capabilities, services compose file, and path mappings — with adapters generated from it per platform. - Unattended agent operations: Guidance for running agents in your own CI, including proving the environment before the agent starts, salvaging work from runs that stop early, and fencing paths the agent must not edit. - Use Case: You port a Rails app with Postgres and Redis to Copilot cloud agent: split the compose file, publish a dev image, write prepare/boot scripts, and transcribe the services half into an Actions services: block. ## Quick Start Ask the agent to assess which tier your target cloud agent platform falls into and draft a clouddev.yml manifest with prepare and boot scripts for your devcontainer-based project.

Frequently Asked Questions about clouddev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a devcontainer project work on cloud agent platforms?▼

Split the devcontainer's two concerns: publish the toolchain as a dev image to a registry, and move backing services into a services-only compose file that your own boot script runs from inside the platform's box. Declare both in a clouddev.yml manifest with prepare and boot scripts.

What is the difference between prepare and boot scripts?▼

Prepare runs once per snapshot and its output is disk: dependency installs, image pulls, and cache warming. Boot runs every session and its output is processes: starting services and dev servers. Platforms snapshot the first and discard the second, so prepare then boot in sequence must always be a valid full provisioning.

Which cloud agent platforms support docker-compose backing services?▼

Only devcontainer-native platforms (Codespaces, Ona, Coder's Dev Containers integration) read dockerComposeFile directly. Everywhere else you run the services compose file yourself from your boot script, or transcribe it into an Actions services: block on Copilot.

Why does my cloud agent fail to reach the database during a run?▼

Several platforms restrict the network during the agent phase but not during provisioning, so lazily pulled images or mid-task installs fail. Do all network work in prepare, and verify service reachability with a verify script before the agent starts.

Can I run coding agents unattended in GitHub Actions?▼

Yes, Actions is a tier-0 host where your devcontainer runs unmodified, but there is no snapshot so prepare and boot both run cold every time. Prove the commit gate green before the agent starts, persist work continuously via pushes and issue comments, and fence protected paths with push rulesets.

When should I not bother adapting a platform?▼

Tier-4 platforms with no contract to target — Codex cloud, Kiro Web, Replit, Daytona, OpenHands Cloud, Antigravity — should be documented as unsupported rather than worked around. When a stack is heavy, tier 0 (your own machine or CI with a headless agent CLI) beats fighting a tier-3 platform.

Related Skills

Explore More Software Engineering Skills→
ovisanovisan
2

docker-patterns

Provides Docker and Docker Compose patterns for development stacks, security hardening, and installer testing.

Community
Advanced
llmh333llmh333

gemini-devfleet

Orchestrate multi-agent coding missions in isolated worktrees via Gemini DevFleet.

Community
Advanced
reiserwangreiserwang

agents-context

Load AGENTS.md repository context into agent sessions at startup.

Community
Intermediate
gabesan21gabesan21
1

run-droid

Invokes Factory's droid CLI as a headless executor for delegated coding tasks.

Community
Intermediate