Validate JSON syntax and structure using the Expanso Edge pipeline in CLI or MCP server modes.

What to check before installing or using this skill: - Verify you have a trusted expanso-edge binary (the skill expects that binary but the registry metadata didn't declare it). Only run pipelines with a known, official expanso-edge binary. - The default behavior is local parsing, which is coherent with the skill's purpose. However the README/README.md suggests you can deploy the pipeline to Expanso Cloud (https://skills.expanso.io). Avoid deploying pipelines that will process sensitive data unless you understand the cloud provider's policies and authentication requirements. - The pipelines add an input_hash (sha256) and trace_id to metadata. Hashes can sometimes be used to correlate or identify inputs; if you deploy or forward outputs, be aware this metadata will be included. - If you run MCP mode, it binds to 0.0.0.0:${PORT} — ensure you don't expose that port to the public internet unless you want to accept remote JSON submissions. - If you need to be confident this skill is safe: ask the publisher for confirmation of the expanso-edge binary provenance, and whether any optional cloud deployment requires credentials or will store/inspect submitted data. You can also run the skill in an isolated environment and monitor network traffic while feeding non-sensitive test inputs. Confidence notes: medium — the core functionality is locally scoped and clear, but the undocumented runtime dependency and explicit cloud-deploy instructions introduce enough ambiguity about potential data transmission to warrant caution.

Type: OpenClaw Skill Name: expanso-json-validate Version: 1.0.0 The OpenClaw skill 'json-validate' is designed to validate JSON syntax and structure. The `pipeline-cli.yaml` and `pipeline-mcp.yaml` files implement this functionality using Expanso's built-in `parse_json()` function, collecting basic metadata like content hash and length. There are no indications of shell command execution, unauthorized file system access, external network calls (beyond serving an HTTP endpoint in MCP mode), or attempts to exfiltrate sensitive data. The `SKILL.md` and `README.md` files provide usage instructions for the user/agent but do not contain any prompt injection attempts or malicious directives. The `skill.yaml` explicitly states no credentials are required and uses only local processing components.