miro-code-review
Use when the user wants to create a visual code review on a Miro board from a pull/merge request (GitHub, GitLab, or any forge), local uncommitted changes, or a branch comparison — produces a file-changes table, summary/architecture/security docs, and architecture diagrams, then links them back from the PR/MR.
93
93%
Does it follow best practices?
Impact
96%
1.39xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
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 ingests outsider-authored free text from PR/MR metadata/body and unified diffs fetched at runtime via external forge CLIs/REST (e.g., `gh pr view ... --json title,body,...` / `glab mr view ... -F json` and `... pr diff/mr diff`), which is then placed into the agent’s LLM context for analysis and artifact generation.
- Repository
miroapp/miro-ai
- Revision
b6408e1
- 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.