Plugin
The whole Engineering plugin: every skill it ships, each with its full file, and a single command that installs the lot.
7 skills
A skill is plain Markdown. The agent loads it on its own when the task matches its description.
/plugin marketplace add https://jesusprodriguez.com/skills/marketplace.json
/plugin install ingenieria@jprodriguez-toolkitThe native route, and the only one that updates itself: add the marketplace once and `/plugin marketplace update` brings in new versions. Skills get their own namespace (`azure-devops:azure-pr-review`).
SKILL=azure-pr-review
curl -fsSL https://jesusprodriguez.com/skills/$SKILL/SKILL.md --create-dirs -o .claude/skills/$SKILL/SKILL.mdOne command at the root of your project. Claude Code discovers it on its own: nothing to register.
$SKILL = "azure-pr-review"
New-Item -ItemType Directory -Force ".claude/skills/$SKILL" | Out-Null
Invoke-WebRequest "https://jesusprodriguez.com/skills/$SKILL/SKILL.md" -OutFile ".claude/skills/$SKILL/SKILL.md"One command at the root of your project. Claude Code discovers it on its own: nothing to register.
curl -fsSL https://jesusprodriguez.com/skills/install.sh -o install.sh
sh install.sh --allDownload the script, read it, run it. Installs one skill, a whole stack or all of them, and pulls in the dependencies between skills. With `--check` it compares the sha256 of what you have installed and lists only what changed.
Review · GitHub
Reviewing a PR starting from the blast radius —what else breaks if this breaks— and moving on to security, contracts and coverage.
when: Before merging anything that touches a shared library, an API contract or the data schema.
How to ask
Review PR 312: it touches the shared library and I want to know what else breaks.
Blast radius · Security sweep · Reversible migrations · A test that fails without the fix
Guided walkthroughs that open inside the editor, with every step anchored to a file and a line that actually exist.
when: When onboarding someone, explaining an architecture or accompanying a large PR.
How to ask
Prepare an onboarding tour of the domain layer for someone starting on Monday.
One tour per audience · Verified line numbers · Narrative arc · What ruins a tour
Document · Diagrams
Diagrams generated from a description that come out editable: flow, architecture, sequence, entity-relationship and swimlanes.
when: When explaining a process or a system with a picture that will need tweaking afterwards.
How to ask
Draw the flow for creating a case file, from the form to the processing queue.
Choosing the type · Grid and colour · Brand icons · When to split the diagram
Automate · Python
Automation scripts you can re-run without fear: dry-run, logging, honest exit codes and idempotency.
when: When writing CLIs, scheduled jobs, file processing or API integrations.
How to ask
Write a script that syncs the invoices folder with the SFTP, dry-run by default.
argparse and dry-run · logging · pathlib and encoding · APIs with timeouts
Document · Python
Reproducible PDF reports with ReportLab: tables that do not break, embedded fonts and identical output on every run.
when: When exporting a status report, an audit or any outward-facing document to PDF.
How to ask
Export this audit report to PDF with the tables not breaking across pages.
Platypus vs canvas · Tables with repeatRows · TTF fonts and accents · Pre-send checklist
Build · HTML / CSS
Self-contained interactive artifacts à la Claude: a single HTML file with everything inlined that opens in the browser, ready to test.
when: When requesting a quick app, a dashboard, a game, a data visualisation or anything interactive to preview.
How to ask
Create an artifact with an interactive Snake game with premium design.
Interactive apps · Data visualisations · SVG diagrams · Formatted documents · Premium dark design
Clear explanations across 4 depth levels (ELI5 to Expert): intuitive analogies, visual diagrams, and verified sources.
when: When asking to explain a complex concept, algorithm, architecture, or bug across different depth levels.
How to ask
Explain how OAuth2 and JWT authentication work across 4 depth levels, starting with an ELI5.
4 depth levels · Analogies & mental models · Visual diagrams · Verified sources & citations