create-gsd-extension

Build and iterate on GSD extensions adding tools, commands, events, and UI to Tamux.

321|26|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/mkurman/tamux --skill create-gsd-extension-mkurman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-gsd-extension
Source: https://github.com/mkurman/tamux/tree/main/skills/gsd-2/skills/create-gsd-extension
Command: npx skills add https://github.com/mkurman/tamux --skill create-gsd-extension-mkurman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured approach to building, debugging, and iterating on GSD extensions that introduce tools, commands, events, UI, and providers to Tamux.

Core Features & Use Cases

  • Scaffold a complete extension skeleton (tools, commands, events, UI)
  • Debug and iterate on extension behavior and integration with the GSD runtime
  • Extend Tamux capabilities by registering new tools, slash commands, and event hooks for customized workflows

Quick Start

Create a new extension by following the skeleton, then register at least one tool, one command, and one event hook, and finally run /reload to test.

Frequently Asked Questions about create-gsd-extension

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

FAQPage Schema
How do I scaffold a Tamux extension with custom tools and commands?

Scaffolding a GSD extension involves generating a complete skeleton that includes tools, commands, events, and UI components, then registering at least one of each before running /reload to test the integration within the Tamux platform.

How do I debug and iterate on GSD extension behavior?

Debugging and iterating on GSD extensions involves analyzing integration points across tools, commands, events, and UI, then using the /reload command to apply changes and validate structured tool registration, event hooks, and state management within the runtime.

What is the best way to register tools and event hooks in Tamux?

Registering tools and event hooks in Tamux requires defining structured tool registrations and event hook definitions within your extension skeleton, ensuring proper rendering, state management, and per-turn prompts are configured before running /reload.

Do I need TypeScript to build GSD extensions for Tamux?

Building GSD extensions for Tamux uses TypeScript to define tools, commands, events, and UI components, providing structured type safety for tool registration, command definitions, event hooks, and state management within the extension development workflow.

Can I add slash commands and UI rendering to an existing GSD extension?

You can extend an existing GSD extension by registering new slash commands, event hooks, and UI rendering capabilities, iterating on integration points to add customized workflows, state management, and per-turn prompts to the Tamux platform.