Skip to content

cogni-dao/cogni / .claude/skills/deploy-node

deploy-node

Verified

Router 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>
envsourceSha
candidate-aThe PR head, after review and green CI
previewThe merge commit. Automatic on merge.
productionThe 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:

Do not hardcode the roster

The roster is live state. Read it:

WantSource
Registered nodes and ownersGET /api/v1/nodes
Per-env deploy stateGET /api/v1/nodes/{id}/deploy-state
In-repo shapeinfra/catalog/*.yaml
Did my deploy work, and why not?GET /api/v1/deploy/workloads/releases/<releaseId>?nodeId=&env=
What is servingcurl https://<host>/version from outside the cluster

Other owners

QuestionOwner
Akash runtime, placement, leasesakash-node-expert
CI/CD design, freeze policydevops-expert
Promote or flight the operator itselfpromote
Prove a flighted PRvalidate-candidate
Secretscicd-secrets-expert
Node access rolesrbac-expert
Turn an env on or off for a nodemanage-node-envs
Provision an env (operator only)provision-env

Invariants

  • Follow the release (GET /api/v1/deploy/workloads/releases/<releaseId>) to active; never poll /version to follow a deploy. After active, one /version.buildSha read 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, then POST /api/v1/deploy/promote.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 117kUpdated Claude CodeCodexVerifiedInstall