github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
58
45%
Does it follow best practices?
Impact
78%
1.62xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/github-release-management/SKILL.mdThe canonical home for this skill is github-release-management in ruvnet/agentic-flow
Low
Low-risk findings.
2 low severity findings. 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: 0.90). The skill explicitly fetches and ingests user-generated GitHub content (commit messages, PRs, discussions) via commands like "gh pr list --json ..." and "gh api repos/:owner/:repo/compare ..." (see "Progressive Disclosure: Level 1" and the GitHub Actions "Initialize Release Swarm" / "Generate Release Changelog" steps) and then uses that data to generate changelogs, version suggestions, PR bodies and drive automated releases/deployments, so untrusted third-party content can materially influence agent actions.
W012: Unverifiable external dependency detected (runtime URL that controls agent)
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
Potentially malicious external URL detected (high risk: 0.90). The workflow and examples repeatedly run "npx claude-flow@alpha" (which fetches and executes package code from the npm registry, e.g. https://registry.npmjs.org), so the skill at runtime pulls remote code that directly implements/controls the agent orchestration and is a required dependency.
- Repository
- ruvnet/RuView
- Commit
d9dfea2
- 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.