What makes Verifiable Data notable?

1.2K downloads. Trust evidence available

How should Verifiable Data be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Verifiable Data

Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wa... Skill: Verifiable Data Owner: i001962 Summary: Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wa... Tags: latest:1.0.3 Version history: v1.0.3 | 2026-04-22T05:06:19.646Z | user Reduce purchase and crypto classifier signals v1.0.2 | 2026-04-22T05:03:23.029Z | user Clarify skill does not make purchases v1.0.1 | 2

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 2026

Version

1.0.3

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.3release · observed Apr 22, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s173v0pjfvbr4r8me40hw2tfsn84yje2:verifiable-data

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-i001962-verifiable-data/snapshot"

Documentation

CLAWHUB

23,985 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: verifiable-data
description: Use Cryptowerk via curl to obtain service credentials, register hashes, fetch seals, and verify proofs for files or append-only records. Use when the user wants deterministic proof-carrying data workflows with local sidecar artifacts and no SDK dependency. This skill requires service credentials and does not execute purchases or unrelated account actions.
metadata:
{
"openclaw":
{
"requires":
{
"bins": ["curl", "python3"],
"env": ["CRYPTOWERK_X_API_KEY"],
},
},
}
---

# Verifiable Data

Use this skill for Cryptowerk-backed proof workflows with simple curl scripts.

Supported primitives:
- obtain a fresh service credential
- register a SHA-256 hash
- fetch a seal by retrieval id
- verify a hash against a seal

Default style:
- shell-first
- curl-first
- sidecar files for local state
- no SDK dependency

## When to use

Use this skill when the user wants:
- verifiable logs
- proof of file existence
- Cryptowerk sealing
- retrieval IDs and seals stored locally
- deterministic local artifacts for later audit

## Workflow

1. Obtain a fresh service credential with `scripts/issue-key.sh`
2. Export the returned token as `CRYPTOWERK_X_API_KEY`
3. Register a file hash with `scripts/register-file.sh`
4. Poll for a seal with `scripts/get-seal.sh`
5. Verify with `scripts/verify-file.sh`

## Requirements

Required binaries:
- `curl`
- `python3`
- one of `shasum`, `sha256sum`, or `openssl`

Credential handling:
- `scripts/issue-key.sh` can write a fresh token to a file you choose
- runtime scripts expect `CRYPTOWERK_X_API_KEY` to contain the exact combined token value
- keep issued tokens out of watched or committed trees
- the skill uses service credentials only for the documented proof APIs

## Quick start

### Obtain a fresh service credential

```bash
scripts/issue-key.sh ~/.secrets/cryptowerk.issue-key.cap
export CRYPTOWERK_X_API_KEY="$(cat ~/.secrets/cryptowerk.issue-key.cap)"
```

### Register a file

```bash
scripts/register-file.sh /path/to/file.txt record:file.txt
```

### Fetch a seal

```bash
scripts/get-seal.sh /path/to/file.txt.rid
```

### Verify a file

```bash
scripts/verify-file.sh /path/to/file.txt /path/to/file.txt.seal
```

## Local artifacts

- `<file>.rid`
- `<file>.seal`
- `<file>.cw.json`
- `<file>.verify.json`

## Rules

- Use SHA-256 over exact raw bytes.
- Keep issued Cryptowerk tokens outside watched trees.
- Save new keys to fresh files, do not overwrite old credentials by default.
- Prefer deterministic `lookupInfo` values.
- Default file workflow lookupInfo may be `sha256:<digest>` when none is supplied.
- Persist failures locally instead of silently discarding them.

## References

Read these when needed:
- `references/cryptowerk-api-notes.md`
- `references/storage-and-state.md`

## Scripts

- `scripts/issue-key.sh`
- `scripts/register-file.sh`
- `scripts/get-seal.sh`
- `scripts/verify-file.sh`

_meta.json

{
  "ownerId": "kn71ymyc5p9wfb0gpxzq48y5ws820mj1",
  "slug": "verifiable-data",
  "version": "1.0.3",
  "publishedAt": 1776834379646
}

references/cryptowerk-api-notes.md

# Cryptowerk API Notes

