/install analyze-json-data
Core Position
This skill solves the specific engineering problem described in the trigger conditions. It focuses on reliable, auditable execution with clear error reporting.
Modes
/analyze-json-data
Default mode. Performs the core task with standard configuration.
/analyze-json-data --verbose
Verbose mode. Includes detailed logging and intermediate results.
Execution Steps
- Parse input — Validate and parse the input data; report any structural issues
- Validate — Confirm all required fields/parameters are present and well-formed
- Execute — Perform the transformation/action with validated input
- Verify — Check the output is well-formed and complete
- Report — Return structured output with a brief summary of what was done
Mandatory Rules
Do not
- Do not make up facts or claim actions were taken that were not
- Do not hardcode API keys — use
os.getenv("API_KEY")instead - Do not store sensitive user data beyond the current session
- Do not exceed token budget without warning the user first
- Do not activate for off-topic requests — return a brief decline message
Do
- Validate all inputs before acting
- Handle errors gracefully with actionable error messages
- Log actions taken for auditability
- State explicitly when you are uncertain or data is insufficient
Quality Bar
| Criterion | Minimum | Ideal |
|---|---|---|
| Task completion | Core task completes without error | Full task with all edge cases handled |
| Error reporting | Clear error message on failure | Actionable error with suggested fix |
| User communication | Brief summary of what was done | Detailed log with reasoning for decisions |
| Input validation | Rejects malformed input | Accepts valid input, explains rejection for invalid |
A good output is one where all edge cases are handled gracefully with clear user communication.
Good vs. Bad Examples
| Scenario | Bad | Good |
|---|---|---|
| Task unclear | Attempts anyway, may be wrong | Asks for clarification before proceeding |
| Error | Technical error message | "Cannot [action]: [reason] — suggest [alternative]" |
| Partial success | Reports "Done" | Reports "Done, but [partial] not completed — see details" |
| Edge case | Silently skips or crashes | Documents edge case and handles gracefully |
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install analyze-json-data - After installation, invoke the skill by name or use
/analyze-json-data - Provide required inputs per the skill's parameter spec and get structured output
What is Analyze Json Data?
Use when (1) Analyze JSON data and generate a structured API design document or OpenAPI specification. It is an AI Agent Skill for Claude Code / OpenClaw, with 55 downloads so far.
How do I install Analyze Json Data?
Run "/install analyze-json-data" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Analyze Json Data free?
Yes, Analyze Json Data is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Analyze Json Data support?
Analyze Json Data is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Analyze Json Data?
It is built and maintained by 王继鹏 (@wangjipeng977); the current version is v1.0.1.