deploy-anywhere
Skill4 starsChanged 3 months agoMITView on GitHub
Deploy with unified build/test/deploy intent across providers using .agent-loom/deploy.yml and per-provider adapters. Load when the user asks to deploy, ship to preview, release to production, or run a provider-agnostic deploy flow. Also triggers on "deploy anywhere", "deploy to Vercel", "deploy with GitHub Actions", "preview deploy", or "ship this". Runs preflight before any deploy — stops on missing secrets. Pairs with ci-cd-and-automation for pipeline design. Ships vercel and github-actions adapters; extensible adapter interface.
In this repository125 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/agent-loom-routing.mdcCursor rule
- .cursor/rules/agent-loom-skills-index.mdcCursor rule
- adversarial-hatSkill
- agent-builderSkill
- agent-launcherSkill
- agent-loom-syncSkill
- agent-observabilitySkill
- agent-run-retroSkill
- agent-system-architectureSkill
- api-and-interface-designSkill
- api-deprecation-and-migrationSkill
- apply-paper-to-projectSkill
- app-security-hardeningSkill
- architectural-decision-logSkill
- assumption-mappingSkill
- brainstormingSkill
- browser-testing-with-devtoolsSkill
- business-modelingSkill
- ci-cd-and-automationSkill
- codebase-understandingSkill
- code-review-crspSkill
- code-simplificationSkill
- compress-skillSkill
- context-engineeringSkill
- create-agent-promptSkill
- cross-link-skillsSkill
- customer-discoverySkill
- debug-and-fixSkill
- deep-thinkingSkill
- dependency-mappingSkill
- deprecate-skillSkill
- design-directionSkill
- design-reviewSkill
- design-systemSkill
- dynamic-routingSkill
- eval-judgeSkill
- eval-outputSkill
- eval-pipelineSkill
- eval-rubric-designSkill
- experimentationSkill
- experiment-backlogSkill
- experiment-readoutSkill
- experiment-runbookSkill
- experiment-specSkill
- fault-localizeSkill
- feature-specSkill
- fermiSkill
- first-principlesSkill
- frontend-designSkill
- generate-changelogSkill
- git-workflow-and-versioningSkill
- gsap-animationSkill
- harness-engineeringSkill
- harness-evolutionSkill
- harness-generationSkill
- idea-evaluationSkill
- idea-generationSkill
- implementation-planSkill
- improve-skillsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
Run scripts/preflight.py before any deploy — no partial deploys on missing config/secrets.
- Very specific: line 36
Run test_cmd from config when present before build.
- Very specific: line 61
Run test_cmd then build_cmd from config.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Deploy Anywhere
One deploy intent — read or scaffold .agent-loom/deploy.yml, detect provider, preflight secrets, run adapter steps, return URL + rollback command.
Hard Rules
Run scripts/preflight.py before any deploy — no partial deploys on missing config/secrets.
Secrets by name only in files — never write credential values to repo.
Shipped adapters: vercel, github-actions — see references/adapters/.
Run test_cmd from config when present before build.
Emit deployment summary: target, URL/status, rollback command.
Workflow
Step 1 — Read or scaffold config
Load .agent-loom/deploy.yml per DEPLOY-SCHEMA.md. If missing, scaffold from repo signals (vercel.json, .github/workflows/) and confirm with user.
Step 2 — Detect target
Config targets[] first; else repo signals; else ask.
Step 3 — Preflight
python3 .agents/skills/deploy-anywhere/scripts/preflight.pyOn fail: list missing items exactly; stop.
Step 4 — Test + build
Run test_cmd then build_cmd from config.
Step 5 — Run adapter
Load references/adapters/<provider>.md. Execute documented CLI sequence.
Step 6 — Summarize
## Deploy summary
Target: [provider] ([preview|prod])
URL: [url or run link]
Rollback: [command]Gotchas
- Vercel prebuilt flow requires
vercel buildbeforevercel deploy --prebuilt. - Local
gh workflow runneedsghauth — not the same as CI token. - Multiple targets deploy sequentially — confirm order with user.
Output Format
See Step 6 summary template.
Examples
Teaser: deploy.yml with vercel target → preflight OK → build → deploy URL returned.
Full pairs: references/examples.md
Common Rationalizations
| Excuse | Reality |
| "Skip preflight — I'll add secrets later" | Half-configured deploys fail opaquely. |
| "Embed token in deploy.yml for now" | Secrets in repo leak — names only. |
| "Skip tests this once" | test_cmd exists for a reason. |
| "One adapter fits all" | Use the adapter file — don't improvise CLI. |
| "Rollback is optional" | Always emit rollback command. |
Verification
- preflight.py passed
- test_cmd run when configured
- Adapter steps from reference file
- Rollback command in summary
Red Flags
- Deploy attempted after preflight fail
- Secret value written to yaml
- Unknown provider without adapter file
Prune Log
Last pruned: 2026-07-05
- Initial release from high-leverage skill spec (Skill 3 family)
Impact Report
Deploy: [provider] | Preflight: [pass/fail] | URL: [url or n/a]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.