GitHub Activity Digest Skill

A Monday-morning summary of last week's commits, PRs, and issues across the repos you watch — so you walk into standup already knowing what shipped, what stalled, and what bug just got reported.

The Problem

Every dev lead either opens GitHub on Monday and scrolls 50+ notifications, or skips it and finds out the bad news in standup. A weekly digest fixes this without adding another dashboard.

How It Works

Sunday evening, a scheduled InTouch job runs three http tasks against the GitHub REST API (PRs, issues, events) for each watched repo. The github-activity-digest skill takes the raw JSON and produces a grouped, ranked text digest, and the message task sends it.

Setup

1. Install this skill
2. Create a http credential for GitHub: - server: api.github.com - port: 443 - secret: a personal access token (scopes: repo for private, none needed for public)
3. Add the auth header on each HTTP task: Authorization: token <YOUR_PAT> — or store the PAT in the credential and reference it via {{credential.secret}}
4. Edit the YAML below for each repo and schedule for Sunday 8pm

Example YAML Job

name: github-weekly-digest
version: 1.0.0
description: Weekly GitHub activity digest for one repo

notifications:
  - userNames: [intouch]
    alertOnError: true

tasks:
  - name: fetch-pulls
    tool: http
    credentialName: github
    properties:
      method: GET
      url: "https://api.github.com/repos/myorg/myrepo/pulls?state=all&sort=updated&direction=desc&per_page=50"
      headers:
        Accept: "application/vnd.github+json"
        X-GitHub-Api-Version: "2022-11-28"

  - name: fetch-issues
    tool: http
    credentialName: github
    properties:
      method: GET
      url: "https://api.github.com/repos/myorg/myrepo/issues?state=all&since=2026-05-06T00:00:00Z&per_page=50"
      headers:
        Accept: "application/vnd.github+json"
        X-GitHub-Api-Version: "2022-11-28"

  - name: fetch-commits
    tool: http
    credentialName: github
    properties:
      method: GET
      url: "https://api.github.com/repos/myorg/myrepo/commits?since=2026-05-06T00:00:00Z&per_page=100"
      headers:
        Accept: "application/vnd.github+json"

  - name: digest
    tool: skill
    properties:
      skillName: github-activity-digest
      input: |
        Repo: myorg/myrepo

        PULLS:
        {{fetch-pulls.responseBody}}

        ISSUES:
        {{fetch-issues.responseBody}}

        COMMITS:
        {{fetch-commits.responseBody}}

  - name: send
    tool: message
    properties:
      subject: "GitHub weekly digest"
      body: "{{digest.answer}}"
      userNames: "intouch"

Customization

• Multiple repos — duplicate the three fetch tasks per repo and concatenate into one skill input
• Time window — since= 14 days for biweekly, 30 for monthly
• Issue labels filter — add &labels=bug to the issues URL
• Risk thresholds — edit SKILL.md to flag PRs with >50 files instead of >20

Notes

• The since= timestamp is a literal string in this template — for true automation, generate it dynamically (e.g., a runtimeenv task that emits an ISO timestamp) and reference its output
• GitHub auth: if your http connector supports Bearer {{credential.secret}} substitution, prefer that over hard-coding the PAT in the YAML

Cost

• GitHub API: free (5000 req/hr authenticated)
• AI assistant: ~$0.01/digest with Claude Sonnet (worth it for the synthesis)

Roughly $0.05/month for one repo, $0.50/month for ten.