MCPInstall

github-author-context

GitHub contributor context: identity, activity, trust, company/team signal.

Installs
89
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/steipete/agent-scripts --skill github-author-context
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads github-author-context automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

GitHub Author Context

Build a compact maintainer-facing profile for a PR author or GitHub user. Use this by default during PR review unless the author is Peter (steipete, Peter Steinberger, or an obvious Peter-owned bot/account).

Inputs

Prefer a GitHub login. From a PR:

gh pr view <n> --json author,url,headRepository,baseRepository -q '{author:.author.login,url:.url,repo:.baseRepository.nameWithOwner}'

Skip the profile pass for steipete unless the user explicitly asks.

Source Order

  1. OpenClaw contributor notes:
~/Projects/maintainers/scripts/clawtributors find github <login>

If a contributor file matches in ~/Projects/maintainers/contributors/people, read only:

  • Identity
  • Signals
  • Context
  • Evidence
  • Notes

Fallback only when the new contributor file is missing and old maintainer context might help:

rg -n -i "<login>|<name>|<discord>" ~/Projects/openclaw-maintainers/people ~/Projects/openclaw-maintainers/data

If an old person file matches, read only the relevant sections:

  • Verdict
  • Identity
  • Company Affiliation
  • Metrics
  • Discord Communication
  • Evidence
  • Risks / Concerns / Recommendation when present
  1. Live GitHub public profile:
gh api "users/<login>" --jq '{login,name,company,location,bio,blog,twitter_username,created_at,followers,following,public_repos}'
  1. Target-repo activity:
gh search prs --repo <owner/repo> --author <login> --state merged --limit 20 --json number,title,mergedAt,url
gh search prs --repo <owner/repo> --author <login> --state open --limit 20 --json number,title,updatedAt,url
gh search issues --repo <owner/repo> --author <login> --state open --limit 20 --json number,title,updatedAt,url
gh api "repos/<owner>/<repo>/collaborators/<login>/permission" --jq '{permission,user:.user.login}' 2>/dev/null || true

For OpenClaw, prefer the new openclaw/maintainers contributor file over recomputing activity unless freshness clearly matters.

  1. Local git evidence when useful:
git log --all --author="<login>" --since="90 days ago" --oneline --decorate --no-merges | head -40
git shortlog -sne --all | rg -i "<login>|<name>|<email>"

Output

Keep it short. Add this block near the top of a PR review:

Author context: @login
- Who: <name/company/location/role, confidence>
- Activity: <merged/open PRs, issues, reviews/commits if known>
- OpenClaw signal: <maintainer/candidate/drive-by/vendor/security/unknown>
- Risk: <review-load, broad PRs, low history, company-governance, none obvious>

Do not quote private phone/email/contact details unless Peter asks. Separate employer from company-directed OpenClaw work; almost everyone has an employer.

Contributor Notes

After a merge/rejection/close/review, add a note only if it creates future review value: first good merge, unusually strong work, repeated quality problems, slop, no-repro churn, exceptional responsiveness, lack of follow-through, or identity confirmation.

Use the maintainer repo helper so Markdown stays consistent:

~/Projects/maintainers/scripts/clawtributors note github <login> --kind merged --pr <n> --summary "Focused bug fix. Tests credible. Smooth review."
~/Projects/maintainers/scripts/clawtributors note github <login> --kind rejected --pr <n> --summary "Broad generated refactor; no reproducible bug; asked to split."
~/Projects/maintainers/scripts/clawtributors link github <login> discord <id> --username <discord> --confidence high --evidence "Self-linked authored PRs in #clawtributors."

Keep notes terse, factual, dated, and linked. Do not record ordinary noise.

FAQ

What does the github-author-context skill do?

GitHub contributor context: identity, activity, trust, company/team signal.

How do I install github-author-context?

Run npx skills add https://github.com/steipete/agent-scripts --skill github-author-context in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/github-author-context/ (personal) or .claude/skills/github-author-context/ (project).

Which AI agents can use github-author-context?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is github-author-context safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains github-author-context?

It is published by steipete in steipete/agent-scripts. It has 89 recorded installs.

More from steipete/agent-scripts

View all →

video-transcript-downloader

steipete/agent-scripts

yt-dlp downloads: video, audio, subtitles, transcripts, clips, playlists.

Media & Creative1K installs

brave-search

steipete/agent-scripts

Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.

skill-cleaner

steipete/agent-scripts

Codex/OpenClaw skill audit: live budget, usage, duplicates, compact descriptions.

Security592 installs

create-cli

steipete/agent-scripts

CLI UX/spec: args, flags, help, output, errors, config, dry-run.

Frontend & Design419 installs

markdown-converter

steipete/agent-scripts

Markdown conversion: PDF, Office, HTML, data, OCR, audio, ZIP, YouTube.

Docs & Writing341 installs

1password

steipete/agent-scripts

Set up and use 1Password CLI (op, one-password). Use when installing the CLI, enabling desktop app integration, signing in, selecting Peter's multi-account setup, or storing/reading/injecting/running secrets via op. Always use tmux for op commands.

Security303 installs

Popular other skills

View category →

hyperframes-cli

heygen-com/hyperframes

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

1.3M installs

triage

mattpocock/skills

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

1M installs

ask-matt

mattpocock/skills

Ask which skill or flow fits your situation. A router over the skills in this repo.

778.4K installs

to-questionnaire

mattpocock/skills

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

508.9K installs

wait-what

mattpocock/skills

Stop. That last message did not land: re-pitch it.

459.7K installs

loop-me

mattpocock/skills

Grill me about specs for the workflows I want to build, within this workspace.

447.9K installs