Deploy the QM package from an organization-owned deployment repository to Fly.io or AWS. Set up an administrator, choose a model provider and sign-in method, configure connectors, and optionally activate Slack, with acceptance checks before handoff.
Deploy the QM package from an organization-owned deployment repository to Fly.io or AWS, onboard an administrator, configure connectors, and optionally activate Slack.
Review the instructions the agent will receive before you install.
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 repository's installed @yc-software/qm dependency through
npm exec qm -- <command>. Do not require or clone the QM source repository.
Do not stop at infrastructure health: complete the acceptance checks and return
the handoff required by deployment.md. A web response without a generated
sidebar title is not a completed deployment.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Help QM organization admins inspect settings, stored memory, conversations, files, and operational records across the organization. It also supports confirmed configuration changes and external user management, while keeping admin grant changes in the dashboard.
Carry out website tasks in a remote browser, including expense submissions, authorized orders, and retrieving data behind a login. Personal browser profiles preserve sign-ins, while users handle login and verification screens themselves.
Sign in to a cloud provider’s command-line tool using a verification URL and one-time code approved on the user’s device. Check installation and account identity, save the login, and run commands within that user’s permissions.
Help users discover and connect apps, then run available app tools through QM’s authenticated backend. It checks connection status, presents consent options, and keeps Composio project keys out of user-facing setup.
Connect supported work apps through browser consent without sharing passwords with the agent. The skill checks available connection methods, provides a single-use authorization link when appropriate, and guides personal Slack account linking.
Set up recurring agent work for issues, tickets, or small fixes. The skill tests one real item first, then defines a repeatable procedure, tracks work to prevent duplicates, and holds outputs for human review.