setup

Redirect legacy setup requests to the canonical .codex/skills/setup/SKILL.md file.

3|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ShalomObongo/nanoclaw --skill setup-shalomobongo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/ShalomObongo/nanoclaw/tree/main/.claude/skills/setup
Command: npx skills add https://github.com/ShalomObongo/nanoclaw --skill setup-shalomobongo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy compatibility wrapper enables backward-compatible access by delegating execution to the canonical setup skill located at .codex/skills/setup/SKILL.md.

Core Features & Use Cases

  • Redirects legacy .claude/skills/setup references to the canonical .codex/skills/setup/SKILL.md.
  • Ensures consistent behavior by loading the canonical skill's frontmatter (name and description) and body during activation.
  • Facilitates maintenance by serving as a bridge to the official implementation while supporting older paths.

Quick Start

Read and execute the canonical file located at .codex/skills/setup/SKILL.md.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I redirect legacy .claude/skills requests to a canonical skill path?

To redirect legacy .claude/skills requests, use a compatibility wrapper that delegates execution to the canonical setup skill located at .codex/skills/setup/SKILL.md, ensuring consistent behavior across both paths.

What is a legacy compatibility wrapper for skill execution?

A legacy compatibility wrapper is a bridge mechanism that intercepts requests from older skill paths and redirects them to the canonical implementation, loading the official file's YAML frontmatter and body during activation.

Do I need valid YAML frontmatter to use the canonical setup skill?

Yes, the canonical SKILL.md file requires valid YAML frontmatter containing both a name and description; the wrapper loads this metadata during activation to ensure consistent execution.

Why does my legacy setup skill path not work with the new canonical directory?

Legacy setup paths fail because execution has moved to the .codex/skills/setup/SKILL.md directory; a wrapper is required to redirect older .claude/skills references to the new canonical location.

Can I maintain older skill paths while using the canonical setup implementation?

Yes, the wrapper facilitates maintenance by serving as a bridge to the official implementation, allowing older .claude/skills paths to function while execution occurs at the canonical .codex/skills location.

What are the limitations of using a legacy wrapper for canonical skill redirection?

The wrapper only redirects execution and loads the canonical file; it does not provide independent functionality and requires the canonical SKILL.md file to exist with valid YAML frontmatter for activation.