Loading the registry…
Activate when the user is WRITING APPLICATION CODE that programmatically interacts with a Kinetica GPU database — Python or Node apps, microservices, ETL scripts, or streaming data pipelines that import the gpudb SDK, call the Kinetica REST API from app code, or wire up Kinetica connectors (Spark, Kafka, JDBC, Airflow, Flink). Trigger on requests like "write a Python script that ingests this CSV into Kinetica", "build a FastAPI endpoint backed by Kinetica", "set up a Kafka to Kinetica pipeline", "use the gpudb client to upsert records", or any request for source code the user will save, version, and run as part of an application. Do NOT use for ad-hoc SQL, one-off table inspection, schema exploration, admin commands, or map tile rendering — those go to kinetica-execute.
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 -- 'kineticadb/agent-skills (kinetica-code)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'kineticadb/agent-skills (kinetica-code)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 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
90 findings · 18.9s
v0.3.74
14 findings · 5.3s
v0.1.0
0 findings · 6.1s
v0.1.0
19 findings · 6.1s
v2.3.8
0 findings · 1.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 · 1.6s
v0.71.0
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 18, 2026 | Flagged70 | — | 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: completetrivy_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 123 findings above stand exactly as their scanners reported them, at full severity.