writing-handlebars

Write Celigo Handlebars expressions with correct brace style and runtime context variables.

3|2|Updated May 20, 2026
One-click install
npx skills add https://github.com/celigo/ai --skill writing-handlebars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-handlebars
Source: https://github.com/celigo/ai/tree/main/skills/writing-handlebars
Command: npx skills add https://github.com/celigo/ai --skill writing-handlebars

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of writing correct Handlebars template expressions for Celigo integrations so your mappings, HTTP requests, SQL queries, and filters render the exact dynamic values you intend.

Core Features & Use Cases

  • Correct syntax and escaping: Choose the right brace style (double vs triple) and place literal quotes safely.
  • Accurate runtime context: Write expressions using the right available variables (record, @root, settings, connection) and understand differences between import, lookup, and export bubbles.
  • Reliable expression patterns: Apply common recipes like conditional fields, nested iteration, and date formatting/arithmetic for computed integration configuration.

Quick Start

Tell the AI: write a Celigo Handlebars expression that builds a JSON HTTP request body using record. fields, triple braces for raw output, and conditional logic when an optional value is missing.

Frequently Asked Questions about writing-handlebars

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Handlebars expressions for Celigo integration mappings?

To write Handlebars expressions for Celigo mappings, select the correct brace style and reference the appropriate runtime context variables like `record.` or `@root` according to AFE 2.0 scoping rules. This ensures your dynamic integration configurations render exactly as intended.

What is the difference between double and triple braces in Handlebars templating?

Double braces in Handlebars templating escape HTML characters for safe display, while triple braces output raw unescaped values. Using triple braces is necessary when generating JSON HTTP request bodies or RDBMS SQL queries so the dynamic values integrate without unwanted character conversion.

How do I access runtime context variables in Celigo import and export stages?

Access runtime context variables in Celigo import and export stages by using available objects like `record`, `@root`, `settings`, and `connection`. Understanding the scope differences between import, lookup, and export bubbles ensures your Handlebars expressions target the correct data.

Can I use conditional logic and date formatting in Celigo Handlebars templates?

Yes, you can use conditional logic and date formatting in Celigo Handlebars templates to compute dynamic values. Applying common expression recipes like conditional fields for missing optional values and safe date arithmetic allows you to build deterministic HTTP URIs, bodies, and output filters.

How do I handle one-to-many grouping shapes in Handlebars mappings?

Handle one-to-many grouping shapes in Handlebars mappings by utilizing structures like `batch_of_records` within your template expressions. This approach supports nested iteration and correct data grouping across import, lookup, and export stages following Celigo AFE 2.0 scoping rules.