dvy1987/agent-loom / .agents/skills/deploy-anywhere
deploy-anywhere
VerifiedDeploy 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.5 KB |
| references/DEPLOY-SCHEMA.md | markdown | 1.3 KB |
| references/adapters/github-actions.md | markdown | 999 B |
| references/adapters/vercel.md | markdown | 793 B |
| references/examples.md | markdown | 381 B |
| scripts/preflight.py | script | 2.7 KB |
references/DEPLOY-SCHEMA.md
View on GitHub# Deploy Schema — `.agent-loom/deploy.yml`
Declarative deploy intent. Secrets referenced by **name only** — never store values in repo.
---
## Example
```yaml
build_cmd: npm run build
test_cmd: npm test
env_map:
NODE_ENV: production
targets:
- provider: vercel
project_id: my-app
org_id: team_abc
prod: false
- provider: github-actions
workflow: deploy.yml
prod: true
```
---
## Fields
| Field | Required | Description |
|-------|----------|-------------|
| `build_cmd` | yes | Build command before deploy |
| `test_cmd` | no | Run before build when set |
| `env_map` | no | Non-secret env defaults |
| `targets` | yes | ≥1 provider block |
### Target block
| Field | Description |
|-------|-------------|
| `provider` | `vercel` \| `github-actions` \| (future adapters) |
| `project_id` | Provider project slug/id |
| `org_id` | Org/team id when required |
| `prod` | `true` = production target |
---
## Preflight
```bash
python3 .agents/skills/deploy-anywhere/scripts/preflight.py .agent-loom/deploy.yml
```
Fails loudly on missing config or env secrets.
---
## Provider detection order
1. Explicit `targets` in deploy.yml
2. Repo signals: `vercel.json` → vercel; `.github/workflows/*deploy*` → github-actions
3. Ask user — never guess credentials
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |