Is Ololand Forensic Qoe Verify safe and trustworthy?

tashan scores Ololand Forensic Qoe Verify on public evidence — it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Ololand Forensic Qoe Verify?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Ololand Forensic Qoe Verify?

2 GitHub contributors, source: ololand-ai/ololand-plugins.

‹ The Index

Ololand Forensic Qoe Verify

skill

Use when the user asks to run the OloLand /verify workflow. Verify every dollar and percentage figure in an externally-drafted artifact (an IC memo, analysis, or answer — e.g. one drafted in Claude Cowork) against an OloLand deal's INGESTED data room. For each figure, evidence is retrieved per-claim from the corpus (not pasted by you) — so it confirms a number against the real source, or flags a source elsewhere in the data room that contradicts it, including evidence the author never cited. Per-figure PASS / FAIL / UNVERIFIED with corpus number reconciliation, an NLI derivation check, an independent grader, and a content-hashed provenance pack. …

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Security — see all ranked ›

Install (Claude Code):

cp -r ololand-forensic-qoe-verify ~/.claude/skills/

Adoption: 1 repos
Upkeep: 79.0
Freshness: 94.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 2
License: Apache-2.0

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when to use it, says when not to, shows worked examples and covers setup.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Pro adds the history to tashan doctor, so a run over your own config says which of yours gained an advisory, started running an install script, or lost its last maintainer — and what to move to.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

source ↗ · skill:ololand-ai/ololand-forensic-qoe-verify

Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-14 · scorer s5 · how · something wrong here?