sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
62
46%
Does it follow best practices?
Impact
90%
1.38xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/sparc-methodology/SKILL.mdThe canonical home for this skill is sparc-methodology 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
The required workflow integrates GitHub repository analysis and pull request management tools (e.g., github_repo_analyze and github_pr_manage), which process external repository issues, PRs, and untrusted outsider-authored code and comments.
- Repository
- ruvnet/RuView
- Commit
de099c1
- 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.