messages

Add custom message types across JSON schema, Go parser, and JavaScript modules.

4.9k|489|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/github/gh-aw --skill messages-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: messages
Source: https://github.com/github/gh-aw/tree/main/skills/messages
Command: npx skills add https://github.com/github/gh-aw --skill messages-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The messages system for safe-output is incomplete without user-defined message types. This Skill provides a guided process to add new message templates that can be configured, generated, and integrated into the safe-output pipeline.

Core Features & Use Cases

  • Ability to add a new message type to the frontmatter and JSON Schema.
  • Auto-generate corresponding JavaScript modules, tests, and core typedefs.
  • End-to-end integration from schema to consumer scripts.

Quick Start

This section outlines the initial steps to begin adding a new message type by following the process defined in this Skill, including updating the JSON Schema, Go parser, JavaScript modules, tests, barrel exports, embeddings, and documentation.

Frequently Asked Questions about messages

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

FAQPage Schema
How do I add a custom message type to safe-output JSON schema definitions?

To add a custom message type to safe-output JSON schema definitions, you must update the schema, Go parser, JavaScript modules, tests, and documentation to ensure end-to-end integration. This coordinates updates across multiple components to expose a new message template.

What is the process for extending safe-output messages with new message types?

Extending safe-output messages with new message types involves updating the JSON schema, Go parser, JavaScript modules, and barrel exports. This guided process configures and generates new message templates integrated into the safe-output pipeline.

Do I need to update Go structs and JavaScript modules to support custom safe-output message types?

Yes, supporting custom safe-output message types requires updating Go structs and JavaScript modules. The process applies changes across schema, Go parsers, JavaScript modules, tests, and embeddings to expose a new message template.

How do safe-output custom messages integrate with JavaScript modules and barrel exports?

Safe-output custom messages integrate with JavaScript modules and barrel exports by auto-generating corresponding modules and core typedefs. This ensures end-to-end integration from schema to consumer scripts within the safe-output pipeline.

Can I auto-generate tests and typedefs when adding new message types to safe-output?

Yes, you can auto-generate corresponding JavaScript modules, tests, and core typedefs when adding new message types to safe-output. This automation ensures the new message template is fully integrated and configured.

What components need coordinated updates to expose a new safe-output message template?

Exposing a new safe-output message template requires coordinated updates across JSON schema, Go parser, JavaScript modules, tests, barrel exports, and embeddings. This ensures end-to-end integration from schema to consumer scripts.