sase_var

Store and retrieve structured JSON variables for SASE agent communication.

5|Updated Dec 6, 2021
One-click install
npx skills add https://github.com/bbugyi200/dotfiles --skill sase-var
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sase_var
Source: https://github.com/bbugyi200/dotfiles/tree/main/home/dot_codex/skills/sase_var
Command: npx skills add https://github.com/bbugyi200/dotfiles --skill sase-var

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of passing small, structured data between independent SASE agents, ensuring that downstream processes can reliably consume outputs from upstream tasks.

Core Features & Use Cases

  • Structured Data Handoff: Set and retrieve JSON-formatted variables (strings, numbers, lists, maps) across different agent runs.
  • Workflow Control: Use the reserved STOP variable to conditionally terminate repeat chains, saving compute resources.
  • Use Case: An upstream agent performs a build and sets a result_path variable, which a downstream agent then reads to locate and process the generated artifact.

Quick Start

Use the sase_var skill to set a summary variable with the value tests passed for the current agent run.

Frequently Asked Questions about sase_var

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

FAQPage Schema
How do I pass JSON variables between agents in a SASE workflow?

To pass JSON variables between agents in a SASE workflow, you can set and retrieve structured data types like strings, numbers, lists, and maps within the SASE execution environment. This ensures downstream agents reliably consume upstream outputs.

How do I conditionally terminate a multi-stage agent chain?

To conditionally terminate a multi-stage agent chain, you use the reserved STOP variable to signal workflow termination. This mechanism saves compute resources by preventing unnecessary repeat chain executions.

Do I need a specific environment to manage agent output variables for SASE workflows?

Yes, managing agent output variables for SASE workflows requires a valid SASE_AGENT environment to be present. This environment provides the necessary execution context for storing and retrieving the structured JSON data.

Can I use Jinja templating to consume downstream variables in SASE workflows?

Yes, you can use Jinja templating to consume downstream variables in SASE workflows. The system provides direct integration with Jinja, allowing downstream processes to dynamically render and utilize the structured JSON outputs.

What is the best way to share build artifacts between independent agents?

The best way to share build artifacts between independent agents is setting a structured JSON variable, such as a result_path. Downstream agents then retrieve this variable to locate and process the generated artifact.