Loading the registry…
Read and explain a Mixpanel report or chart — what it shows, what's notable, and what's worth a closer look. Use whenever the user asks to interpret, explain, summarize, review, or break down an existing chart, report, or saved query in Mixpanel. Trigger phrases: "what does this chart show", "explain this report", "interpret this chart", "summarize this for me", "what's notable here", "anything weird in this chart", "tell me what's happening", "review this insight", "walk me through this report", "what's the takeaway from this". Also trigger when the user pastes a Mixpanel chart or report URL and asks anything about it. Lean by default — surfaces what the report shows and flags notable patterns, but does not chase root causes. Do NOT trigger for building new charts, reviewing entire dashboards, or full root-cause diagnostic workflows (for "why did this change" questions, use monitor-metrics). Requires a Mixpanel engine — run /mixpanel:install if not set up.
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 -- 'mixpanel/ai-plugins (analyze-report)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'mixpanel/ai-plugins (analyze-report)' ~/.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
0 findings · 0.6s
v2.0.11
44 findings · 10.7s
v0.3.74
5 findings · 1.5s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
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 · 0.9s
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
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
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 21, 2026 | Flagged79 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-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: not applicablegovulncheck ·n/a: not applicable | 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 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 49 findings above stand exactly as their scanners reported them, at full severity.