json-render-templates_skill

This skill helps you generate UI templates like flowcharts, forms, dashboards, and galleries as ready-to-emit JSON payloads for rapid visualization.
  • Go

8

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill cklxx/elephant.ai --skill json-render-templates

  • SKILL.md3.5 KB

Overview

This skill provides a set of JSON-render protocol templates for common visual layouts: flowchart, form, dashboard, info cards, gallery, table, kanban, and diagram. It lets you produce UI-ready JSON payloads that can be emitted to a renderer or UI pipeline to produce consistent visual outputs. Use it to convert structured answers into visual components instead of long prose.

How this skill works

Choose the template that best matches the layout you need and replace the sample values with your data. Serialize the resulting payload to JSON and emit it with the platform's emit function (for example, via a2ui_emit using the content string). The templates are intentionally minimal so they can be extended or combined in your runtime before rendering.

When to use it

  • When the user requests a visual representation (flowchart, diagram, gallery, or cards).
  • When a multi-entity summary benefits from layout instead of paragraph text.
  • When you need to return a form skeleton for onboarding or data capture.
  • When you want to present metrics and items in a dashboard view.
  • When you need a quick UI mock or proof-of-concept payload for the frontend.

Best practices

  • Pick the closest template and only change the data values; keep structural keys intact.
  • Keep labels and ids concise to avoid rendering truncation in compact UIs.
  • Use consistent id and label naming for nodes and edges to make maps and diagrams readable.
  • Prefer numeric types for metric values and strings for captions to preserve formatting.
  • Emit the payload as a single JSON string via the platform emit function so viewers receive a complete message.

Example use cases

  • Build a release flowchart: map design → build → deploy nodes and edges for deployment docs.
  • Return an onboarding form payload when requesting new-user data collection fields.
  • Produce a product dashboard payload with active users, conversion, and revenue metrics.
  • Send info cards to summarize health checks like latency and error rate for a monitoring UI.
  • Generate a gallery payload to preview visual design mockups or marketing assets.

FAQ

Yes — you can include multiple message blocks (e.g., heading plus flow) in a single payload as long as the renderer supports message bundles.

What format should metric values use?

Use numeric types for raw metrics and formatted strings (with % or $) for display-ready values so frontends can apply correct formatting if needed.

How do I emit the JSON to the UI?

Serialize the payload to a JSON string and send it using the platform emit method (for example, a2ui_emit with content set to the JSON string).

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational