Configuration Automation - Ping CLI

Agent Skills

Agent Skills are structured reference files that give coding agents targeted knowledge of Ping CLI commands and capabilities. Installing an Agent Skill means your agent can reason about the CLI directly, understanding available commands, flags, and service connectors without having to discover them through --help output at runtime.

Agent Skills follow the Agent Skills open format and are distributed from the remote Ping CLI repository.

What Agent Skills provide

An installed Ping CLI Agent Skill enables your coding agent to:

  • Know the full set of available commands, subcommands, and their purpose.

  • Understand flags, their types, and default values.

  • Use the correct output format options (text, json, ndjson).

  • Understand how service connectors are structured and how to authenticate to them.

  • Know when certain commands require an active profile or authenticated session.

  • Construct valid pingcli invocations without trial and error.

Discovering available Agent Skills

To see all Agent Skills available from the remote Ping CLI repository:

pingcli agent-skills list

The output includes the name and description of each available skill.

Installing an Agent Skill

Install an Agent Skill to the default location (.claude/skills/ in your current working directory):

pingcli agent-skills install pingcli-usage

To install to a custom directory:

pingcli agent-skills install pingcli-usage --output-dir /path/to/skills

The output directory is created automatically if it does not exist. The skill is placed at <output-dir>/<skill-name>.

After installing an Agent Skill, your coding agent will reference it automatically when you ask about or use Ping CLI commands in that project. The skill file does not need to be referenced manually.

Using Ping CLI without Agent Skills

Installing an Agent Skill is optional. Coding agents can still use Ping CLI by running pingcli --help or any subcommand with --help to discover available options at runtime. Agent Skills reduce that friction by making CLI knowledge available upfront.