Design, run, and systematize A/B tests and experimentation programs. Triggers on 'A/B test,' 'split test,' 'run an experiment,' 'test this change,' 'statistical significance,' 'ICE score,' or 'experiment backlog.' For tracking implementation, see analytics-tracking. For page-level conversion optimization, see conversion-optimization.
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.
1 critical finding reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'bulldozer-collective/bulldozer-claude-marketplace (ab-testing )'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'bulldozer-collective/bulldozer-claude-marketplace (ab-testing )' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 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
288 findings · 15.3s
v0.3.74
147 findings · 4.7s
v0.1.0
10 findings · 5.8s
v0.1.0
0 findings · 5.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
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
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
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 Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 445 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 445 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
443 The model's answer could not be read.
Rules: AAK-MCP-001, AAK-SKILL-004, opt.nerlo-rules.nerlo-py-secret-to-network-egress and 25 more · Files: plugins/bulldozer-external/.mcp.json, plugins/bulldozer-external/skills/market-signals/SKILL.md, plugins/bulldozer-external/skills/sales-compensation/SKILL.md and 257 more · reported by agent-audit-kit, nerlo-behavioral, cisco-skill-scanner
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: BINARY_FILE_DETECTED, MANIFEST_INVALID_NAME · Files: /repo/plugins/bulldozer-external/skills/lead-magnet-assets/.DS_Store, /repo/plugins/bulldozer-external/skills/audit-content/SKILL.md · reported by cisco-skill-scanner
Critical and high severity findings require review
The artifact contains a critical finding related to an MCP configuration file and multiple high severity findings. These include potential marketplace configuration issues, unauthenticated default settings in a script, and several instances of Server-Side Request Forgery (SSRF) redirection in various scripts. Additionally, there are high severity findings for OAuth configuration and a secret present in a Google authentication script.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Showing 25 of 25; the rest are in the per-scanner reports above.