How to Run an AI GitHub Productivity Agent with OE Runtime

Get a clear picture of your GitHub repository's health in seconds. OE Runtime fetches open issues and pull requests, triages by age and label, flags what is stale or unreviewed, and delivers a prioritised action list — no manual triage required.

What You Need

• Node.js 18+ installed, or the OE Runtime binary from openenthrium.com/runtime
• An API key from OpenAI, Anthropic, or any supported LLM provider
• A GitHub Personal Access Token with repo scope — generate one at github.com/settings/tokens
• A text editor — nothing else

Create the Project Folder

Create a folder called productivity-crm/ and add these two files:

The Skill Files

Create SKILL.md inside a productivity-crm/ directory. This is the portable skill — it follows the agentskills.io format and runs unchanged on Claude, Cursor, Windsurf, or OE Runtime:

---
name: productivity-crm
description: Summarize open issues and PRs in a repository
license: Apache-2.0
metadata:
  author: Open Enthrium
  version: "1.0"
---

You are a GitHub assistant. Fetch repository activity, summarize open issues and pull requests,
and identify what needs immediate attention.
Complete all steps fully before writing your report.

## Step 1: Fetch Repository Activity
Using the GitHub connector, fetch:
- All open issues (up to 20), sorted by most recently updated
- All open pull requests (up to 10), sorted by most recently updated
For each, note: title, author, labels, created date, and days open.

## Step 2: Triage and Prioritize
From the fetched issues and PRs:
- Flag any issue or PR open for more than 14 days as stale
- Group issues by label (bug, enhancement, question, other)
- Identify PRs that have no reviewers assigned
- Find any issues marked as "bug" that have no assigned PR

## Step 3: Report
Produce a repository health summary:
- Open issues: total, breakdown by label, stale count
- Open PRs: total, unreviewed count, stale count
- Top 3 most urgent issues (bugs with no PR)
- Recommended next actions

Create agent.yaml in the same directory to wire the skill to your connector:

name: GitHub Assistant
description: Summarize open issues and PRs in a repository
connectors:
  - connection_name: GitHub
    connection_type: github
skills:
  - path: ./
    trigger_type: auto

The Config File

Create oe-config.json in the same directory:

{
  "llm": {
    "provider": "openai",
    "model": "gpt-4o",
    "apiKey": "YOUR_OPENAI_API_KEY"
  },
  "server": {
    "enabled": false,
    "port": 3333,
    "apiKey": "your-secret-api-key"
  },
  "connectors": [
    {
      "connection_name": "GitHub",
      "connection_type": "github",
      "token": "ghp_YOUR_GITHUB_PERSONAL_ACCESS_TOKEN",
      "owner": "your-org",
      "repo": "your-repo"
    }
  ]
}

Create a Personal Access Token at github.com/settings/tokens with repo scope. Replace your-org and your-repo with your organisation and repository names.

Download OE Runtime

Run the Agent

From the parent folder containing your skill directory:

1 npx recommended

npx -y @openenthrium/oe-runtime@latest ./productivity-crm

2 Windows

oe-runtime-win.exe ./productivity-crm

3 macOS

chmod +x oe-runtime-macos
./oe-runtime-macos ./productivity-crm

First run blocked? System Settings → Privacy & Security → Allow Anyway.

4 Linux

chmod +x oe-runtime-linux
./oe-runtime-linux ./productivity-crm

5 API Server integration

Add a "server" block to oe-config.json, then start with --serve:

{
  "llm": { ... },
  "server": { "enabled": true, "port": 3333, "apiKey": "your-secret-key" },
  "connectors": [ ... ]
}

npx -y @openenthrium/oe-runtime@latest --serve --config oe-config.json

Run with inline YAML:

curl -X POST http://localhost:3333/run \
  -H "Content-Type: application/json" \
  -H "X-API-Key: your-secret-key" \
  -d '{"yaml": "...", "params": {}}'

Or run from a file on the server:

curl -X POST http://localhost:3333/run-file \
  -H "Content-Type: application/json" \
  -H "X-API-Key: your-secret-key" \
  -d '{"file": "/path/to/agent.yaml", "params": {}}'

Use Cases

• Daily repository health checks — Run the agent each morning to get a snapshot of open issues, PR status, and stale items across your repository. The report tells your team what to focus on without anyone needing to manually scan the issue tracker or pull request queue.
• Sprint planning support — Before a sprint planning session, run the agent to produce a triaged list of open bugs, feature requests, and technical debt items with their age and labels. This gives your team a prioritised backlog view without the overhead of manual issue grooming.
• Pull request review management — Identify pull requests that have been open for more than a week with no reviewer assigned and surface them as a priority. Unreviewed PRs slow down the team and block feature delivery — the agent flags them so engineering leads can reassign or expedite review.
• Release readiness assessment — Before cutting a release, run the agent to confirm there are no open bug issues without an associated pull request and that all critical PRs have been reviewed and merged. This gives your release manager confidence that nothing critical has been missed.
• Open source community management — For open source maintainers, the agent provides a regular digest of unanswered community questions, stale contributor PRs, and unfiled bug reports. It helps maintainers stay on top of community engagement even with limited time.
• Cross-repository portfolio view — Run the agent against multiple repositories in sequence to build a portfolio-wide health report for engineering leadership. Each report shows the issue and PR status per repo, giving a consolidated view of development health across the entire product.
• Automated triage notifications — Run the agent as an API server and integrate it with your Slack or email setup to deliver automated triage summaries to the relevant channel or inbox. Engineering managers get a daily digest without any manual reporting effort.
• Onboarding for new contributors — Point new developers at the agent to get an instant view of what is most urgently needed in the repository. The prioritised issue list with bug tags and PR gaps gives newcomers a clear starting point for their first meaningful contribution.