json-render-core
Core package for defining schemas, catalogs, and AI prompt generation for json-render. Use when working with @json-render/core, defining schemas, creating catalogs, or building JSON specs for UI/video generation.

Install the complete plugin to include its agents, hooks, commands, and runtime context.
- PUBLISHER
- vercel-labs
- RELATIONSHIP
- vendored
- VERSION
- 1.0.0
- BENCHMARK
- unknown
Install bOpen Mcp
The complete plugin is the supported path. It preserves everything the publisher designed to work alongside this skill.
Codex
VERIFIEDGrok Build
VERIFIED- This is the grok CLI, not Grok Bot.
- grok plugin details mcp-dev
Grok Bot
GUIDED SETUP- Paste this request into your Bot’s conversation. It will report what it can add.
OpenCode
VERIFIED- Paste into OpenCode. Restart after installation.
- Includes native agents, commands, skills and supported hooks/MCP. HammerTime uses bounded follow-up turns in persistent sessions.
Install only this skill
Use this narrower path only when you intentionally want the portable SKILL.md without the plugin’s surrounding capabilities.
Skills CLI
VERIFIED- Installs only the portable skill; it omits plugin hooks, agents, commands, apps/MCP configuration, and unlisted companion skills.
Grok Bot
GUIDED SETUP- Paste into your Bot’s conversation. Once saved, use / to select the skill.
Trace it to the source.
- DISTRIBUTED SOURCE
- modules/mcp-dev/.agents/skills/json-render-core/SKILL.md ↗
- UPSTREAM SOURCE
- vercel-labs/json-render
- DISTRIBUTED DIGEST
- sha256:b83a37312fe7ac43657b3faa6ad3878a7ed78ab3528900eb1df8fbbb00e20805
- LOCK HASH
- ff1d5f1daa4736237aab6c37b7642ae8e623d65b8cb2eb9916c6ba33384efb81
Companion skills
No required companion skills are declared.
Share this skill.
Pass the canonical page to a teammate or keep it close for later.
json-render-devtools
Drop-in inspector panel for any json-render app. Use when the user wants to debug a generative UI, inspect the spec tree, edit state at runtime, see dispatched actions, follow stream patches live, browse a catalog, or pick DOM elements to find their spec keys. Triggers include "add devtools", "debug json-render", "inspect the spec", "why is this element not rendering", "see the state at runtime", or requests to tap streams / capture action logs for `@json-render/devtools`.
