Loading the registry…
Covers ANY question about the firm's deals, pipeline, deal sourcing, sourcing attribution, bankers/intermediaries, target companies, interactions, deal history, or deal documents. Triggers even casually: 'what's in the pipeline', 'largest deals', 'who sources our best deals', 'where did this deal come from', 'which bank sourced X', 'what's stuck', 'deal velocity', 'pull up the [company] deal', or any reference to a target company, intermediary, sector, or pipeline stage. IMPORTANT: Claude should read this skill BEFORE calling any Meridian MCP tool for a deal question — a connected Meridian MCP is the cue to use the skill, not to skip it. It governs how to query the Meridian MCP (the live source of truth) AND how to render the result as a visual; querying directly without it yields wrong output. Claude always pulls live from Meridian and says so. Not for portfolio KPIs or LP/fundraising unless tracked as deals.
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 -- 'meridianai/meridianai-mcp-plugin (meridian-deal-intelligence)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'meridianai/meridianai-mcp-plugin (meridian-deal-intelligence)' ~/.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 · 6.7s
v0.3.74
3 findings · 0.6s
v0.1.0
0 findings · 2.6s
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.6s
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
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 17, 2026 | Scan Halted | — | 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 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 8 findings above stand exactly as their scanners reported them, at full severity.