deploy-qm
GitHub指导部署QM应用至Fly.io或AWS，包含管理员配置、连接器设置及Slack集成。遵循标准工作流，收集模型密钥与认证方式，执行自动化检查及手动验收，确保发布流程完整。
Trigger Scenarios
Install
npx skills add yc-software/qm --skill deploy-qm -g -y
SKILL.md
Frontmatter
{
"name": "deploy-qm",
"description": "Deploy the QM package from an organization-owned repository into Fly.io or AWS, 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.
Version History
-
1a6b0e4
Current 2026-09-08 20:01
优化了文档结构，明确email.md的读取时机；更新认证逻辑描述，强调OIDC无需邮件而内置auth需要；新增允许操作员无需邮件即可管理员登录的功能。
-
3cb5623
2026-08-12 09:22
修复Pi路由问题并增强实时部署验证逻辑，加固部署金丝雀测试以关闭竞态窗口。
- 7f2c916 2026-08-02 21:46
