MCUB-modules-creator

Create and update MCUB userbot modules with class-style structure and lifecycle hooks.

3|1|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/hairpin01/repo-MCUB-fork --skill mcub-modules-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCUB-modules-creator
Source: https://github.com/hairpin01/repo-MCUB-fork/tree/main/OpenAgent/skills/MCUB-modules-creator
Command: npx skills add https://github.com/hairpin01/repo-MCUB-fork --skill mcub-modules-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from creating and updating MCUB userbot modules by guiding you toward the correct runtime structure, API usage, and file layout.

Core Features & Use Cases

  • Module Creation: Build new debug modules that follow MCUB class-style conventions and command patterns.
  • Module Updates: Refactor or extend existing modules without breaking version history or overwriting earlier builds.
  • Docs-Driven Workflows: Use the local API, inline, and lifecycle documentation to implement commands, callbacks, and forms correctly.
  • Use Case: A developer wants to add a new userbot command with inline buttons and needs a safe, debugger-friendly implementation path.

Quick Start

Ask for a new MCUB debug module that follows the local API docs and save it under app-debug with the next version number.

Frequently Asked Questions about MCUB-modules-creator

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

FAQPage Schema
How do I create MCUB userbot modules with inline forms and callbacks?

To create MCUB userbot modules, use class-style conventions and follow local API documentation to implement inline forms, callbacks, and command handlers with debugger-safe patterns. This ensures correct runtime structure and proper file layout under app-debug.

What is the correct way to update an existing userbot module without breaking version history?

Updating an existing userbot module requires preserving versioned build files and maintaining import hygiene while refactoring. You extend the module using MCUB-only APIs and lifecycle hooks without overwriting earlier builds or disrupting the runtime structure.

Does this approach support app-debug module development for Telegram userbots?

Yes, app-debug module development is supported for Telegram userbots. It applies class-style modules, command handlers, and lifecycle hooks within the MCUB runtime, ensuring debugger-safe implementation patterns and correct API usage.

What's the best way to structure userbot command handlers using MCUB APIs?

The best way to structure userbot command handlers is by using MCUB-only APIs within class-style modules. Follow docs-driven workflows to implement lifecycle hooks and inline forms correctly, ensuring import hygiene and versioned build files.

Why does my MCUB module fail when using non-standard APIs or breaking import hygiene?

MCUB modules fail when using non-standard APIs because the runtime requires strict import hygiene and MCUB-only APIs. Breaking these constraints disrupts the debugger-safe implementation patterns and lifecycle hooks that maintain runtime structure.

Do I need versioned build files to save new userbot modules under app-debug?

Yes, versioned build files are required to save new userbot modules under app-debug. This preserves version history and prevents overwriting earlier builds while maintaining the correct runtime structure and documentation links.