/as:skill-maker — Author a governed skill

Use the active host's native skill maker when available. If none exists, write the minimum skill in that host's supported format. The host owns generic authoring technique; this skill supplies Arch Studio's target, governance and acceptance requirements. Do not require a particular host maker or install an Arch Studio runtime.

Read PATTERNS.md and follow its owning links as relevant: architecture, host contract, host adapters, workspace model, terminology, and contribution rules. Read this component's declaration (skill:skill-maker) and only its applicable modes from the shared catalog. For MCP delivery, retrieve all required resources at the advertised release digest; resource references are not assumed local paths.

Target

Derive ordinary authoring choices from the request; do not run a routine setup interview. Ask only for missing scope, target authorization or a concrete governance conflict.

Resolve the exact target before writing. Catalog detection has highest priority: find the Git root and check whether .codex-plugin/plugin.json or .claude-plugin/plugin.json names as. A plugin cache or MCP resource is not a writable source checkout. Otherwise find the nearest STUDIO.md for a normal firm skill; do not let a nearer project silently override a resolved studio. Use the nearest project root only when the user explicitly requests a project-only skill. If no root is established, ask one target question rather than treating the current directory as a studio. A global target requires an explicit request.