github-author-context
GitHub contributor context: identity, activity, trust, company/team signal.
How do I install this agent skill?
npx skills add https://github.com/steipete/agent-scripts --skill github-author-contextIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill gathers GitHub contributor context by executing local scripts, git commands, and GitHub CLI tools. It processes external data from GitHub profiles and PRs, creating an attack surface for indirect prompt injection and potential command injection via unsanitized placeholders.
- Socketwarn
1 alert: gptSecurity
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
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
- OpenClaw contributor notes:
~/Projects/maintainers/scripts/clawtributors find github <login>
If a contributor file matches in ~/Projects/maintainers/contributors/people, read only:
IdentitySignalsContextEvidenceNotes
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:
VerdictIdentityCompany AffiliationMetricsDiscord CommunicationEvidenceRisks/Concerns/Recommendationwhen present
- Live GitHub public profile:
gh api "users/<login>" --jq '{login,name,company,location,bio,blog,twitter_username,created_at,followers,following,public_repos}'
- 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.
- 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.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/steipete/agent-scripts/github-author-context">View github-author-context on skillZs</a>