Skrptiq SKRPTIQ

Assets

Colour: Pink (#ec4899)

Assets are structured content — configuration files, JSON schemas, SVG graphics, code snippets, YAML specs, and other machine-readable or formatted content.

When to use assets

Use an asset node when you have structured or formatted content that other nodes need to reference or consume. Assets bridge the gap between human-readable documentation and machine-readable configuration.

Good candidates for asset nodes:

  • Output schemas — JSON schemas that define the expected structure of LLM responses
  • SVG graphics — icons, diagrams, or visual elements used in workflows
  • JSON configurations — model parameters, feature flags, routing rules
  • YAML specifications — OpenAPI specs, pipeline configs, deployment manifests
  • Code templates — reusable code snippets, boilerplate, function signatures
  • Prompt fragments — reusable prompt components stored as structured text

Format auto-detection

The editor automatically detects the content format and applies appropriate handling:

  • SVG — detected by <svg or <?xml opening tags; renders an inline preview in the editor
  • JSON — detected by attempting to parse the content; applies syntax highlighting
  • YAML — detected by openapi: or swagger: headers, or colon-newline patterns; applies syntax highlighting
  • Code — other structured content gets code-style editing with a monospace font

You don’t need to configure the format manually. The editor handles detection on the fly based on the content.

How assets connect

Assets typically sit downstream of the nodes that use them:

  • Prompts → Assets — a prompt references a JSON schema to enforce output structure (connection type: “references”)
  • Workflows → Assets — a workflow requires a configuration file (connection type: “requires”)
  • Skills → Assets — a skill uses a code template as part of its implementation (connection type: “references”)

Text-only content

Asset content is stored as text. Binary formats and base64-encoded content are not supported. Stick to text-based formats: JSON, YAML, SVG, XML, code, markdown, CSV, and similar.