jira-safe
Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking.
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/01000001-01001110/agent-jira-skills/jira-safe/SKILL.mdSecurity
1 medium severity finding. This skill can be installed but you should review these findings before use.
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
Third-party content exposure detected (high risk: 0.80). 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
f772de4
- 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.