GitHub Actions Troubleshooting
Analysis
This instruction-only skill is coherent for troubleshooting GitHub Actions, though it can use your GitHub CLI access to view or download workflow logs and artifacts.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Download workflow artifacts for inspection: `gh run download <run-id> --repo owner/repo` ... Run `go mod tidy` to resolve dependency conflicts
The documented workflow includes CLI commands that can download files and modify Go dependency files. This is aligned with CI troubleshooting, but should be scoped to the intended repo and reviewed before committing changes.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Use the `gh` CLI and Git to diagnose and fix GitHub Actions workflow failures ... `gh run view <run-id> --repo owner/repo --log-failed` ... `gh run download <run-id> --repo owner/repo`
These commands retrieve GitHub workflow status, logs, and artifacts. The GitHub CLI normally acts with the user's GitHub account permissions, so private repository CI data may be accessed.
