Template Variables Reference

Reference Handlebars templating syntax for Overcut workflow data integration.

9|2|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/overcut-ai/overcut-playbooks --skill template-variables-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Template Variables Reference
Source: https://github.com/overcut-ai/overcut-playbooks/tree/main/.agents/skills/template-variables
Command: npx skills add https://github.com/overcut-ai/overcut-playbooks --skill template-variables-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to understanding and utilizing Handlebars templating within Overcut workflows, enabling dynamic data passing and conditional logic.

Core Features & Use Cases

  • Output Referencing: Learn how to pass data between workflow steps using {{outputs.step-id}}.
  • Trigger Context: Access event-specific data like pull request details or issue information via {{trigger.*}}.
  • Handlebars Helpers: Utilize built-in helpers for comparisons, logical operations, and JSON serialization.
  • Use Case: When creating a workflow that needs to dynamically set the repository name based on the trigger event, you would use {{trigger.repository.fullName}} in the repoFullName parameter of a git.clone step.

Quick Start

Refer to the documentation for examples of how to use {{outputs.step-id.message}} to pass agent output to a subsequent step's prompt.

Frequently Asked Questions about Template Variables Reference

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

FAQPage Schema
How do I pass data between workflow steps using Handlebars?

To pass data between workflow steps using Handlebars, reference the output of a previous step with the `{{outputs.step-id}}` syntax. You can access specific properties like `{{outputs.step-id.message}}` to pass agent output to a subsequent step's prompt.

How do I access trigger context variables in Handlebars workflows?

Access trigger context variables in Handlebars workflows using the `{{trigger.*}}` syntax. This allows you to retrieve event-specific data, such as pull request details or issue information, to dynamically set parameters like `{{trigger.repository.fullName}}`.

What is Handlebars templating used for in workflow automation?

Handlebars templating in workflow automation is used for dynamic workflow construction and data integration. It enables dynamic data passing between steps and allows conditional logic through built-in helpers for comparisons, logical operations, and JSON serialization.

Can I use conditional logic and JSON serialization with built-in Handlebars helpers?

Yes, you can use conditional logic and JSON serialization with built-in Handlebars helpers. The templating reference covers utilizing built-in helpers for comparisons, logical operations, and JSON serialization to manipulate data within your workflows.

How do I dynamically set a repository name based on a trigger event?

To dynamically set a repository name based on a trigger event, use the `{{trigger.repository.fullName}}` variable in the `repoFullName` parameter of a `git.clone` step. This passes the event-specific data directly into the workflow action.