add-gmail

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

3|1|Updated Feb 10, 2026

Search Tags:#codex #delegation #gmail #backward-compatibility #legacy #wrapper

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This wrapper preserves backward compatibility by routing calls to the canonical add-gmail skill file located at .codex/skills/add-gmail/SKILL.md.

Core Features & Use Cases

Backward compatibility: keeps existing workflows functional when referencing the legacy wrapper.
Delegation: transparently delegates execution to the canonical skill without changing behavior.
Maintenance: minimizes drift by centralizing logic in the canonical skill.

Quick Start

Invoke the add-gmail wrapper to execute the canonical skill file located at .codex/skills/add-gmail/SKILL.md.

Frequently Asked Questions about add-gmail

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

FAQPage Schema

How do I maintain backward compatibility when migrating legacy skill wrappers to a canonical path?▼

To maintain backward compatibility, use a legacy wrapper that delegates execution to the canonical skill file. This routes calls from older paths to the new central implementation without breaking existing workflows.

What is the best way to route legacy .claude/skills references to a canonical .codex/skills implementation?▼

The best way to route legacy references is by invoking a wrapper that transparently delegates execution to the canonical skill file, preserving existing behavior while minimizing logic drift across environments.

Do I need to update existing workflows if I use a delegation wrapper for my legacy skills?▼

No, you do not need to update existing workflows. The delegation wrapper preserves backward compatibility by routing older references directly to the canonical implementation without introducing new actions.

Why does my legacy skill wrapper still function after moving the canonical file to a new directory?▼

Your legacy wrapper still functions because it acts as a bridge that delegates execution to the canonical skill file in its new directory, keeping older workflows operational without changing behavior.

Can I introduce new actions when delegating execution from a legacy wrapper to a canonical skill?▼

No, you cannot introduce new actions. The wrapper requires invoking the canonical file to preserve existing behavior strictly, ensuring backward compatibility without adding new functionality.

When should I use a legacy wrapper instead of directly calling the canonical skill file?▼

Use a legacy wrapper when older environments or workflows reference legacy paths and must route to the canonical implementation, ensuring continuity without requiring updates to existing references.