CLI Usage Check And Version Confirmation

Prerequisite: read ../apidog-cli/SKILL.md first. If the stable entry skill conflicts with this skill, use current apidog <command> --help and this skill as the source of truth. Then read the corresponding domain skill based on the resource type.

This skill is for public CLI troubleshooting and does not rely on internal APIs or internal code. The goal is to confirm command, project, branch, environment, resource ID, report location, and CLI version, then return to the domain skill to fix resource structure. Agents should close the loop with current help, schema validation, get readback, and agentHints; do not trust summary text alone.

When To Use

• CLI returns success, but the Apidog client does not show the resource or displays it incompletely.
• A resource cannot be found by list/get after creation.
• Test cases, test scenarios, or test suites fail to run.
• Local or cloud reports are missing or have no step details.
• agentHints, help, examples, or actual command behavior conflict.
• A user or tester says a parameter is missing or a command is unknown, and the CLI version needs confirmation.

First Five Checks