Background
The GitHub CLI ships an agent skill at skills/gh/SKILL.md. It's a markdown file (with YAML frontmatter) committed into the CLI's own repo that coding agents (Claude Code, etc.) auto-discover and load when a task involves gh. It doesn't change CLI behavior — it encodes the non-obvious operational knowledge an agent needs to drive the CLI reliably: non-interactive behavior, structured output, auth, pagination, and common workflows.
Proposal
Add the equivalent for the Apify CLI at skills/apify/SKILL.md, teaching agents the Apify-specific equivalents:
- Non-interactive use — bypassing the
create/init/login wizards; -y/--yes for confirmations.
- Auth —
APIFY_TOKEN env var for automation; apify info to verify; apify auth token.
- Structured output —
--json on list/info commands; --limit/--offset; apify datasets get-items --format json.
- Core workflows —
create → run → push; apify call / apify actors start; runs/builds wait, info, log.
- Escape hatch —
apify api with --list-endpoints / --describe.
The skill points to docs/reference.md and apify help <command> for exhaustive detail rather than duplicating it.
Why
Agents increasingly drive the Apify CLI. A shipped skill makes that usage reliable and consistent without each user re-discovering the gotchas.
Background
The GitHub CLI ships an agent skill at
skills/gh/SKILL.md. It's a markdown file (with YAML frontmatter) committed into the CLI's own repo that coding agents (Claude Code, etc.) auto-discover and load when a task involvesgh. It doesn't change CLI behavior — it encodes the non-obvious operational knowledge an agent needs to drive the CLI reliably: non-interactive behavior, structured output, auth, pagination, and common workflows.Proposal
Add the equivalent for the Apify CLI at
skills/apify/SKILL.md, teaching agents the Apify-specific equivalents:create/init/loginwizards;-y/--yesfor confirmations.APIFY_TOKENenv var for automation;apify infoto verify;apify auth token.--jsonon list/info commands;--limit/--offset;apify datasets get-items --format json.create → run → push;apify call/apify actors start;runs/builds wait,info,log.apify apiwith--list-endpoints/--describe.The skill points to
docs/reference.mdandapify help <command>for exhaustive detail rather than duplicating it.Why
Agents increasingly drive the Apify CLI. A shipped skill makes that usage reliable and consistent without each user re-discovering the gotchas.