Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Work with JSON data structures, APIs, and serialization effectively.
Work with JSON data structures, APIs, and serialization effectively.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Always validate against JSON Schema before processing untrusted input—don't assume structure Define schemas for API responses—catches contract violations early Use additionalProperties: false to reject unknown fields in strict contexts
Pick one convention and stick to it—camelCase for JS ecosystems, snake_case for Python/Ruby Avoid mixed conventions in same payload—userId alongside user_name confuses consumers Use plural for collections: "users": [] not "user": []
Distinguish "field is null" from "field is absent"—they mean different things Omit optional fields entirely rather than sending null—reduces payload, clearer intent Document which fields are nullable in schema—don't surprise consumers
Always use ISO 8601: "2024-01-15T14:30:00Z"—no ambiguous formats like "01/15/24" Include timezone or use UTC with Z suffix—local times without zone are useless Timestamps as strings, not epoch integers—human-readable, no precision loss
Large IDs as strings: "id": "9007199254740993"—JavaScript loses precision above 2^53 Money as string or integer cents—never float: "price": "19.99" or "price_cents": 1999 Avoid floats for anything requiring exactness—currency, coordinates with precision
Keep nesting shallow—3 levels max; flatten or split into related endpoints Consistent envelope for APIs: {"data": ..., "meta": ..., "errors": ...} Paginate large arrays—never return unbounded lists; include next/prev links or cursor
Errors as structured objects: {"code": "INVALID_EMAIL", "message": "...", "field": "email"} Include request ID in responses for debugging: "request_id": "abc-123" Return created/updated resource in response—saves client a follow-up GET
toJSON() method silently overrides output—Date becomes string, custom classes may surprise Map, Set, BigInt don't serialize—need custom replacer function Circular references throw—detect cycles before stringify or use libraries like flatted Strip sensitive data before serializing—don't rely on client to ignore extra fields
__proto__ key can pollute prototypes—sanitize input or use Object.create(null) Parse in try/catch—malformed JSON from external sources is common Reviver function for type reconstruction: dates, BigInt, custom types
Emoji need surrogate pairs in escapes: 😀 = \uD83D\uDE00—single \u1F600 invalid Control chars U+0000–U+001F must be escaped—pasted text may contain invisible ones BOM at file start breaks parsing—strip \uFEFF from file input
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.