triage-resolve
Project- and tracker-agnostic engineering pipeline. Given a normalized work-item plus one or more targets ({repo, base, local checkout, site}), it implements the change with plan-with-docs + TDD in an isolated worktree, runs the REPO'S OWN declared verification (whatever its AGENTS.md / CLAUDE.md / cloud.md prescribes), then mandatory pipeline gates — an agent-browser visual regression for UI changes and `/simplify` + `/code-review` for code changes — then hands to the independent `triage-verifier` agent before opening a DRAFT pull request. For bug-kind items it propagates a verified fix to other sites that actually reproduce it. Returns PR URLs; performs no tracker calls. Usable standalone to resolve a branch against an AC checklist.
58
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./triage-resolve/SKILL.mdW011: 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 workflow takes an input object containing a bug or task title and body (`title, body`), which originate from a work-item tracker and are processed by implementation and verification agents.
- Repository
- MrToxy/claude-skills
- Commit
66c7102
- 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.