messages

Add customizable safe-output message types to GitHub Agentic Workflows.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill messages-kaushal-waygood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: messages
Source: https://github.com/kaushal-waygood/agentic-self-healing-ci/tree/main/skills/messages
Command: npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill messages-kaushal-waygood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The messages skill streamlines the multi-step process of introducing new safe-output message types into GitHub Agentic Workflows by ensuring frontmatter, schema, compiler, runtime modules, tests, and documentation stay in sync. It reduces errors and developer friction when exposing configurable templates that workflows render at runtime.

Core Features & Use Cases

  • Schema Integration: Guides adding YAML frontmatter fields and JSON Schema entries so messages validate in workflows.
  • Compiler and Runtime Wiring: Shows required Go struct and parser updates, JavaScript message module creation, embedding, and barrel exports for runtime use.
  • Testing and Documentation: Covers unit tests, typedef updates, bundler registration, and documentation updates to ensure reliable behavior.
  • Use Case: Add a custom "close-older-discussion" or "my-new-message" template that workflow authors can configure in frontmatter and render with placeholders during safe-output operations.

Quick Start

Add a new safe-output message named my-new-message by updating the JSON Schema, the Go struct and parser, creating the JavaScript message module and tests, embedding the module, and documenting its placeholders and usage.

Frequently Asked Questions about messages

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

FAQPage Schema
How do I add custom safe-output message types to GitHub Agentic Workflows?

To add safe-output message types, update the YAML frontmatter and JSON Schema, modify Go structs and parser logic, create JavaScript runtime modules with defaults, and document placeholders.

Why do my workflow safe-output messages fail JSON schema validation?

Safe-output messages fail schema validation when YAML frontmatter fields lack matching JSON Schema entries. Synchronize schema definitions with Go compiler structs and JavaScript modules to ensure valid configurable templates flow through.

What is the process for wiring new message templates through the Go compiler and JavaScript runtime?

Wiring message templates requires updating Go struct definitions and parser logic, creating JavaScript message modules, embedding sources for bundling, and exporting barrel files for runtime rendering.

Do I need to update tests and documentation when creating new safe-output message modules?

Yes, creating safe-output message modules requires unit tests, typedef updates, bundler registration, and documentation of placeholders and usage to ensure reliable runtime behavior and template rendering.

Can I configure custom placeholders in safe-output message templates for GitHub workflows?

Yes, custom safe-output message templates support configurable placeholders defined in YAML frontmatter. Document these placeholders alongside JavaScript module exports and JSON schema entries for workflow authors.

What limitations exist when adding safe-output messages across schema, Go, and JavaScript layers?

Adding safe-output messages requires synchronized updates across YAML schema, Go compiler structs, and JavaScript runtime modules. Failing to update any layer breaks template rendering and workflow validation.