x-integration

Route legacy x-integration wrappers to canonical TypeScript implementations.

3|1|Updated Feb 10, 2026

Search Tags:#typescript #compatibility #delegation #legacy #wrapper #x-integration

Ready to run

npx skills add https://github.com/ShalomObongo/nanoclaw --skill x-integration-shalomobongo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: x-integration
Source: https://github.com/ShalomObongo/nanoclaw/tree/main/.claude/skills/x-integration
Command: npx skills add https://github.com/ShalomObongo/nanoclaw --skill x-integration-shalomobongo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Bridges legacy x-integration calls to the canonical implementation, preserving backward compatibility for existing integrations.

Core Features & Use Cases

Backward-compatible delegation: routes legacy wrappers to the canonical TS implementations.
Minimal maintenance: centralizes logic in the canonical path while preserving old entry points.
Safe deprecation path: allows gradual migration to the canonical skill.

Quick Start

Invoke the legacy wrapper to route calls to the canonical x-integration implementation.

Frequently Asked Questions about x-integration

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

FAQPage Schema

How do I maintain backward compatibility when migrating legacy TypeScript wrappers?▼

To maintain backward compatibility, route legacy wrapper calls to the canonical TypeScript implementation, preserving old entry points while centralizing logic in the canonical path.

What is a safe deprecation path for legacy integration calls?▼

A safe deprecation path for legacy integration calls uses wrapper delegation to route existing references to canonical logic, allowing gradual migration without breaking current deployments.

How do I route existing deployment references to canonical TypeScript files?▼

You can route existing deployment references to canonical TypeScript files by invoking a legacy wrapper that re-exports to the canonical implementation located under .codex/skills.

Do I need to update my integration scripts if they reference the legacy path?▼

You do not need to update integration scripts referencing the legacy path, because the wrapper delegates calls to the canonical TypeScript implementation, preserving existing behavior automatically.

Why does my legacy integration wrapper fail to find the canonical logic?▼

Legacy integration wrappers fail when the canonical TypeScript files under .codex/skills are missing or misplaced, preventing the wrapper from successfully re-exporting to the canonical implementation.