meta-diagram-triangulation
Scan a target codebase path, classify the most informative diagram kind, then render it as BOTH a PlantUML source file AND a draw.io XML in parallel, and compose them into a single architecture doc. Use when writing an RFC or onboarding doc and you want a text-friendly (PlantUML) and an editable (drawio) view of the same architecture.
69
85%
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
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—`render_drawio` and `render_drawio`→`compose_doc` are fed `{{ outputs.scan_repo | truncate(2000) }}` which is produced from the runtime codebase scan (outsider-authored repo content if the user scans untrusted sources), so free text from that scan can enter the LLM context via the `task: | ... Scan output: --- {{ outputs.scan_repo ... }} ---` blocks.
- Repository
- TokenRhythm/opensquilla
- Commit
94ac35e
- 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.