orchestrate-cloud-work
Skill2 starsChanged 29 days agoApache-2.0View on GitHub
Run a sustained program of repository work through later.dog's supervisor: split it into scoped cloud jobs with dependencies, follow their durable receipts, and carry each result to a verified, reviewed draft PR.
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-appSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- setup-laterdogSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Submission uncertain: never submit again. Look for the task with list_provider_tasks on the job's profile and attach it with …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Orchestrate cloud work
Use when the work is bigger than one change: several jobs, several repositories, or days of follow-up. Coding runs in the cloud through the supervisor; do not fan out parallel agents on the person's computer instead. Use the later.dog MCP server. Tool prefixes depend on the client; discover tools by their names below.
Plan
- Read the workspace.
laterdog_workspacelists repositories, account profiles, backends and their stated limits, slots in use, existing jobs and measured outcomes.inspect_provider_accessshows a profile's sign-in and CLI capabilities, not its remaining allowance; treat allowance as unknown. A backend listed as enabled is ready to use: later.dog Cloud runs each job in its own cloud computer on the owner's Cloudflare with their Claude plan, and needs no keys from the person. Say a key or setup step is missing only when the workspace shows that backend disabled, and quote its stated reason. - Split the work by what each piece owns. Every job gets a goal, acceptance criteria, write scopes as narrow as the change allows, and
dependencieson the jobs it builds on. The supervisor holds a job until its dependencies are ready and runs overlapping scopes in one repository one at a time; choosing good boundaries is still your call.
Delegate and follow
delegate_cloud_jobfor each job, with arequestKeytied to that intent (reuse it on a retry, never for different work), therepository, atitle, abriefholding the goal and acceptance criteria,writeScopes,dependencies, and the program'sstandingInstructionson every job. LeaveprofileIdout to use later.dog Cloud; name a profile only to send the job to a different backend the workspace lists as enabled. The person sees each job as a cloud task card in the chat, with its live progress, so tell them what you started rather than polling it. A brief goes to the cloud: no credentials or private material in it.inspect_cloud_jobreads a job and its receipts without touching the provider task. Never resume a task just to see whether it is alive.- A finished job is a result to judge, not proof. Read the diff with
collect_cloud_diff, publish it as a draft PR withpublish_cloud_job(only the remote publishing host can; a supervisor on the local computer refuses), then follow themonitor-and-shipskill. Merging stays with the person.
When something goes wrong
- Submission uncertain: never submit again. Look for the task with
list_provider_taskson the job's profile and attach it withreconcile_cloud_task. Only if that list shows no task maycancel_cloud_jobwithacknowledgeUnknownfree the slot. - Cancelling stops queued work. A native task that was already submitted cannot be cancelled; the job records the request and the task may keep running.
- Limits stay visible. This adapter cannot create a cloud environment, continue a native task or cancel a submitted one. A follow-up change is a new repair run (
correct_cloud_job) on the published branch.
Keep score
- Record decisions, human interventions, regressions and sourced costs with
record_job_observation. Report PRs opened, verified and merged as separate numbers, with blockers and limits. A capacity goal (a monthly PR count, a concurrency level) is a target until observations show it; raise concurrency only after they do.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

