apx-agency-agents

Manages a two-layer vault of reusable agent templates for listing, importing, and overriding.

6|1|Updated May 8, 2026
One-click install
npx skills add https://github.com/agentprojectcontext/apx --skill apx-agency-agents-agentprojectcontext
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apx-agency-agents
Source: https://github.com/agentprojectcontext/apx/tree/main/src/core/runtime-skills/apx-agency-agents
Command: npx skills add https://github.com/agentprojectcontext/apx --skill apx-agency-agents-agentprojectcontext

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams repeatedly recreate the same agent personas (developer, QA, marketing, ops) across projects. This Skill provides a global, project-agnostic vault of agent templates so specialists can be listed, imported, customized, or hidden once and reused everywhere. ## Core Features & Use Cases - Two-layer template vault: Bundled read-only defaults ship with the repo while user templates in ~/.apx/agents override them per-slug, with copy-on-write editing and tombstone-based hiding of bundled entries. - 14 bundled starter templates: A named team (orchestrator, architect, developer, qa-engineer, growth, security, pm, designer, billing) plus generic specialists (development, marketing, ops, qa, support), all with Spanish language defaults and inheriting the project model. - CLI, daemon, and web CRUD: List, add, remove, restore, and import templates via apx agent vault commands, daemon tool APIs like list_vault_agents, or the Agent Defaults web tab. - Use Case: A user says "spawn a QA agent" — the Skill imports the qa-engineer template from the vault into the current project, optionally copying it locally for edits. ## Quick Start Ask the agent to list the available vault templates and import the developer agent into the current project.

Frequently Asked Questions about apx-agency-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import an agent template into my APX project?▼

Run `apx agent import <slug>` to reference a vault template in the current project, or add `--copy` to duplicate it into .apc/agents/ for local edits. Use `--force` to overwrite an existing agent with the same slug.

How do I create a new reusable agent template?▼

Run `apx agent vault add <slug>` with flags like --role, --model, --language, --skills, and --description. The template is written to ~/.apx/agents/<slug>.md and becomes available to every project.

What happens when I edit or delete a bundled agent template?▼

Editing a bundled template is copy-on-write: a copy materializes in the user layer at ~/.apx/agents/ and overrides the bundled version. Deleting a bundled entry creates a restorable tombstone in .removed.json rather than removing files.

Which agent should I use for a generic developer or QA role?▼

Use the generic specialist slugs (development, qa, marketing, ops, support) when you want a plain functional role without a persona. Use the named team slugs like orchestrator, architect, or qa-engineer when you want a fuller role definition.

Do bundled agent templates require a sync step after install?▼

No. Bundled defaults live in the repo at assets/agent-vault-defaults/ and appear in `apx agent vault list` immediately on a fresh install. They ship with language es and no model, inheriting the project or global default model.