resolve-repo
Resolve the correct repository for a task — detect VCS platform, match ticket to repo, clone if missing. Run this in a sub-agent to avoid filling main context.
60
68%
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 ./devflow-plugin/skills/resolve-repo/SKILL.mdThe canonical home for this skill is resolve-repo in AndreJorgeLopes/devflow
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
Yes—step 3 fetches outsider-authored free text (remote repo `name` and `description`) from public VCS platforms at runtime via `gh repo list ... --json name,description` or `glab api .../projects ... | jq -r ...`, and that text is then used in the agent’s LLM context for scoring/output.
- Repository
- AndreJorgeLopes/devflow
- Commit
526efe4
- 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.