DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to set a weekday routine that briefs you each morning with Conch Agent

Schedule a Conch routine for 7:30 each weekday and read the result in chat.

Credentials. Connecting Gmail or Google Calendar gives the routine access to those accounts, so choose Read only unless the routine needs to write.

Who it is forA busy person who wants the day's information ready before they open a laptop.

The problemChecking calendars, email and tasks by hand every morning takes time before the day starts.

The outcomeA routine that runs every weekday at 7:30 and reports back in your Conch chat.

What you need first

  • A computer running macOS, Windows or Linux
  • A plan you already pay for with a supported provider, or an API key from a provider
  • Node 24 or newer, only if you run from a checkout

Steps

  1. On macOS or Linux, run curl -fsSL https://conchagent.com/install.sh | sh. On Windows, run irm https://conchagent.com/install.ps1 | iex in PowerShell.
  2. Open Conch and connect a provider you already pay for.
  3. In chat, ask for a routine that runs every weekday at 7:30 and describes the briefing you want.
  4. Open Routines in the app, confirm the schedule, and check the first result the next morning.

Prompt for your agent

Using the georgevibing/conch-agent repo, create a weekday routine at 7:30 in the Conch app that summarizes <the sources you choose>. Expected output: a routine listed under Routines with the 7:30 weekday schedule. Verify that the first run posts its result to the chat.

Caveat. The README lists Routines and the 7:30 weekday example, but it does not describe the exact briefing format, so confirm the output on your first run.

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