Loading the registry…
Interactively set up an AWS CodePipeline + CodeBuild CI/CD pipeline, step by step. On entry, ask the user about the use case and recommend V1 (commit push deployment) or V2 (PR pre-merge) accordingly, then let the user pick V1, V2, or both. Claude executes CodeStar Connection, IAM roles, S3 artifact bucket, CodeBuild projects, and CodePipeline creation directly via AWS CLI with per-step user approval. Manual tasks such as setting environment variables, issuing the GitHub PAT, storing it in Secrets Manager, and approving the CodeStar Connection in the AWS Console are never performed by Claude; Claude only explains what the user should do. Triggers: "set up CodePipeline", "build CI/CD pipeline", "create AWS deploy pipeline", "pre-merge pipeline", "codepipeline setup", "aws cicd configuration", "CodePipeline V1", "CodePipeline V2", "commit push deploy pipeline", "PR validation pipeline". Use this skill whenever the user wants AWS-native CI/CD on GitHub sources, even when they don't use the word "pipeline" (e.g. "make auto-deploy on AWS", "run build on every PR").
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'heemanglee/claude-plugins (aws-codepipeline-setup)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'heemanglee/claude-plugins (aws-codepipeline-setup)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
3 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
5 findings · 7.2s
v0.3.74
1 finding · 0.6s
v0.1.0
0 findings · 2.9s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 2.9s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.0s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Caution92 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a |
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
| completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Caution badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 6 findings above stand exactly as their scanners reported them, at full severity.