Sardis Escrow
v1.0.0Smart contract escrow for agent-to-agent payments with delivery confirmation
⭐ 0· 209·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, required binaries (curl, jq), and the single required environment variable (SARDIS_API_KEY) are consistent with a REST-based smart-contract escrow integration that performs create/fund/release operations.
Instruction Scope
SKILL.md contains curl commands to the sardis API and example payloads (including delivery proof URLs). The instructions do not ask the agent to read unrelated files or other secrets. They do include operations that will move funds (fund/release) which is expected for an escrow skill.
Install Mechanism
The registry lists no install spec, but the SKILL.md frontmatter includes an install entry referencing an npm package (@sardis/sdk). This is an inconsistency: npm installs can execute code and should be surfaced to users/administrators. The skill as-published is instruction-only (no automatic install), so if an agent or integrator installs @sardis/sdk, they should inspect that package source before installing.
Credentials
Only a single credential (SARDIS_API_KEY) is required and is directly relevant for authorizing requests to the Sardis API. That key represents financial authority — treat it as highly sensitive and scope/revoke it if possible.
Persistence & Privilege
The skill does not request always:true, does not require system config paths, and allows normal autonomous invocation. No elevated or persistent privileges are requested by the skill metadata or instructions.
Assessment
This skill appears to do what it claims (smart-contract escrow via the Sardis API), but verify a few things before installing or using it with real funds:
- Confirm the API domain and project: SKILL.md references https://api.sardis.sh and frontmatter lists homepage https://sardis.sh, but the registry metadata showed no homepage — verify the official project homepage and that the API endpoint is correct.
- Inspect @sardis/sdk before installing: the SKILL.md mentions an npm SDK but the package is not installed automatically in the published skill. If you install the SDK, review its source and permissions first since npm packages can execute arbitrary code.
- Limit and treat SARDIS_API_KEY as highly sensitive: create a key with minimal permissions, keep it secret, and have a revocation plan in case it is exposed.
- Test with small amounts: because the skill can initiate fund movements (fund/release), first test flows on minimal or testnet funds and confirm contract addresses and behavior.
- Confirm dispute/arbitration details: the skill mentions dispute resolution but does not detail how arbitration works or who has final authority; get those policies in writing before committing significant funds.
If you want, I can check whether the npm package @sardis/sdk exists on the registry and summarize its contents or check whether the sardis.sh domain and API endpoints resolve to a legitimate project.Like a lobster shell, security has layers — review code before you run it.
latestvk971z0fhpjxj1r1vygkc52m2ms82gabm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔒 Clawdis
Binscurl, jq
EnvSARDIS_API_KEY
Primary envSARDIS_API_KEY
