Create user components

User-owned components have one canonical source. Edit that source, then run sync to regenerate the Claude Code, Codex, and Cursor copies.

Scope	Canonical source
Repository	`.agents-pack/user/`
Global	`~/.agents-pack/user/`

Names you create cannot use the reserved ap- prefix. That prefix is reserved for official components.

Do not edit generated provider copies. Those edits are drift and block synchronization. See Ownership.

Create a skill (CLI)

agents-pack create skill deploy-app \
  --description "Deploy this application safely. Use for staging or production deployment." \
  --dry-run

agents-pack create skill deploy-app \
  --description "Deploy this application safely. Use for staging or production deployment." \
  --yes

Agents Pack creates a small valid SKILL.md scaffold, adds it to the user catalog, renders it for every selected agent, and records the generated files.

Edit the canonical file:

.agents-pack/user/skills/deploy-app/SKILL.md

Then synchronize:

agents-pack sync --dry-run
agents-pack sync --yes
agents-pack status

sync requires at least one canonical user-owned component.

Interactive create can prompt for a missing description. Non-interactive use requires --description.

Create a skill from chat

Every installation includes the required ap-create-new-skill skill. Ask in natural language:

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.

Or name the skill explicitly:

Use ap-create-new-skill to create a portable skill for reviewing database
migrations before deployment.

The agent should clarify important missing details, create the skill through Agents Pack, edit the canonical source, synchronize the provider copies, and verify the result. That is the recommended approach when you want help designing the skill, not only scaffolding files.

Create a read-only subagent

New subagents are read-only by default:

agents-pack create subagent release-checker \
  --description "Review release correctness and operational risk. Use before deployment." \
  --yes

Create a subagent that can edit the workspace

Add --write only when the role genuinely needs to change files:

agents-pack create subagent api-implementer \
  --description "Implement approved API changes. Use after an API plan is accepted." \
  --write \
  --yes

--write is valid only for subagents. The canonical subagent source contains provider-neutral agent.toml and instructions.md. Agents Pack renders each provider’s native definition.

Create user components

Create user components

Create a skill (CLI)

Create a skill from chat

Create a read-only subagent

Create a subagent that can edit the workspace

Related