Content
71%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A high-density, highly actionable body that assumes competence and provides copy-paste-ready commands across GitHub, GitLab, and CircleCI, with an explicit safety decision gate. The main weaknesses are the monolithic single-file structure (no progressive disclosure despite 185 lines, plus dangling references to sibling skills) and a few placeholder-stubbed paths (GCP exchange).
Suggestions
Split provider-specific detail into reference files (e.g., references/gitlab-job-token.md, references/detection-signatures.md) and link them from the body, turning the 185-line monolith into an overview with one-level-deep references.
Complete or remove stubbed guidance: either give the GCP Workload Identity Federation exchange commands or drop the section, and resolve placeholders like <COLLAB>, <OTHER_PROJECT_ID>, and $AWS_ROLE_ARN with sourcing instructions.
Move time-sensitive claims ("default historically", CVE-2025-30066, the tj-actions incident) into a clearly-labeled incidents/version-notes section, and fix or remove the dangling references to poisoned-pipeline-execution/ and github-actions-injection/.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and command-first, assuming Claude's competence (env-var maps are bare comments, no library tutorials). A few things could be trimmed: the SLSA narrative sentence, re-explanations like "GITHUB_TOKEN is short-lived (job duration) and not exfilable to durable infra", and time-sensitive claims ("default historically", CVE-2025-30066) that are not quarantined in a deprecated/old-patterns section. | 4 / 5 |
Actionability | Nearly every section gives copy-paste-ready commands with real flags (e.g., the curl OIDC mint, "aws sts assume-role-with-web-identity --duration-seconds 900", the gh API calls). Minor gaps keep it below 5: the GCP Workload Identity Federation exchange is only a comment, and $AWS_ROLE_ARN, <COLLAB>, <OTHER_PROJECT_ID>, and RUN_ID are unresolved placeholders. | 4 / 5 |
Workflow Clarity | Sections form a coherent progression (surface map → env inventory → masking bypass → OIDC → token abuse → cleanup) and the numbered Decision gate supplies explicit validation checkpoints (proof-not-secret limits, scrub artifacts before declaring done), satisfying the destructive-operation validation requirement. It is not 5 because the main exploitation flow is never explicitly ordered — sequence must be inferred from heading arrangement. | 4 / 5 |
Progressive Disclosure | Headers are clear, but this is a single ~185-line file with no bundle files at all: the per-provider deep-dives (GitLab job-token pivot, CircleCI), the detection-signatures table, and the tools table are natural candidates for references/. Additionally, the body cites "poisoned-pipeline-execution/" and "github-actions-injection/" which do not exist in the bundle, and the >50-line simple-skill exception does not apply. | 3 / 5 |
Total | 15 / 20 Passed |