ensure-epic-jira-issue
Pass
Audited by Gen Agent Trust Hub on Nov 10, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONDYNAMIC_EXECUTIONCOMMAND_EXECUTION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill and its included framework scripts ingest data from local repository files which could be manipulated to influence agent behavior.
- Ingestion points:
SKILL.md(Step EJ1) reads epic markdown files atEPIC_FILE_PATH.references/defer-mutation.jsparses thereferences/tracker-access-record.mdfile to determine valid mutation kinds and consequences. - Boundary markers: Absent; the skill and scripts parse YAML frontmatter or markdown tables from these files without explicit sanitization or instructions to ignore embedded instructions in the ingested data.
- Capability inventory: The skill invokes Atlassian MCP tools (
getJiraIssue) and executes Node.js scripts (sync-jira-epic.js). It also performs file system writes to update markdown frontmatter. - Sanitization: Absent; extracted values (such as
jira_key,title, and roster kinds) are used directly as parameters for tools and command-line execution. - [DYNAMIC_EXECUTION]: Internal helper scripts utilize dynamic code execution for environment resolution and configuration parsing.
references/read-config.shexecutes Python code strings viapython -cto parse YAML configurations when thepyyamllibrary is available.references/defer-mutation.jsuseschild_process.spawnSyncto executebashcommands for platform detection and access mode resolution.- [COMMAND_EXECUTION]: The skill executes a bundled script in Step EJ4 by running
node .agents/skills/sync-jira-epic/scripts/sync-jira-epic.js --file "$EPIC_FILE_PATH"to synchronize data between the local file and Jira.
Audit Metadata