Security audit
Security checks for vulnerabilities and agentic risk
The skill is a disclosed Checkly CLI documentation and workflow pack, with expected Checkly credentials and cloud-changing commands called out rather than hidden.
Install only if you intend to let an agent help with Checkly CLI workflows. Use a least-privilege Checkly API key/account, review previews and dry-runs before approving deploy, destroy, import commit/cancel, check delete/run, or member changes, and consider pinning the Checkly CLI version in CI instead of relying on floating npx/npm resolution.
The manifest describes the skill primarily as a reference/router, but the body includes instructions for real testing, deployment, imports, deletion-adjacent workflows, and live-account operations. That mismatch can cause an orchestrator or user to grant the skill broader trust or lower scrutiny than warranted, leading to unexpected state-changing actions in production.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Expanded `bundle.packages.embed` guidance for ordered `!` exclusions, `**` cross-scope wildcards, automatic bundle lockfile pruning (including pnpm `patchedDependencies` filtering), Yarn Berry/Bun support, and pnpm `auth.ini` credentials.
- Added `bundle.packages.prune` guidance for dependency-class and workspace-member `remove`/`keep` rules, including lockfile-consistency and runtime-safety constraints.
- Added `runner.registries` routing for runner-only registry overrides with typed upstreams, first-match package rules, mandatory catch-all routing, and environment-reference-only bearer credentials.
- The `.npmrc` trailing-slash auth-key fix (#1448), bare `.` / `..` import resolution, and concurrent cache-write fixes required no separate workflow guidance.
- checkly-cli v8.22.0
- Reviewed upstream release `8.22.0`, compare `8.21.0...8.22.0`, tag `98f1c46`, and relevant source for `bundle.packages.embed` plus `CHECKLY_MQTT_URL` on 2026-08-21.
- Added Playwright Check Suite guidance for embedding private-registry package tarballs with top-level `bundle.packages.embed`, including exact package specs, wildcard matching, lockfile eligibility, integrity checking, cache behavior, and runner dependency-cache implications.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Expanded `bundle.packages.embed` guidance for ordered `!` exclusions, `**` cross-scope wildcards, automatic bundle lockfile pruning (including pnpm `patchedDependencies` filtering), Yarn Berry/Bun support, and pnpm `auth.ini` credentials.
- Added `bundle.packages.prune` guidance for dependency-class and workspace-member `remove`/`keep` rules, including lockfile-consistency and runtime-safety constraints.
- Added `runner.registries` routing for runner-only registry overrides with typed upstreams, first-match package rules, mandatory catch-all routing, and environment-reference-only bearer credentials.
- The `.npmrc` trailing-slash auth-key fix (#1448), bare `.` / `..` import resolution, and concurrent cache-write fixes required no separate workflow guidance.
- checkly-cli v8.22.0
- Reviewed upstream release `8.22.0`, compare `8.21.0...8.22.0`, tag `98f1c46`, and relevant source for `bundle.packages.embed` plus `CHECKLY_MQTT_URL` on 2026-08-21.
- Added Playwright Check Suite guidance for embedding private-registry package tarballs with top-level `bundle.packages.embed`, including exact package specs, wildcard matching, lockfile eligibility, integrity checking, cache behavior, and runner dependency-cache implications.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Expanded `bundle.packages.embed` guidance for ordered `!` exclusions, `**` cross-scope wildcards, automatic bundle lockfile pruning (including pnpm `patchedDependencies` filtering), Yarn Berry/Bun support, and pnpm `auth.ini` credentials.
- Added `bundle.packages.prune` guidance for dependency-class and workspace-member `remove`/`keep` rules, including lockfile-consistency and runtime-safety constraints.
- Added `runner.registries` routing for runner-only registry overrides with typed upstreams, first-match package rules, mandatory catch-all routing, and environment-reference-only bearer credentials.
- The `.npmrc` trailing-slash auth-key fix (#1448), bare `.` / `..` import resolution, and concurrent cache-write fixes required no separate workflow guidance.
- checkly-cli v8.22.0
- Reviewed upstream release `8.22.0`, compare `8.21.0...8.22.0`, tag `98f1c46`, and relevant source for `bundle.packages.embed` plus `CHECKLY_MQTT_URL` on 2026-08-21.
- Added Playwright Check Suite guidance for embedding private-registry package tarballs with top-level `bundle.packages.embed`, including exact package specs, wildcard matching, lockfile eligibility, integrity checking, cache behavior, and runner dependency-cache implications.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Expanded `bundle.packages.embed` guidance for ordered `!` exclusions, `**` cross-scope wildcards, automatic bundle lockfile pruning (including pnpm `patchedDependencies` filtering), Yarn Berry/Bun support, and pnpm `auth.ini` credentials.
- Added `bundle.packages.prune` guidance for dependency-class and workspace-member `remove`/`keep` rules, including lockfile-consistency and runtime-safety constraints.
- Added `runner.registries` routing for runner-only registry overrides with typed upstreams, first-match package rules, mandatory catch-all routing, and environment-reference-only bearer credentials.
- The `.npmrc` trailing-slash auth-key fix (#1448), bare `.` / `..` import resolution, and concurrent cache-write fixes required no separate workflow guidance.
- checkly-cli v8.22.0
- Reviewed upstream release `8.22.0`, compare `8.21.0...8.22.0`, tag `98f1c46`, and relevant source for `bundle.packages.embed` plus `CHECKLY_MQTT_URL` on 2026-08-21.
- Added Playwright Check Suite guidance for embedding private-registry package tarballs with top-level `bundle.packages.embed`, including exact package specs, wildcard matching, lockfile eligibility, integrity checking, cache behavior, and runner dependency-cache implications.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Expanded `bundle.packages.embed` guidance for ordered `!` exclusions, `**` cross-scope wildcards, automatic bundle lockfile pruning (including pnpm `patchedDependencies` filtering), Yarn Berry/Bun support, and pnpm `auth.ini` credentials.
- Added `bundle.packages.prune` guidance for dependency-class and workspace-member `remove`/`keep` rules, including lockfile-consistency and runtime-safety constraints.
- Added `runner.registries` routing for runner-only registry overrides with typed upstreams, first-match package rules, mandatory catch-all routing, and environment-reference-only bearer credentials.
- The `.npmrc` trailing-slash auth-key fix (#1448), bare `.` / `..` import resolution, and concurrent cache-write fixes required no separate workflow guidance.
- checkly-cli v8.22.0
- Reviewed upstream release `8.22.0`, compare `8.21.0...8.22.0`, tag `98f1c46`, and relevant source for `bundle.packages.embed` plus `CHECKLY_MQTT_URL` on 2026-08-21.
- Added Playwright Check Suite guidance for embedding private-registry package tarballs with top-level `bundle.packages.embed`, including exact package specs, wildcard matching, lockfile eligibility, integrity checking, cache behavior, and runner dependency-cache implications.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Expanded `bundle.packages.embed` guidance for ordered `!` exclusions, `**` cross-scope wildcards, automatic bundle lockfile pruning (including pnpm `patchedDependencies` filtering), Yarn Berry/Bun support, and pnpm `auth.ini` credentials.
- Added `bundle.packages.prune` guidance for dependency-class and workspace-member `remove`/`keep` rules, including lockfile-consistency and runtime-safety constraints.
- Added `runner.registries` routing for runner-only registry overrides with typed upstreams, first-match package rules, mandatory catch-all routing, and environment-reference-only bearer credentials.
- The `.npmrc` trailing-slash auth-key fix (#1448), bare `.` / `..` import resolution, and concurrent cache-write fixes required no separate workflow guidance.
- checkly-cli v8.22.0
- Reviewed upstream release `8.22.0`, compare `8.21.0...8.22.0`, tag `98f1c46`, and relevant source for `bundle.packages.embed` plus `CHECKLY_MQTT_URL` on 2026-08-21.
- Added Playwright Check Suite guidance for embedding private-registry package tarballs with top-level `bundle.packages.embed`, including exact package specs, wildcard matching, lockfile eligibility, integrity checking, cache behavior, and runner dependency-cache implications.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
// Note: API_TOKEN is a user-defined environment variable for YOUR API checks.
// It is NOT required by Checkly CLI itself. Define it in your .env or CI secrets
// based on your application's authentication needs.
new ApiCheck('authenticated-api-check', {
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
// Note: API_TOKEN is a user-defined environment variable for YOUR API checks.
// It is NOT required by Checkly CLI itself. Define it in your .env or CI secrets
// based on your application's authentication needs.
new ApiCheck('authenticated-api-check', {
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
// Note: API_TOKEN is a user-defined environment variable for YOUR API checks.
// It is NOT required by Checkly CLI itself. Define it in your .env or CI secrets
// based on your application's authentication needs.
new ApiCheck('authenticated-api-check', {
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
// Note: API_TOKEN is a user-defined environment variable for YOUR API checks.
// It is NOT required by Checkly CLI itself. Define it in your .env or CI secrets
// based on your application's authentication needs.
new ApiCheck('authenticated-api-check', {
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
// Note: API_TOKEN is a user-defined environment variable for YOUR API checks.
// It is NOT required by Checkly CLI itself. Define it in your .env or CI secrets
// based on your application's authentication needs.
new ApiCheck('authenticated-api-check', {
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Local Development:
# .env.local (add to .gitignore)
# Example variables for YOUR checks - NOT required by Checkly CLI itself
API_TOKEN=dev-token-123 # Example: if your API check needs auth
TEST_EMAIL=test@example.com # Example: if your browser check tests login
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Local Development:
# .env.local (add to .gitignore)
# Example variables for YOUR checks - NOT required by Checkly CLI itself
API_TOKEN=dev-token-123 # Example: if your API check needs auth
TEST_EMAIL=test@example.com # Example: if your browser check tests login
The skill declares required binaries and environment variables but does not define any explicit tool scope such as allowed-tools or permissions. In an agent setting, that can let the runtime infer or grant broader shell/env access than users expect, increasing the chance of unintended command execution or secret exposure.
MCP server references in the skill manifest without version pinning are a rug-pull risk.
MCP server references in the skill manifest without version pinning are a rug-pull risk.
Referencing npx checkly without pinning a version allows the agent to fetch and execute whatever package version is current at runtime. That creates a supply-chain risk: a compromised upstream release or unexpected breaking change could alter behavior, execute malicious code, or bypass reviewed safety expectations.
Referencing npx checkly without pinning a version allows the agent to fetch and execute whatever package version is current at runtime. That creates a supply-chain risk: a compromised upstream release or unexpected breaking change could alter behavior, execute malicious code, or bypass reviewed safety expectations.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
"kind": "node",
"package": "checkly",
"bins": ["checkly"],
"label": "Create Checkly project (npm)",
"command": "npm create checkly@latest",
},
{
This line instructs use of unpinned npx checkly, which may download and execute an unreviewed package version at runtime. In an agent workflow, that turns documentation into an implicit remote-code execution path controlled by the package registry state.
This unversioned npx checkly invocation carries supply-chain execution risk because package contents are resolved dynamically. An attacker controlling or poisoning the package or its dependencies could execute arbitrary code in the agent environment.
The skill instructs an unpinned npx checkly command, which can fetch different code over time. That undermines reproducibility and opens a direct package-registry supply-chain path to code execution.
Using floating npx checkly means the actual executed code is not fixed at authoring time. In an agent context, this is dangerous because the skill can cause remote package retrieval and execution with user credentials or repository access present.
An unpinned npx checkly command can resolve to any current release, including a malicious or incompatible one. That creates a time-of-use code execution risk not covered by static review of this skill file.
No suspicious patterns detected.