flowchart TD
START([Repo Health]) --> GH{"/github"}
GH -->|My status| MYSTATUS["github:my-status"]:::github
GH -->|Weekly summary| WEEK["github:last-week"]:::github
GH -->|Org-wide weekly| ORGWEEK["github:last-week-org"]:::github
GH -->|Triage issues| ISSUES["github:issues"]:::github
GH -->|PR health| PRS["github:prs"]:::github
GH -->|Review PR| PRREVIEW["github:pr-review"]:::github
ORGWEEK -->|calls per repo| WEEK
WEEK -->|calls| ISSUES
WEEK -->|calls| PRS
ISSUES -->|stale| CLOSE[Close or update]
PRS -->|CI failing| RCA["rca:ci"]:::rca
classDef github fill:#E91E63,stroke:#333,color:white
classDef rca fill:#FF5722,stroke:#333,color:white
Follow this diagram as the workflow.
GitHub Skills
Repository health analysis, issue triage, and PR management.
Auto-Select Sub-Skill
What do you need?
│
├─ What needs my attention today?
│ → github:my-status
│
├─ Weekly summary (what happened last week?)
│ ├─ Single repo (kagenti/kagenti)
│ │ → github:last-week
│ └─ Org-wide (all repos)
│ → github:last-week-org
│
├─ Analyze open issues (triage, stale, priority)
│ → github:issues
│
├─ Analyze open PRs (CI status, review needed)
│ → github:prs
│
├─ Review a specific PR (inline comments, conventions)
│ → github:pr-review
│
└─ Create an issue with proper template
→ repo:issue
Available Skills
| Skill |
Purpose |
github:my-status |
Personal dashboard: your open PRs, pending reviews, assigned issues |
github:last-week |
Weekly report: merged PRs, new issues, CI health, priority analysis |
github:last-week-org |
Org-wide weekly report: all kagenti repos, proportional depth by activity |
github:issues |
Issue triage: stale, blocking, no attention, should-close |
github:pr-review |
Automated PR review: inline comments, conventions, security checks |
github:prs |
PR health: passing CI without review, stale, conflicts |
Related Skills
repo:issue - Issue template formatrepo:pr - PR template formatci:status - CI check detailsci:monitoring - Monitor running CI
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: github-133description: GitHub repository analysis - weekly reports, issue triage, PR health, CI trends Use when this capability is needed.4---56```mermaid7flowchart TD8 START([Repo Health]) --> GH{"/github"}9 GH -->|My status| MYSTATUS["github:my-status"]:::github10 GH -->|Weekly summary| WEEK["github:last-week"]:::github11 GH -->|Org-wide weekly| ORGWEEK["github:last-week-org"]:::github12 GH -->|Triage issues| ISSUES["github:issues"]:::github13 GH -->|PR health| PRS["github:prs"]:::github14 GH -->|Review PR| PRREVIEW["github:pr-review"]:::github1516 ORGWEEK -->|calls per repo| WEEK17 WEEK -->|calls| ISSUES18 WEEK -->|calls| PRS19 ISSUES -->|stale| CLOSE[Close or update]20 PRS -->|CI failing| RCA["rca:ci"]:::rca2122 classDef github fill:#E91E63,stroke:#333,color:white23 classDef rca fill:#FF5722,stroke:#333,color:white24```2526> Follow this diagram as the workflow.2728# GitHub Skills2930Repository health analysis, issue triage, and PR management.3132## Auto-Select Sub-Skill3334```35What do you need?36 │37 ├─ What needs my attention today?38 │ → github:my-status39 │40 ├─ Weekly summary (what happened last week?)41 │ ├─ Single repo (kagenti/kagenti)42 │ │ → github:last-week43 │ └─ Org-wide (all repos)44 │ → github:last-week-org45 │46 ├─ Analyze open issues (triage, stale, priority)47 │ → github:issues48 │49 ├─ Analyze open PRs (CI status, review needed)50 │ → github:prs51 │52 ├─ Review a specific PR (inline comments, conventions)53 │ → github:pr-review54 │55 └─ Create an issue with proper template56 → repo:issue57```5859## Available Skills6061| Skill | Purpose |62|-------|---------|63| `github:my-status` | Personal dashboard: your open PRs, pending reviews, assigned issues |64| `github:last-week` | Weekly report: merged PRs, new issues, CI health, priority analysis |65| `github:last-week-org` | Org-wide weekly report: all kagenti repos, proportional depth by activity |66| `github:issues` | Issue triage: stale, blocking, no attention, should-close |67| `github:pr-review` | Automated PR review: inline comments, conventions, security checks |68| `github:prs` | PR health: passing CI without review, stale, conflicts |6970## Related Skills7172- `repo:issue` - Issue template format73- `repo:pr` - PR template format74- `ci:status` - CI check details75- `ci:monitoring` - Monitor running CI7677---78> Converted and distributed by [TomeVault](https://tomevault.io/claim/kagenti) — claim your Tome and manage your conversions.79<!-- tomevault:4.0:skill_md:2026-04-11 -->
tomevault-io