e2e
Story-to-e2e-test workflow that takes a Jira [QE] Story, discovers the project's e2e testing infrastructure, plans test scenarios, writes e2e tests matching project conventions, validates them, and manages review via GitHub PRs. Use when implementing [QE] stories produced by the design workflow. Activated by commands: /ingest, /plan, /revise, /code, /validate, /publish, /respond.
89%
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
The canonical home for this skill is e2e in flightctl/ai-workflows
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 e2e workflow consumes outsider-authored PR review comments and feedback via GitHub CLI / API in the /respond skill.
- Repository
amir-yogev-gh/ai-workflows
- Path
e2e/SKILL.md
- Revision
7b2b8de
- 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.