customize

Redirect legacy skill calls to the canonical .codex/skills/customize/SKILL.md file.

3|1|Updated Feb 10, 2026

Search Tags:#codex #backward-compatibility #wrapper #customize #legacy-support #canonical-skill #skill-pipeline

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The wrapper provides backward compatibility by delegating all calls for the legacy customize skill to the canonical implementation located at .codex/skills/customize/SKILL.md. This ensures existing automations and workflows continue functioning without modification when upgrading to the canonical skill.

Core Features & Use Cases

Backward-compatibility routing: transparently forwards requests from the legacy path to the canonical skill.
Lightweight wrapper: minimal maintenance with no behavioral changes to the canonical logic.
Use Case: An existing automation references .claude/skills/customize; it now works by invoking the canonical skill at .codex/skills/customize/SKILL.md.

Quick Start

Invoke the wrapper to run the canonical customize skill.

Frequently Asked Questions about customize

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

FAQPage Schema

How do I maintain legacy skill paths when upgrading to canonical skills?▼

Legacy skill paths are maintained during an upgrade by using a backward-compatibility wrapper that transparently forwards calls to the canonical skill, ensuring existing automations continue functioning without modification.

What does backward compatibility routing for legacy skills actually do?▼

Backward compatibility routing redirects execution requests from a legacy file path to a canonical skill implementation, preserving the original input and output behavior without duplicating the core logic.

Do I need to update my automation to use the new canonical skill path?▼

No, you do not need to update existing automations if you use a lightweight wrapper. It intercepts the old path and delegates execution directly to the canonical skill file.

Can I use the legacy .claude skills path with the .codex canonical skill pipeline?▼

Yes, the legacy .claude skills path works with the .codex canonical skill pipeline by applying a wrapper that forwards requests to the canonical implementation located at .codex/skills/.

Are there limitations to using a wrapper for legacy skill support?▼

The primary limitation is that the wrapper itself contains no functional logic and relies entirely on the canonical skill file being present and correctly configured at the target path to execute successfully.