github-author-context
GitHub contributor context: identity, activity, trust, company/team signal.
66
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/github-author-context/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
At runtime the workflow runs `gh api "users/<login>"` and `gh search ...` / `gh search prs ...` to fetch a PR author’s public GitHub profile and activity (outsider-authored/free text from public web/API sources) and injects those retrieved fields like `bio`, `company`, and PR/issue titles into the agent’s LLM context.
- Repository
- steipete/agent-scripts
- Commit
bb36883
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.