Known working curl-based flow:

1. `POST https://www.cryptowerk.com/api/issue-key`
   - may return `402` with x402 payment challenge
   - after successful paid retry, returns JSON with:
     - `apiKey`
     - `apiCredential`
     - `requesterId`
   - in some middleware configurations, may return `200` directly without x402

2. `POST https://aiagent.cryptowerk.com/platform/API/v8/register`
   - send `X-API-Key: <apiKey> <apiCredential>`
   - use query params `hashes` and optional `lookupInfo`
   - returns `documents[0].retrievalId`

3. `POST https://aiagent.cryptowerk.com/platform/API/v8/getseal`
   - send `X-API-Key: <apiKey> <apiCredential>`
   - use query params `retrievalId` and `provideVerificationInfos=true`
   - may return pending before a seal exists

4. `POST https://aiagent.cryptowerk.com/platform/API/v8/verifyseal`
   - send `X-API-Key: <apiKey> <apiCredential>`
   - use query params `verifyDocHashes` and `seals`

Important field note:
- issue-key returns `apiCredential`, not `credential`
- stored combined token format should be:
  - `apiKey apiCredential`

Operational note:
- `issue-key.sh` writes a fresh token only when you pass an output path
- `register-file.sh`, `get-seal.sh`, and `verify-file.sh` require `CRYPTOWERK_X_API_KEY`
- required local tools are `curl`, `python3`, and one SHA-256 provider (`shasum`, `sha256sum`, or `openssl`)

references/storage-and-state.md

# Storage and State

Recommended local sidecars:

- `<file>.rid` for retrieval id
- `<file>.seal` for getseal JSON
- `<file>.cw.json` for local metadata
- `<file>.verify.json` for verify response JSON

Recommended metadata fields:

- `version`
- `sourcePath`
- `lookupInfo`
- `sha256`
- `retrievalId`
- `registeredAt`
- `sealPath`
- `verifyPath`
- `lastSealReceivedAt`
- `lastVerifiedAt`
- `lastError`

Credential storage:

- save issued credentials to a fresh secret path
- format: `apiKey apiCredential`
- restrict file permissions
- avoid storing credentials inside watched data trees

skill-card.md

## Description:

Verifiable Data helps agents use Cryptowerk curl workflows to issue service credentials, register SHA-256 hashes, retrieve seals, and verify file or append-only record proofs while storing local sidecar artifacts.

This skill is ready for commercial/non-commercial use.

## Publisher:

[i001962](https://clawhub.ai/user/i001962)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and engineers use this skill to create proof-carrying data workflows for verifiable logs, file existence proofs, Cryptowerk sealing, retrieval IDs, and later audit verification.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill issues and stores Cryptowerk service credentials without strong overwrite or symlink safeguards.

Mitigation: Use a private non-repository secret path, avoid reusing existing file paths for issued keys, and review credential paths before running credential scripts.

Risk: Lookup values and sidecar files may expose sensitive filenames, identifiers, or workflow metadata.

Mitigation: Use deterministic but non-sensitive lookupInfo values and keep generated .rid, .seal, .cw.json, and .verify.json files out of committed or watched trees when they are sensitive.

## Reference(s):

- [ClawHub skill page](https://clawhub.ai/i001962/skills/verifiable-data)
- [Cryptowerk API Notes](references/cryptowerk-api-notes.md)
- [Storage and State](references/storage-and-state.md)
- [Cryptowerk issue-key API](https://www.cryptowerk.com/api/issue-key)
- [Cryptowerk register API](https://aiagent.cryptowerk.com/platform/API/v8/register)
- [Cryptowerk getseal API](https://aiagent.cryptowerk.com/platform/API/v8/getseal)
- [Cryptowerk verifyseal API](https://aiagent.cryptowerk.com/platform/API/v8/verifyseal)

## Skill Output:

**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Files, Guidance]

**Output Format:** [Markdown with inline shell commands and JSON sidecar files]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Produces local .rid, .seal, .cw.json, and .verify.json sidecar artifacts when workflows are executed.]

## Skill Version(s):

1.0.3 (source: server release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.