add-voice-transcription

Route legacy add-voice-transcription requests to the canonical skill.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy compatibility wrapper that preserves the old add-voice-transcription workflow by routing calls to the canonical skill located at .codex/skills/add-voice-transcription/SKILL.md.

Core Features & Use Cases

  • Backward compatibility: forwards requests from the legacy path to the canonical implementation without requiring changes to downstream tooling.
  • Lightweight routing: minimal overhead, keeps existing interfaces and inputs intact.
  • Safe delegation: validates inputs and surfaces errors clearly while delegating actual processing to the canonical skill.

Quick Start

Use the legacy wrapper to invoke the canonical voice transcription workflow.

Frequently Asked Questions about add-voice-transcription

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

FAQPage Schema
How do I route legacy voice transcription requests to a canonical skill?

Legacy voice transcription requests are routed to the canonical skill by forwarding inputs to the new SKILL.md path, preserving backward compatibility without altering downstream tooling.

What is a legacy wrapper for workflow routing and when do I need it?

A legacy wrapper is a compatibility layer that delegates processing to a canonical skill implementation. You need it when existing automation relies on old wrapper paths but must use the updated voice transcription workflow.

Can I use the legacy voice transcription wrapper without changing my existing automation inputs?

Yes, the wrapper keeps existing interfaces and inputs intact. It performs lightweight routing with minimal overhead, validating inputs before delegating processing to the canonical voice transcription skill.

Does the voice transcription wrapper handle input validation and error reporting?

The wrapper provides safe delegation by validating inputs and surfacing errors clearly. It forwards valid data to the canonical skill and returns its output, ensuring robust error handling across legacy environments.

When should I not use a legacy wrapper for voice transcription?

You should avoid the legacy wrapper if your downstream tooling can be updated directly. The wrapper exists solely to preserve compatibility for environments that still depend on the old add-voice-transcription path.