messages

Add a message type to the safe-output messages system across JSON, Go, and JavaScript.

Updated Aug 27, 2026

Search Tags:#testing #templates #javascript #go #messages #json-schema #safe-output

Ready to run

npx skills add https://github.com/maxfraieho/garden-seedling --skill messages-maxfraieho

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: messages
Source: https://github.com/maxfraieho/garden-seedling/tree/main/gh-aw/skills/messages
Command: npx skills add https://github.com/maxfraieho/garden-seedling --skill messages-maxfraieho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide explains how to add a new message type to the GitHub Agentic Workflows safe-output messages system, enabling customizable messages across workflows.

Core Features & Use Cases

Step-wise extension of the safe-output messages to support new templates and contexts.
Reusable across all consumer scripts and safe-output operations.
Example: add a new notification type for a specific workflow condition.

Quick Start

Add a new message type by updating the JSON schema, implementing the type in Go and JavaScript, and validating with tests.

Frequently Asked Questions about messages

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

FAQPage Schema

How do I add a new message type to safe-output messages?▼

To add a new safe-output message type, update the JSON schema, implement the corresponding Go struct and JavaScript components, then validate the integration via tests to ensure correct exposure across builds.

What is the safe-output messages system used for in agentic workflows?▼

The safe-output messages system enables customizable, reusable message templates across workflows, allowing you to define specific notification types for distinct workflow conditions and consumer scripts.

Do I need to update both Go and JavaScript components when extending safe-output messages?▼

Yes, extending safe-output messages requires updating both the Go SafeOutputMessages struct and the JavaScript messages core, alongside modifying the JSON schema to validate the new template correctly.

How does JSON schema validation work with safe-output message templates?▼

JSON schema validation enforces the structure of safe-output message templates, ensuring that newly added message types integrate correctly with the Go and JavaScript components before build exposure.

Can I reuse a custom safe-output message template across multiple consumer scripts?▼

Yes, once you add a new message type by updating the schema and implementing the Go and JavaScript components, the template becomes reusable across all consumer scripts and safe-output operations.

What tests are required to validate a new safe-output message type integration?▼

Validation requires running integration tests that confirm the updated JSON schema, Go SafeOutputMessages struct, and JavaScript core correctly expose and handle the new message module during builds.