ci-readiness-check
Pass
Audited by Gen Agent Trust Hub on Oct 12, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONCOMMAND_EXECUTIONEXTERNAL_DOWNLOADSDYNAMIC_EXECUTION
Full Analysis
- [Indirect Prompt Injection]: The skill processes data from the local environment, such as file names, package metadata, and tool outputs. This creates a surface where instructions could be inadvertently or intentionally embedded in repository data.
- Ingestion points: The agent reads outputs from
git diffandgit statuscommands, package names frompackage.jsonfiles, and diagnostic logs frompnpmandfluid-buildas described inSKILL.mdandci-readiness-check.sh. - Boundary markers: The instructions do not employ specific delimiters or guidance to distinguish between data and potentially executable instructions within these inputs.
- Capability inventory: The skill possesses the ability to execute shell commands, run build processes via
pnpm, and interact with the file system. - Sanitization: Tool outputs and file contents are analyzed directly without explicit sanitization or filtering of instruction-like patterns.
- [Command Execution]: The skill executes various system commands and local scripts to perform its functions.
- Evidence: The skill invokes a bundled shell script (
ci-readiness-check.sh) and uses package management tools (pnpm) for building, linting, and testing (e.g.,pnpm exec fluid-build). These operations are consistent with a developer-focused utility. - [External Downloads]: The skill performs dependency installation using standard package managers.
- Evidence: The
ci-readiness-check.shscript runspnpm install --frozen-lockfileifnode_modulesare missing. This is a routine operation for managing project dependencies. - [Dynamic Execution]: The skill uses runtime evaluation to retrieve project metadata.
- Evidence: The
ci-readiness-check.shscript executes anode -pcommand to evaluate a snippet of JavaScript that reads the package name frompackage.json.
Audit Metadata