Iot Witness Verify
- 640 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
iot-witness-verify is an agent skill that verifies witness chain integrity and detects provenance gaps on Cognitum Seed devices for developers auditing device telemetry trustworthiness.
About
iot-witness-verify is a ruvnet/ruflo skill that verifies witness chain integrity for a Cognitum Seed device by running npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot witness verify DEVICE_ID. It checks for epoch gaps and hash chain breaks, reporting an integrity score from 0.0 to 1.0. When gaps are found, agents store audit trail entries via mcp__claude-flow__memory_store under the iot-audit namespace with keys like iot-witness-gap-DEVICEID. Allowed tools include Bash(npx *), memory_store, and Read. Developers reach for iot-witness-verify when device provenance must be validated before trusting telemetry history or during compliance investigations on IoT audit trails. Catalog metadata lists 440 installs. iot-witness-verify complements iot-anomalies by proving chain-of-custody integrity rather than only statistical metric deviations.
- iot-witness-verify
Iot Witness Verify by the numbers
- 640 all-time installs (skills.sh)
- +6 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #599 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill iot-witness-verifyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 640 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you verify IoT witness chain integrity?
Use iot-witness-verify for development tasks
Who is it for?
Developers auditing Cognitum Seed device provenance who need witness chain verification and epoch-gap detection before trusting telemetry.
Skip if: Developers without Cognitum IoT witness chains or teams only needing application-level auth logs without device provenance verification.
When should I use this skill?
User asks to verify witness chain integrity, detect provenance gaps, or audit Cognitum Seed device epoch continuity.
What you get
Witness integrity score (0.0–1.0), epoch gap report, hash chain break findings, and iot-audit memory_store trail entries.
- Integrity score report
- Epoch gap findings
- iot-audit memory entries
By the numbers
- Reports witness integrity score on a 0.0 to 1.0 scale
- Stores gap audit entries in iot-audit memory namespace
Files
Verify the witness chain integrity for a Cognitum Seed device.
Steps: 1. npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot witness verify DEVICE_ID 2. Check for epoch gaps and hash chain breaks 3. Report integrity score (0.0–1.0) 4. If gaps found, store for audit trail: mcp__claude-flow__memory_store({ key: "iot-witness-gap-DEVICEID", value: "Gap from EPOCH to EPOCH", namespace: "iot-audit" })
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Pick iot-witness-verify for provenance chain audits instead of iot-anomalies when the question is witness integrity rather than statistical telemetry deviation.
FAQ
What does iot-witness-verify check?
iot-witness-verify checks witness chain integrity on Cognitum Seed devices, detecting epoch gaps and hash chain breaks. It reports an integrity score from 0.0 to 1.0 indicating how trustworthy the provenance chain is.
How are witness gaps stored?
iot-witness-verify stores gap findings via mcp__claude-flow__memory_store under the iot-audit namespace with keys like iot-witness-gap-DEVICEID, recording gap epochs for later compliance review.
Which CLI command does iot-witness-verify run?
iot-witness-verify executes npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot witness verify with a device-id argument-hint to validate the full witness chain on the target device.