flow-driven-integrate
Bind a flow workspace to wherever the work is actually managed — GitHub Issues and Projects, Jira, Linear, an internal Kanban dashboard, a spreadsheet, or chat — by choosing a system-of-record mode (files-only, mirror, adopt, split), writing a field-ownership map with exactly one writer per field, and using the board export plus the harness's own tools to sync. Use when leadership needs the flow where they already look, when a tracker already holds the work, or when a sync has started fighting the workspace. Part of the flow-driven family.
85%
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 workflow integrates with external systems like GitHub Issues, Jira, and Linear (SKILL.md lines 3, 34-35), which ingest outsider-authored free text without the agent first selecting a specific item.
- Repository
yyeret/portfolio-pdlc
- Revision
cb337f8
- 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.