Portable Library
This catalog now mirrors the department-scoped plugins repo. Every skill lives under a concrete <department>/skills/<slug> path, and the install flows differ by runtime, so the site surfaces both the library and the current install matrix.
Featured Skills
Use for end-to-end software execution in an unfamiliar or complex repo: orienting the codebase, choosing an execution model, planning and verifying changes, reviewing architecture or PRs, and coordinating work across the specialized `frontend` and `backend` engineering skills.
Cross-cloud CLI-first cloud operations for AWS, Azure, and GCP. Use when the assistant needs to identify which cloud provider or multi-cloud estate a repo uses, deploy new resources or services, wire automatic deployments, inventory and optimize infrastructure, or diagnose and repair cloud failures entirely from the terminal, with explicit approval gates for high-cost, destructive, identity-sensitive, or hard-to-reverse changes.
Create and evolve code-based slide decks and presentations (pitch decks, demos, product walkthroughs, technical talks) with HTML/CSS/JS or React/TypeScript. Use when a user asks for slides implemented in code, a single-file HTML presentation, responsive behavior across mobile/tablet/desktop, PowerPoint/PPTX-to-web conversion, remote-control navigation, configurable right-side or bottom navigation, iframe-based deck rendering, visual style exploration, or image workflows that combine AI-generated assets, external URLs, local repo images, and code-as-image product mockups. Trigger this skill for new deck creation, redesigns, refactors, framework migrations, PPT conversions, and slide-quality QA.
Use for finance work across accounting reconciliation, financial modeling, and fundraising materials. Covers statement-to-ledger reconciliation, receipt linking, cash flow and scenario models, cap tables, investor messaging, materials audits, and fundraising process diagnostics.
Go-to-market planning and revenue execution skill for positioning, target segment definition, first-customer acquisition, launch plans, messaging hierarchies, pricing, channel strategy, technical pre-sales, growth experimentation, revenue intelligence, pipeline and forecast review, retention and expansion planning, content-to-revenue attribution, client reporting, and commercialization decisions. Use when the user needs a coherent market-facing plan tying product value to buyers, message, motion, channels, pricing, experiments, deal support, call insights, attribution, post-sale growth, revenue metrics, launch timing, and launch risks.
Use for SEO, GEO, and AEO work: keyword research, on-page optimization, AI-citation readiness, technical SEO audits, content gap analysis, competitor benchmarking, structured data, Core Web Vitals, internationalization, entity optimization, backlink analysis, content refreshes, and monitoring. Trigger when the user wants better search visibility in traditional or AI search systems.
Installation Modes
The old flat skills/<slug> commands are no longer the source of truth. Use these runtime-specific flows for full department plugins, selective skill installs, or local development.
Claude Code marketplace
Marketplace plus one department pluginFull department plugins with teams, hooks, commands, references, and skills.
/plugin marketplace add alvarovillalbaa/plugins
/plugin install engineering@agent-companyThis is the current top-level plugin flow from the repo README. Install departments, not root-level single skills.
Vercel `npx skills`
Skills onlyCross-agent skill installs from a department or a single skill folder.
npx -y skills add ./engineering
npx -y skills add ./marketing/skills/seo-and-geoThe repo is department-scoped now, so both department roots and individual skill folders are valid targets.
Codex manual install
Skills onlyInstalling one skill or a small set of skills with local control.
mkdir -p ~/.codex/skills
cp -R engineering/skills/frontend ~/.codex/skills/Use the department path that owns the skill instead of the old flat `skills/<slug>` layout.
Codex `$skill-installer`
Individual skillsDirect GitHub-backed skill installs inside Codex.
$skill-installer
https://github.com/alvarovillalbaa/plugins/tree/main/engineering/skills/frontendPoint the installer at the concrete department skill path in GitHub.
OpenClaw manual install
Skills, optionally agents and commandsLocal runtime skill folders, optionally alongside copied agents or commands.
mkdir -p ~/.openclaw/skills
cp -R marketing/skills/code-slides ~/.openclaw/skills/OpenClaw still works as a selective local copy workflow.
Git clone
EverythingLocal development, direct loading, inspection, or forking.
git clone https://github.com/alvarovillalbaa/plugins.git
cd pluginsClone once when you want the entire company package and all department plugins locally.
Sparse checkout
Individual foldersPulling only one department or skill subtree from Git.
git clone --filter=blob:none --no-checkout https://github.com/alvarovillalbaa/plugins.git
cd plugins
git sparse-checkout init --cone
git sparse-checkout set engineering/skills/frontend
git checkout mainUseful when you only need one skill path and want to avoid cloning the full repo.
Catalog
Results are ranked using the same local vector + lexical blend that powers the MCP layer, now against the current department-scoped plugin catalog.
Engineering
General software-engineering orchestration skill for unfamiliar or complex repositories.
Use for end-to-end software execution in an unfamiliar or complex repo: orienting the codebase, choosing an execution model, planning and verifying changes, reviewing architecture or PRs, and coordinating work across the specialized `frontend` and `backend` engineering skills.
engineering/skills/agentic-development
How it works
Engineering
AI and data engineering skill for ML systems, pipelines, prompt workflows, evaluation, and production AI architecture.
Use for ML, data, and AI engineering work: data pipelines, ETL and ELT, DataOps, warehouses and lakehouses, streaming systems, prompt and agent design, RAG, constrained generation, experiment design, model evaluation, feature engineering, and computer vision systems from dataset prep through production deployment.
engineering/skills/ai-engineering
How it works
Engineering
Backend engineering skill for APIs, services, schemas, persistence, and server-side operational work.
Use for backend engineering work such as APIs, services, data models, persistence, queues, caching, auth, background jobs, and server-side debugging or refactors.
engineering/skills/backend
How it works
Engineering
CLI-first cloud operations skill for AWS, Azure, and GCP.
Cross-cloud CLI-first cloud operations for AWS, Azure, and GCP. Use when the assistant needs to identify which cloud provider or multi-cloud estate a repo uses, deploy new resources or services, wire automatic deployments, inventory and optimize infrastructure, or diagnose and repair cloud failures entirely from the terminal, with explicit approval gates for high-cost, destructive, identity-sensitive, or hard-to-reverse changes.
engineering/skills/cloud-management
How it works
Engineering
Documentation skill for READMEs, architecture notes, runbooks, ADRs, changelogs, and code-adjacent technical writing.
This skill should be used when the user asks to write, update, review, scaffold, or reorganize documentation for code, folders, services, repos, workflows, architectural decisions, or operational processes. Trigger for `README.md`, `ARCHITECTURE.md`, `TESTS.md`, `SETUP.md`, `RUNBOOK.md`, `CHANGELOG.md`, `SECURITY.md`, `OVERVIEW.md`, `FAQ.md`, `DECISIONS.md`, `DEPENDENCIES.md`, `AGENTS.md`, `PLAN.md`, `SPEC.md`, `SOUL.md`, `PRINCIPLES.md`, `DESIGN.md`, `runbooks/**/*.md`, `docs/**/*.md`, MDX docs, JSDoc/TSDoc, docstrings, ADRs, post-mortems, migration guides, and PR documentation-impact reviews.
engineering/skills/code-documentation
How it works
Engineering
Frontend engineering skill for browser-facing implementation, UI systems, and design-quality work.
Use for frontend engineering work such as components, routes, state management, accessibility, performance, design-system integration, and browser-facing debugging or refactors.
engineering/skills/frontend
How it works
Engineering
Authorized offensive-security skill for validating exploitability against approved targets.
Use for authorized hands-on offensive security work against staging, sandbox, or lab targets. Covers pentest planning, finding validation, exploitability proof, raw HTTP replay, browser and API testing, network and cloud assessment, secrets and misconfiguration discovery, bounded post-exploitation, and evidence-driven pentest reporting. Do not use for passive code review or compliance audits.
engineering/skills/pentest
How it works
Engineering
Pull request management skill for designing or improving review systems, merge policies, SLAs, and workflow health at team scale.
Pull request management skill for teams from 1 to 1000+ engineers. Use when the user needs to design or improve PR workflow, review queues, merge policy, ownership rules, branch strategy, review SLAs, CI gating, metrics, or operating rituals for getting code reviewed and merged safely at scale.
engineering/skills/pr-management
How it works
Engineering
End-to-end QA skill for testing, debugging, secure engineering, code review, and release confidence.
End-to-end quality assurance and secure engineering for any software repo: code review, test strategy, bug triage, debugging, flaky-test repair, coverage analysis and improvement, suite architecture, CI quality gates, secure coding reviews, security audits, threat modeling, compliance validation, and dependency or vulnerability management for frontend, backend, full-stack, and AI systems. Use when reviewing PRs, writing or repairing tests, debugging failing suites, improving release confidence, creating test plans, running passive security reviews, or translating threats into requirements. For authorized active penetration testing, exploit validation against a running target, or pentest reporting, use `pentest`.
engineering/skills/quality-assurance
How it works