Agent Company

This repository is a company package with department-level plugins for Claude, Codex, and Cursor.

This repo is structured so people can use it in multiple ways:

• As a Claude Code plugin system through the root marketplace plus department plugins
• As a skill collection via Vercel's npx skills
• In Codex
• In OpenClaw
• By cloning the repo and loading it manually
• By copying only the folders you want with shell scripts
• By installing only individual skills, agents, or commands

The active departments are:

• learning-system
• marketing
• sales
• engineering
• product
• business-ops

The active agents are:

• sales-prospecting
• executive
• deep-research
• financial-analyst
• growth-lead
• principal-engineer
• vp-of-operations

Install

Install matrix

| Method | Best for | Installs | |--------|----------|----------| | Claude Code marketplace + department plugin | Full repo with department plugins, teams, and shared references | Marketplace plus department plugin | | npx skills | Cross-agent skill install | Skills only | | Codex manual install | One skill or a small set of skills | Skills only | | Codex $skill-installer | Direct GitHub skill install inside Codex | Individual skills | | OpenClaw manual install | Local runtime skill folders | Skills, optionally agents/commands | | Git clone | Local development, forking, direct loading | Everything | | Symlink / shell copy | Selective local installs | Individual folders | | Sparse checkout | Pull only specific folders from Git | Individual folders |

1. Claude Code plugin

Use this when you want the full repo: root marketplace, department plugins, teams, references, commands, hooks, agents, and skills.

Claude now installs departments through the root marketplace at .claude-plugin/marketplace.json.

Local development

Run Claude against the department you want to work with:

claude --plugin-dir /absolute/path/to/repo/engineering
claude --plugin-dir /absolute/path/to/repo/marketing
claude --plugin-dir /absolute/path/to/repo/business-ops

Persistent install

Clone the repo once, then add the marketplace and install the department plugin you want:

mkdir -p ~/.claude/plugins
git clone https://github.com/alvarovillalbaa/plugins.git ~/.claude/plugins/agent-company

Inside Claude:

/plugin marketplace add /absolute/path/to/repo
/plugin install engineering@agent-company
/plugin install sales@agent-company

If the repo is hosted on GitHub, the flow is:

/plugin marketplace add alvarovillalbaa/plugins
/plugin install engineering@agent-company
/plugin install sales@agent-company

Update

cd ~/.claude/plugins/agent-company && git pull

2. Vercel npx skills

Use this when you want portable skill installation across supported agents.

Because the repo is now department-scoped, install from a department path or from a published skill repo that mirrors one skill.

Install from a local department path

npx -y skills add ./engineering
npx -y skills add ./marketing

Install all skills from selected departments globally

npx -y skills add -g ./engineering
npx -y skills add -g ./business-ops

Install for a specific agent

npx -y skills add -a codex ./engineering
npx -y skills add -a claude-code ./marketing

Install only selected skills

If your npx skills workflow accepts direct folder targets, point it at the skill folder:

npx -y skills add ./marketing/skills/seo-and-geo
npx -y skills add ./sales/skills/prospect-research

Install from a cloned local path

git clone https://github.com/alvarovillalbaa/plugins.git
cd plugins
npx -y skills add ./engineering

3. Codex

You still have the same three practical options: install via npx skills, install an individual skill manually, or use Codex $skill-installer.

Option A: install through npx skills

npx -y skills add -a codex ./engineering
npx -y skills add -a codex ./marketing

Option B: install a single skill manually

Copy a skill folder into your local Codex skills directory.

mkdir -p ~/.codex/skills
cp -R marketing/skills/seo-and-geo ~/.codex/skills/
cp -R engineering/skills/agentic-development ~/.codex/skills/
cp -R business-ops/skills/finances ~/.codex/skills/

Option C: install a single skill with Codex's skill installer

Inside Codex, use $skill-installer for repository-backed installs.

$skill-installer

If you want a skill from this repo, prompt the installer to fetch the skill from its new department path:

https://github.com/alvarovillalbaa/plugins/tree/main/engineering/skills/agentic-development
https://github.com/alvarovillalbaa/plugins/tree/main/marketing/skills/seo-and-geo
https://github.com/alvarovillalbaa/plugins/tree/main/business-ops/skills/finances

4. OpenClaw

OpenClaw users can still clone the repo and point the runtime at the specific department skills/ directory, or copy individual skill folders.

Full clone

mkdir -p ~/.openclaw/skills
git clone https://github.com/alvarovillalbaa/plugins.git ~/.openclaw/skills/agent-company

From there, point OpenClaw at one or more department skill roots:

