jira-safe
Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking.
64
76%
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 ./data/skills-md/01000001-01001110/agent-jira-skills/jira-safe/SKILL.mdLow
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
The skill's SKILL.md shows it directly fetches data from an external Jira instance (e.g., fetch(`${JIRA_URL}/rest/api/3/project/${PROJECT_KEY}``, `${JIRA_URL}/rest/api/3/field`, and the search/delete endpoints) and uses that project/field/issue data (which can be user-generated/untrusted) to determine project type, field IDs, and drive create/delete actions, so third-party content can materially influence tool behavior.
- Repository
- NeverSight/skills_feed
- Commit
2f57aec
- 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.