cogni-dao/cogni / .claude/skills/deploy-node
deploy-node
VerifiedRouter for 'deploy a node', 'ship my node app', 'deploy to candidate-a, preview or production', 'which nodes exist', 'check deployment status'. A node ships with one call: POST /api/v1/deploy/workloads. Routes each deploy question to the hub guide or skill that owns it.
Deploy a node
A node ships with one call. Only env changes between environments.
POST https://cognidao.org/api/v1/deploy/workloads {nodeId, env, workload, sourceSha}
GET https://cognidao.org/api/v1/deploy/workloads?nodeId=<id>&env=<env>
env | sourceSha |
|---|---|
candidate-a | The PR head, after review and green CI |
preview | The merge commit. Automatic on merge. |
production | The validated merge commit. Explicit call. |
Declare the app in .cogni/workloads/<name>.yaml in the node repo. CI publishes sha-<sha>. The operator does the rest.
Read these hub guides before the first call:
- cicd-e2e-required-sequence owns the order of steps and the gates.
- deploy-a-declared-workload owns the declaration, the call, the watch and the failure signatures.
- node-service-delivery owns the design.
Do not hardcode the roster
The roster is live state. Read it:
| Want | Source |
|---|---|
| Registered nodes and owners | GET /api/v1/nodes |
| Per-env deploy state | GET /api/v1/nodes/{id}/deploy-state |
| In-repo shape | infra/catalog/*.yaml |
| Did my deploy work, and why not? | GET /api/v1/deploy/workloads/releases/<releaseId>?nodeId=&env= |
| What is serving | curl https://<host>/version from outside the cluster |
Other owners
| Question | Owner |
|---|---|
| Akash runtime, placement, leases | akash-node-expert |
| CI/CD design, freeze policy | devops-expert |
| Promote or flight the operator itself | promote |
| Prove a flighted PR | validate-candidate |
| Secrets | cicd-secrets-expert |
| Node access roles | rbac-expert |
| Turn an env on or off for a node | manage-node-envs |
| Provision an env (operator only) | provision-env |
Invariants
- Follow the release (
GET /api/v1/deploy/workloads/releases/<releaseId>) toactive; never poll/versionto follow a deploy. Afteractive, one/version.buildSharead from outside the cluster confirms the exact commit. A 200 from the verb, a green workflow or a lease is not proof. - Missing placement is a hard failure. Never fall back to k3s.
- Never roll a node back to k3s. Fix forward.
- The operator is the exception. It stays on k3s and Argo (operator only):
POST /api/v1/vcs/flight, thenPOST /api/v1/deploy/promote.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |