Product strategy, product management, and product marketing support plugin for the agent company.
Use for product strategy and product management work: PRDs, prioritization, roadmaps, discovery summaries, experiment plans, release criteria, decision memos, OKR planning, user stories, sprint planning, and in-product UX copy. Choose this when the user needs product framing, strategic tradeoffs, or delivery planning before implementation.
Use for product marketing work: positioning, messaging, ICPs, product marketing context, landing pages, CRO, content strategy, buyer psychology, proof points, and brand voice. Choose this when the user needs market-facing narrative or conversion-focused assets before execution.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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:
npx skillsThe active departments are:
learning-systemmarketingsalesengineeringproductbusiness-opsThe active agents are:
sales-prospectingexecutivedeep-researchfinancial-analystgrowth-leadprincipal-engineervp-of-operations| 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 |
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.
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
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
cd ~/.claude/plugins/agent-company && git pull
npx skillsUse 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.
npx -y skills add ./engineering
npx -y skills add ./marketing
npx -y skills add -g ./engineering
npx -y skills add -g ./business-ops
npx -y skills add -a codex ./engineering
npx -y skills add -a claude-code ./marketing
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
git clone https://github.com/alvarovillalbaa/plugins.git
cd plugins
npx -y skills add ./engineering
You still have the same three practical options: install via npx skills, install an individual skill manually, or use Codex $skill-installer.
npx skillsnpx -y skills add -a codex ./engineering
npx -y skills add -a codex ./marketing
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/
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:
npx claudepluginhub alvarovillalbaa/plugins --plugin productAuto-improve, memory management, and second-brain workflows for the agent company.
Prospecting, outreach, GTM support, and revenue workflow plugin for the agent company.
Content, SEO/GEO, social, slides, video, and visual content workflows for the agent company.
Architecture, implementation, QA, security, cloud, and documentation workflows for the agent company.
Finance, reporting, research, review, and operating cadence workflows for the agent company.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Complete developer toolkit for Claude Code
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.