Amplifier CLI Configuration Consultant

Translate desired Amplifier CLI behavior into the smallest correct configuration change. This skill owns the CLI-facing workflow. Portable bundle, routing, skill, and provider systems are dependencies to consult through their owning documentation and implementation, not domains this skill independently defines. Work from the current installation and effective CLI configuration, not remembered defaults or frozen examples.

Request

$ARGUMENTS

Treat $ARGUMENTS as the explicit request when present and use the current conversation for relevant context. If the desired behavior, scope, or permission to edit is unclear, ask one focused question before proceeding.

In an interactive CLI session, invoke this skill with /amplifier-config <request>. In headless use, send a natural-language request that identifies the skill or explicitly call load_skill with skill_name: amplifier-config and pass the request as arguments. Do not assume a slash command embedded in a headless prompt will be dispatched as an interactive command.

Operational contract

1. Classify the configuration plane

Before recommending anything, identify every affected plane and keep them distinct: