Repo Recap — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Repo Recap (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Ask Claude about any GitHub repository in plain English — it answers using real live data.
Repo Recap is an MCP (Model Context Protocol) server that bridges Claude to the GitHub API. Instead of clicking through dozens of GitHub pages, you simply ask Claude a question:
"What happened in `vercel/next.js` this week?" "Draft release notes for `facebook/react` from the last 30 days." "Which issues in `microsoft/vscode` need the most attention?"
Claude calls this server, fetches the data, and hands you a clean, readable answer.
| Ask Claude… | Tool called |
|---|---|
"Recap owner/repo from the last week" | list_recent_activity |
"Draft release notes for owner/repo" | summarize_pull_requests |
| "What open issues need attention?" | triage_issues |
"How healthy is owner/repo?" | get_repo_health |
Also includes:
You (in Claude) ──► Claude ──► repo-recap server ──► GitHub API
│ │
clean summary ◄──────┴────── tidied-up data ◄────────────┘Claude never talks to GitHub directly. This server is the bridge: it holds your GitHub token securely, calls the API, and converts raw JSON into readable summaries.
git clone https://github.com/YOUR_USERNAME/repo-recap.git
cd repo-recappip install -r requirements.txtTip: use a virtual environment —python -m venv .venv && source .venv/bin/activate(Mac/Linux) or.venv\Scripts\activate(Windows)
.env filecp .env.example .envOpen .env and paste your GitHub token:
GITHUB_TOKEN=github_pat_your_real_token_hereHow to get a token: GitHub → Settings → Developer settings → Fine-grained personal access tokens → New token. Set it to read-only. Required permissions: Contents, Issues, Pull requests, Metadata.
mcp dev server.pyThis opens the MCP Inspector in your browser — you can click-test every tool before connecting to Claude.
Find your Claude Desktop config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd this block (adjust the path to where you cloned the repo):
{
"mcpServers": {
"repo-recap": {
"command": "python",
"args": ["C:/FULL/PATH/TO/repo-recap/server.py"]
}
}
}Restart Claude Desktop. A small hammer icon will appear — the tools are live.
Weekly recap
"Give me a recap of torvalds/linux from the last 7 days."Release notes
"Summarize pull requests in astral-sh/uv from the last month and write release notes."Issue triage
"What are the top 10 open issues in django/django sorted by discussion?"Health check
"How healthy is supabase/supabase — stars, open PRs, last release?"Read a README
"Show me the README for anthropics/anthropic-sdk-python."repo-recap/
├── server.py # MCP server — all tools, resource, and prompt live here
├── requirements.txt # Python dependencies
├── .env.example # Token template (safe to commit)
├── .env # Your real token (never committed)
└── .gitignore.env loadingPull requests are welcome! For major changes, please open an issue first to discuss what you'd like to change.
git checkout -b feature/my-feature)git commit -m 'Add my feature')git push origin feature/my-feature)~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.