chainlink-cre-skill

Pass

Audited by Gen Agent Trust Hub on Oct 23, 2026

Risk Level: SAFEREMOTE_CODE_EXECUTIONCOMMAND_EXECUTIONDATA_EXFILTRATIONINDIRECT_PROMPT_INJECTION
Full Analysis
  • [REMOTE_CODE_EXECUTION]: The skill provides installation instructions in getting-started.md that utilize shell scripts fetched from cre.chain.link via curl | bash and irm | iex. These resources are hosted on official infrastructure belonging to the skill's author and are standard for the product's onboarding.
  • [COMMAND_EXECUTION]: The skill makes extensive use of the cre CLI tool via the Bash capability to initialize projects, simulate workflows, and manage secrets. Access is restricted to the cre:* command namespace in the skill's frontmatter configuration to ensure least privilege.
  • [DATA_EXFILTRATION]: Network operations are performed using the WebFetch tool and internal HTTPClient APIs to access official documentation (docs.chain.link) and vendor services (cre.chain.link, app.chain.link). These communications are part of the intended workflow for fetching developer resources and interacting with the product's API.
  • [INDIRECT_PROMPT_INJECTION]: The skill handles untrusted external data, such as smart contract ABIs and trigger payloads.
  • Ingestion points: The skill reads external data in evm-client.md (ABIs) and triggers.md (HTTP and EVM log payloads).
  • Boundary markers: SKILL.md (Operational Invariant #12) explicitly instructs the agent to treat external content as untrusted and ignore any embedded instructions for credentials or shell callbacks.
  • Capability inventory: The agent has access to Bash (restricted), WebFetch, Write, and Edit tools to process this data.
  • Sanitization: Instructions in workflow-patterns.md mandate strict input validation and decimal scaling using regular expressions and Zod schemas to ensure data integrity during processing.
  • [CREDENTIALS_UNSAFE]: The skill references environment variables such as CRE_ETH_PRIVATE_KEY and CRE_API_KEY for authentication and operation. However, it follows security best practices by explicitly prohibiting the agent from reading, printing, or logging these values, ensuring they remain opaque to the AI context and are only consumed by the authorized CLI tool.
Audit Metadata
Risk Level
SAFE
Analyzed
Oct 23, 2026, 04:00 PM