skills.rest
ShalomObongo
ShalomObongoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

add-telegram

Delegate execution to the canonical Telegram skill for legacy workflows.

3|1|Updated Feb 10, 2026
Search Tags:#integration#migration#backward-compatibility#telegram#wrapper#canonical-skill
One-click install
npx skills add https://github.com/ShalomObongo/nanoclaw --skill add-telegram-shalomobongo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-telegram
Source: https://github.com/ShalomObongo/nanoclaw/tree/main/.claude/skills/add-telegram
Command: npx skills add https://github.com/ShalomObongo/nanoclaw --skill add-telegram-shalomobongo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy compatibility wrapper that delegates execution to the canonical Telegram skill located at .codex/skills/add-telegram/SKILL.md to preserve existing workflows.

Core Features & Use Cases

  • Backwards-compatible wrapper that forwards all calls to the canonical skill without changing behavior.
  • Facilitates migration of legacy references to the new canonical path in .codex/skills.
  • Provides a stable interface for tools and pipelines that expect add-telegram to exist at the old location.

Quick Start

Call the wrapper to execute the canonical Telegram skill at .codex/skills/add-telegram/SKILL.md.

Frequently Asked Questions about add-telegram

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

FAQPage Schema
How do I maintain Telegram workflow backward-compatibility after migrating to a canonical skill?▼

To maintain backward-compatibility, use a wrapper that delegates execution to the canonical Telegram skill. This preserves existing workflows by forwarding calls without changing behavior, ensuring legacy references continue to function during migration.

What is a legacy wrapper for canonical skills and when do I need one?▼

A legacy wrapper for canonical skills is a compatibility layer that forwards calls to a newly centralized skill file. You need one when migrating legacy workflows to a canonical path to prevent breaking existing tools and pipelines that expect the old location.

Does the Telegram integration wrapper require the canonical skill to be present?▼

Yes, the Telegram integration wrapper requires the canonical skill file at .codex/skills/add-telegram/SKILL.md to be present and accessible. The wrapper depends entirely on delegating execution to this canonical file to function.

How to execute Telegram tasks using a backward-compatible wrapper?▼

To execute Telegram tasks using a backward-compatible wrapper, call the wrapper function. It will automatically delegate execution to the canonical Telegram skill located at .codex/skills/add-telegram/SKILL.md without changing behavior.

What's the best way to migrate legacy Telegram references without breaking pipelines?▼

The best way to migrate legacy Telegram references without breaking pipelines is implementing a wrapper that delegates execution to the canonical skill. This provides a stable interface for tools expecting the old location while facilitating migration.

Related Skills

Explore More Software Engineering Skills→
ShalomObongoShalomObongo
3

add-telegram-swarm

Delegate legacy add-telegram-swarm calls to the canonical SKILL.md implementation.

Community
Basic
ShalomObongoShalomObongo
3

convert-to-docker

Delegate execution from legacy skill wrappers to the canonical convert-to-docker skill.

Community
Basic
ShalomObongoShalomObongo
3

add-parallel

A backward-compatibility layer that delegates Packfile reads and writes to lib-dmgr.

Community
Basic
ShalomObongoShalomObongo
3

add-gmail

Delegate legacy add-gmail wrapper calls to the canonical skill file.

Community
Basic