engineering
Engineering plugin with 9 installable skills, including Agentic Development and Cloud Management.
Open source folderCopy-paste prompt
Install Engineering (engineering) from https://github.com/alvarovillalbaa/plugins/tree/main/engineering. Detect the current agent runtime first, including Codex, Claude Code, Cursor, Claude Code-compatible shells, OpenClaw, or Vercel `npx skills`. Install the necessary skills for this repository or task, read every installed SKILL.md before acting, and report exactly which plugins or skills were installed.
9 total
Engineering
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
Engineering
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
Engineering
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
Engineering
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
Engineering
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
Engineering
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
Engineering
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
Engineering
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
Engineering
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