DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to triage your inbox on a schedule in your own voice with QM

Label and draft replies to email on a recurring schedule, using your past sends as style.

Voice cloning. The agent learns your writing voice from past sends, so drafts imitate you and should be reviewed before anyone treats them as your words.

Credentials. The agent acts with your email credentials and permissions, so limit the connector scope and keep approval gates on while you test.

Who it is forA founder or operator with a crowded inbox who wants routine email handled in their own writing style on a schedule.

The problemTriage takes time every day. Generic reply drafts sound wrong, and sending them unreviewed is risky.

The outcomeA scheduled triage run that labels incoming email and drafts replies in your learned voice, ready for your review.

What you need first

  • Your own cloud account for the deployment, as the README says each deployment runs in the operator's own cloud
  • Your own model keys and provider choice, since the README says deployments use your own models and keys
  • Node.js and npm to run the qm CLI and npm install (inferred from the npm commands in the README)
  • A Postgres database for durable sessions, set through DATABASE_URL
  • Optional: a Slack workspace where you can grant access, if you want Slack rather than web only

Steps

  1. Deploy QM and complete the connector credentials step during initialization so the agent can reach your email.
  2. Ask the agent to learn your writing voice from your past sends in your personal scope.
  3. Set a cron in your personal scope to run triage on the schedule you want, covering labels and reply drafts.
  4. Review the drafts in the web app before anything is sent, and keep the posture at Strict if you want every tool call approved.

Prompt for your agent

Using the repository yc-software/qm, set up a scheduled inbox triage for <person's email account>. Learn the writing voice from past sent mail, then label incoming messages and create reply drafts without sending them. Verify that no message was sent and that each draft is saved for review.

Caveat. The README mentions email triage as a capability but does not name the email connector, so confirm which connectors your deployment supports before you start.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page