~/.openclaw/skills/agent-company/engineering/skills
~/.openclaw/skills/agent-company/marketing/skills

Individual skill copy

mkdir -p ~/.openclaw/skills
cp -R marketing/skills/code-slides ~/.openclaw/skills/
cp -R sales/skills/prospect-research ~/.openclaw/skills/

Reload the runtime after install.

5. Git clone

Use this when you want the repo locally for development, inspection, or manual loading in any AI OS.

git clone https://github.com/alvarovillalbaa/plugins.git
cd plugins

From there you can:

• Load one department as a plugin if your runtime supports plugins
• Point your runtime at one or more <department>/skills/ directories
• Copy only selected agents/, commands/, or skills
• Symlink folders into a local skill registry

6. Install with shell scripts

Use plain sh commands if you want repeatable installs without a marketplace.

Copy one skill

mkdir -p "$HOME/.codex/skills"
cp -R marketing/skills/seo-and-geo "$HOME/.codex/skills/"

Copy several skills

mkdir -p ~/.codex/skills
cp -R marketing/skills/seo-and-geo ~/.codex/skills/
cp -R sales/skills/prospect-research ~/.codex/skills/
cp -R business-ops/skills/research ~/.codex/skills/

Symlink for local development

mkdir -p "$HOME/.codex/skills"
ln -s "$(pwd)/engineering/skills/agentic-development" "$HOME/.codex/skills/agentic-development"

7. Install only individual skills

Every folder under <department>/skills/ is installable on its own.

Examples:

cp -R business-ops/skills/finances ~/.codex/skills/
cp -R marketing/skills/code-slides ~/.openclaw/skills/
npx -y skills add ./sales/skills/message-outreach

8. Install only individual agents

If your runtime supports agent files, copy only the agent you want from the owning department.

Examples:

cp sales/agents/sales-prospecting.md /path/to/your/agents/
cp engineering/agents/principal-engineer.md /path/to/your/agents/
cp business-ops/agents/executive.md /path/to/your/agents/

The agent files reference skills by logical name, so the corresponding department skills should also be available in that runtime.

9. Install only individual commands

If your runtime supports command markdown files, copy only the files you need from the owning department.

Examples:

cp business-ops/commands/investor-messaging.md /path/to/your/commands/
cp marketing/commands/slides.md /path/to/your/commands/
cp engineering/commands/repo-review.md /path/to/your/commands/

Command support is runtime-specific. In some environments, commands are ignored while skills still work.

10. Sparse checkout for partial clone

Use sparse checkout if you want only one part of the repo without pulling everything.

One skill

git clone --filter=blob:none --no-checkout https://github.com/alvarovillalbaa/plugins.git
cd plugins
git sparse-checkout init --cone
git sparse-checkout set marketing/skills/seo-and-geo
git checkout main

Only agents and commands

git clone --filter=blob:none --no-checkout https://github.com/alvarovillalbaa/plugins.git
cd plugins
git sparse-checkout init --cone
git sparse-checkout set sales/agents engineering/agents marketing/commands business-ops/commands
git checkout main

11. Other compatible approaches

Depending on the runtime, these also work:

• Install from a local path after cloning the repo
• Use symlinks instead of copies for local development
• Fork the repo and install from your own GitHub namespace
• Vendor specific <department>/skills/<name> folders into another repo
• Use the repo as a template for your own internal company package

12. Cursor

Cursor should target a department directory because each department contains its own .cursor-plugin/plugin.json.

Examples:

• engineering/
• marketing/
• sales/

Structure

agent-company/
├── .claude-plugin/marketplace.json
├── COMPANY.md
├── assets/
├── scripts/
├── references/
├── learning-system/
├── marketing/
├── sales/
├── engineering/
├── product/
└── business-ops/

Each department follows the same contract:

department/
├── .claude-plugin/plugin.json
├── .codex-plugin/plugin.json
├── .cursor-plugin/plugin.json
├── TEAM.md
├── profile.yaml
├── skills/
├── agents/
├── commands/
├── hooks/
└── scripts/

Department map

• learning-system: auto-improve, memory-management, second-brain
• marketing: content, SEO/GEO, social, slides, video, visual content
• sales: GTM, pipeline, prospect research, outreach
• engineering: implementation, QA, docs, security, cloud, AI engineering
• product: product development and product strategy support
• business-ops: finance, reporting, research, review, executive operating cadence

Notes

• The repo root is no longer the Codex or Cursor plugin root.
• The repo root is the Claude marketplace root and the company package root.
• Legacy root-level manifests, hooks, agents, and commands were moved under references/legacy.

License

MIT. See LICENSE.