Expanso json-pretty

v1.0.0

Formats and pretty-prints JSON input with indentation using Expanso Edge pipelines for easy readability.

0· 782·1 current·1 all-time
byExpanso@aronchick
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name, SKILL.md, skill.yaml and pipeline YAML files all align: the skill's sole purpose is to parse and reformat JSON (CLI and HTTP/MCP modes). Required components (expanso-edge) match the stated purpose.
Instruction Scope
Runtime instructions only tell the agent to run expanso-edge with the provided pipeline files, run an MCP HTTP endpoint, or deploy to Expanso Cloud. The pipelines only parse/format JSON and add metadata. One operational note: the MCP pipeline enables an unauthenticated HTTP endpoint (0.0.0.0:${PORT:-8080} /format), which is expected for an HTTP formatting service but could be exposed if started on a public network.
Install Mechanism
There is no install specification and no code to download or execute; this is instruction-only and relies on the expanso-edge binary being present. Low install risk.
Credentials
The skill declares no required environment variables, no credentials, and skill.yaml has empty credentials. The files and instructions do not reference secrets or unrelated environment variables.
Persistence & Privilege
always is false and the skill does not request persistent system-level privileges or modify other skills' config. Autonomous invocation is allowed (platform default) but the skill's scope is limited.
Assessment
This skill appears to do exactly what it says: pretty-print JSON using Expanso pipelines. It requires the expanso-edge binary to run and provides two modes (CLI and an HTTP server). There are no requested secrets. If you start the MCP HTTP server, be aware it binds to 0.0.0.0 by default and has no built-in authentication—avoid running it on a public interface unless you add network-level protections. Otherwise it is safe and coherent with its stated purpose.

Like a lobster shell, security has layers — review code before you run it.

latestvk97a57xd76tsa9paw2hkccvbqs80xf4k

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments