jira-refactor-findings
The Jira tracker for refactor findings: ENG tickets labeled refactor-findings with the Pod field, the plan attached, and a run link. Read when fragility-common/config.json sets tracker to jira and you need to know how findings map onto tickets, or when changing that mapping.
87%
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
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 skill reads Jira issues and comments via `scripts/jira.ts`, exposing the agent to outsider-authored free text from Jira tickets.
- Repository
BuilderIO/agent-native
- Revision
46ed84c
- 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.