Loading the registry…
Use proactively while helping the user operate a coding agent on a real codebase — when they write a prompt, plan a change, run a build/test, commit, or show an agentic anti-pattern (vague ask, "don't do X" phrasing, no plan, no executable definition of done, "it works" with no proof, editing tests to pass, secrets in the repo/prompt, dumping the whole repo as context, begging "think hard", one agent on a huge job). ALSO use whenever the user says "coach", "coach me", or "coach this" (engage fully), or asks "why" or "how to / how do I" about how they're operating the agent (teach the answer from the guide). Surface the single most relevant tip from the Professional Agentic Product Engineering guide, briefly, then continue the task. Do not use during a structured tutoring session.
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 cisco-skill-scanner. 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 -- 'krivitsky/professional-agentic-product-engineering (agentic-coach)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'krivitsky/professional-agentic-product-engineering (agentic-coach)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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.
v1.4.0
5 findings · 0.9s
v2.0.11
17 findings · 15.5s
v0.3.74
4 findings · 3.1s
v0.1.0
0 findings · 6.4s
v0.1.0
3 findings · 6.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.3s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.4s
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 18, 2026 | Scan Halted | — | agentshield: completecisco-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.
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 29 findings above stand exactly as their scanners reported them, at full severity.