convert-to-docker

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This wrapper preserves backward compatibility by delegating execution to the canonical convert-to-docker skill located at .codex/skills/convert-to-docker/SKILL.md.

Core Features & Use Cases

  • Maintains legacy automation workflows by routing calls to the canonical skill, ensuring consistent behavior without rewriting existing logic.
  • Provides a single entry point for older CLAUDE-style skill directories to access the canonical implementation.
  • Use Case: You have an outdated wrapper in .claude/skills/convert-to-docker and you want it to execute the current canonical logic without changes to your workflow.

Quick Start

Activate this wrapper to transparently execute the canonical convert-to-docker skill at .codex/skills/convert-to-docker/SKILL.md.

Frequently Asked Questions about convert-to-docker

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

FAQPage Schema
How do I maintain backward compatibility for legacy CLAUDE-style skill directories?

To maintain backward compatibility for legacy CLAUDE-style directories, use a legacy wrapper that delegates execution to the canonical skill file, redirecting calls without rewriting existing automation workflows.

What is the best way to redirect a legacy wrapper to a canonical skill file?

Redirecting a legacy wrapper to a canonical skill file requires placing a wrapper SKILL.md in the legacy directory that references and delegates execution to the canonical implementation at the target path.

Do I need the canonical SKILL.md present to use a legacy wrapper?

Yes, the legacy wrapper requires the canonical SKILL.md file to be present at .codex/skills/convert-to-docker/SKILL.md, as the wrapper solely delegates execution and depends entirely on the canonical file's logic.

Can I execute the canonical convert-to-docker logic without changing my existing workflow?

You can execute the canonical logic without workflow changes by activating a wrapper at .claude/skills/convert-to-docker that transparently routes calls to the canonical implementation, preserving existing directory structures.

Why does my legacy skill wrapper need a single entry point for execution delegation?

A legacy skill wrapper needs a single entry point to ensure consistent behavior by routing all calls to the canonical implementation, preventing logic duplication and maintaining a unified execution path across environments.

When should I use a legacy wrapper instead of directly updating to the canonical skill?

Use a legacy wrapper when your environment maintains older CLAUDE-style skill directories and requires backward compatibility, allowing you to access canonical logic without rewriting established automation workflows.