Pilio Skills: install developer API skills by feature; leave execution to the CLI

Who it's for

Use this skill set when you want to hand Pilio developer API workflows to an agent, and you accept that “each skill is deliberately small; the thing that actually calls the API is the CLI”. It is not a generic image plugin marketplace; it only covers the few --skill names written in the notes.

Three preconditions. First, install one feature at a time: gpt-image-2, nano-banana-pro, or remove-background. Do not invent a fourth name. Second, set PILIO_API_KEY in the local environment before running the CLI; do not paste a real key into a prompt or a skill file. Third, first try the same workflow with hosted Pilio tools in a browser, then hand it to the agent. Visible text gives no URL for the hosted tools; go back to the official repository to find the entry, and do not invent a domain.

Without an API key, and with no plan to verify in the browser first, do not let the agent run the CLI.

First try in 3 minutes

Official page:

https://github.com/pilioai/skills

First only install; do not call the API. Pick one official skill, for example (writes skill files on this machine; confirm the name first):

pnpm dlx skills add pilioai/skills --skill remove-background

The other two official names are gpt-image-2 and nano-banana-pro. After install, check that that skill appears. If the command fails, stop.

Success signal: the matching skill is installed, and you have not yet run any @pilio/cli. If you later really call the API, first finish the same workflow in the hosted browser tools, then export PILIO_API_KEY locally, and only then let the agent run:

pnpm dlx @pilio/cli <command>

The body of <command> lists no concrete subcommands. First have the agent state the full command it will run; after you confirm it will not bill at random or write to the wrong directory, execute, and immediately look at the output file or the error.

Use cases

Case 1: Install one skill by feature. Use pnpm dlx skills add pilioai/skills --skill plus one of the three official names. Check that only the one you chose appears. Do not install everything at once with an --all that never appeared.

Case 2: Leave execution to @pilio/cli. The skill itself does not call the API. First verify in the browser, then set PILIO_API_KEY, then run pnpm dlx @pilio/cli <command>. If the subcommand is not written, do not invent it. Any secret stays in the local environment, not in a prompt, not in a skill file.

Boundaries

Install is evidenced only as pnpm dlx skills add for gpt-image-2, nano-banana-pro, remove-background.

API execution is evidenced only as pnpm dlx @pilio/cli <command>. There is no subcommand table.

PILIO_API_KEY must live in the local environment; do not write a real key into a prompt or skill file.

Hosted browser tools are required as verification before the agent, but no URL appears. Do not invent a domain.

The notes give no language coverage, pricing, or named clients. Keep undocumented items unknown; do not invent subcommands or a fourth skill name.