github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
56
38%
Does it follow best practices?
Impact
88%
2.83xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/github-multi-repo/SKILL.mdThe canonical home for this skill is github-multi-repo in ruvnet/agentic-flow
Low
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
Third-party content exposure detected (high risk: 1.00). The SKILL.md workflow contains numerous Bash/gh commands that auto-discover, gh api fetch, and clone GitHub repositories and their files (e.g., "gh repo list ...", "gh api repos/:owner/:repo/contents/package.json", and cloning in /tmp), meaning the agent will read untrusted, user-generated third-party repository content from GitHub and act on it (tests, commits, PRs), which could enable indirect prompt injection.
- Repository
- ruvnet/ruvector
- Commit
6a6c39e
- 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.