Deploy Qm
Deploy the QM package from an organization-owned repository into Fly.io, AWS, or...
Install
npx skills add yc-software/qm --skill deploy-qm -g -a claude-code -y- Repository
- yc-software/qm15.6k
- Category
- DevOps
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 304 tokens
- Runs scripts
- No, instructions only
What it does
Deploy the QM package from an organization-owned repository into Fly.io, AWS, or Render, onboard an administrator, configure connectors, and optionally activate Slack.
Deploy QM
Read ../../../deployment.md completely and follow it
as the authoritative workflow. Read only the selected provider reference. Read
references/email.md before collecting email secrets. Administrators can defer
email setup and use qm admin-login; ordinary email sign-in needs a transport. Read
references/slack.md only when Slack is requested.
A deployment needs a base model key and a way for people to sign in. Collect
both in the same pass. The base model provider is a deployment choice recorded
as modelProvider, not a setting to leave for the Admin page. Sign-in is either
the built-in auth broker, with optional email setup for an initial admin-only
deployment, or an external OIDC provider such as Slack. Read references/email.md
once the operator has chosen the broker.
Use the installed @yc-software/qm dependency through npm exec qm -- <command>. Do
not require or clone the QM source repository. Complete every acceptance check
and return the handoff required by deployment.md. Treat qm check --live and
its private live session canary as the automated release gate; still complete
the administrator's manual sign-in and web acceptance check.
