Skip to content

Manage via coding agent

After initialization, you do not need to memorize Agents Pack commands. Talk to Claude Code, Codex, or Cursor about the outcome you want.

The first agents-pack init is the exception: run it yourself because the management skill is installed by that command.

Every installation includes:

Skill Role
ap-manage-agents-pack Inspect health, list/install/remove components, create or sync user components, fork, update, pin, roll back, and verify
ap-create-new-skill Create one canonical user-owned skill and synchronize it for every selected provider

The management skill teaches the agent that the CLI is the source of truth. It must not work around lifecycle protections or edit generated provider copies directly.

Check my Agents Pack installation and explain whether everything is healthy.
Do not change anything.
Show me which frontend-related components are available and recommend which
ones fit this project.
Install the ap-frontend-design skill. Preview the change first and wait for my
approval before applying it.
Check whether a new Agents Pack content version is available. Summarize the
release notes, but do not update anything yet.
Fork ap-debug into a user-owned skill named my-debug, then show me which
canonical file I should customize.
Create a read-only subagent named release-checker that reviews release
correctness and deployment risk. Make it available to all coding agents
configured in this repository.
Create a reusable Agents Pack skill named deploy-app. It should guide an agent
through safely deploying this project to staging or production, including
preflight checks and post-deployment verification.
Synchronize my user-owned Agents Pack components, then verify that every
managed file is clean.

If the agent does not select the skill automatically

Section titled “If the agent does not select the skill automatically”

Name it explicitly:

Use ap-manage-agents-pack to check for available updates and explain what
would change. Do not apply the update.
Use ap-create-new-skill to create a portable skill for reviewing database
migrations before deployment.

These are skills, not special chat commands. How your coding agent shows or invokes skills may differ, but the natural-language request can stay the same across Claude Code, Codex, and Cursor.

Running the CLI yourself is useful when you want exact control, are writing automation, your coding agent is unavailable, or you are diagnosing a lifecycle or ownership problem. The management skills use the same public CLI documented in the other guides.