Skip to main content
This recipe builds an agent that runs on a schedule. Every weekday morning it searches a GitHub repository for open issues nobody has labeled yet and posts the list to a Slack channel, so triage doesn’t depend on someone remembering to look.

Before you start

  • The Guild CLI, logged in.
  • GitHub connected in your workspace, with the Guild GitHub App installed on the repository. See GitHub setup.
  • Slack connected, and the Slack agent invited to the channel it will post in. See Slack setup.

1. Create the agent

Replace PROMPT.md:
Replace guild.yaml:

2. Save it and install it in your workspace

3. Create the trigger

Schedule times are in UTC, so 14:00 is 7:00 in San Francisco and 10:00 in New York during daylight saving time. To include weekends, use --frequency DAILY and drop --days-of-week. The input is fixed: the agent receives the same text on every run. To cover another repository or channel, create another trigger with a different input rather than another agent.

4. Try it

You don’t have to wait for the schedule. From the agent’s directory, run it once with the same input:
The digest appears in the Slack channel. After the first scheduled run, guild trigger sessions <trigger-id> lists it.

Variations

  • Stale pull requests. Change the query to repo:<repository> is:pr is:open review:required to list pull requests still waiting for a review.
  • Label as well as report. Add github_issues_add_labels and have the agent label each listed issue needs-triage. Labeled issues drop out of the next no:label search; skip labeling if you want them to repeat until someone triages.
  • A different schedule. See Schedule triggers for hourly, weekly, and monthly frequencies.
Last modified on October 15, 2026