/skills
The conventions I follow, packaged as Markdown skills for Claude Code, Cursor or any agent that reads instructions from a file. Each one is a real file, proven on real projects: open it, read the whole thing, take it with you.
Installation
A skill is plain Markdown and the agent loads it on its own when the task matches its description. The native route is the only one that updates itself: add the marketplace once and /plugin marketplace update brings in the new versions.
/plugin marketplace add https://jesusprodriguez.com/skills/marketplace.json
/plugin install azure-devops@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.
No skill matches that search.
Try a shorter term.
Pull request review, a prioritised inbox, sprint status, backlog health and planning on Azure DevOps.
/plugin install azure-devops@jprodriguez-toolkit Automate · Azure DevOps
The access foundation for Azure DevOps: a PAT with the right scope, CLI defaults, WIQL, Analytics OData and honest pagination.
when: When reading from or writing to Azure Repos, Boards or Pipelines from the terminal.
How to ask
Set up Azure DevOps access in this repo and check the PAT has the scopes it needs.
PATs and scopes · az devops / az boards · WIQL queries · REST and pagination
Review · Azure DevOps
Review a pull request against risk criteria —correctness, contract, security— and leave every comment anchored to the right line.
when: When reviewing a specific PR or forming the verdict before approving.
How to ask
Review PR 4821 in the Expedientes repo and leave the comments anchored to the right thread.
Diff from refs/pull · Risk checklist · Inline threads over REST · Blocker vs suggestion
↳ requires azure-devops-cli
Report · Azure DevOps
A PR inbox prioritised by who is blocking whom: what is waiting on your vote, what of yours is stalled, and what has been open too long.
when: At the start of the day, or when asking which pull requests are on your plate.
How to ask
Tell me which pull requests are on my plate this morning and which ones are blocking someone.
Waiting on your vote · Age and size · Conflicts and builds · Alerts without noise
↳ requires azure-devops-cli
Report · Azure DevOps
A status report you can actually decide from: progress against what was committed, blockers, incoming scope and what will not make it.
when: Before a daily, a demo or a steering meeting, or when asking how the project is going.
How to ask
Prepare the current sprint status for Friday’s demo, flagging what will not make it.
Sprint via WIQL · Projected pace · Blockers and risks · Steering-meeting variant
↳ requires azure-devops-cli
Audit · Azure DevOps
A backlog audit with written thresholds: unestimated, criteria-less, stalled items, untriaged bugs, unclosed epics and zombies.
when: Before a refinement session, or as a periodic backlog review.
How to ask
Audit the project backlog before Tuesday’s refinement and rank the alerts for me.
Seven threshold alerts · Untriaged bugs · Likely duplicates · Capped alerting
↳ requires azure-devops-cli
Plan · Azure DevOps
PBIs you can estimate and close without argument: verifiable criteria, explicit out-of-scope and complete fields.
when: When creating a PBI, a bug or a feature, or rewriting one that arrives empty.
How to ask
Rewrite PBI 3120: it arrives with no acceptance criteria and no defined scope.
Acceptance criteria · Bug template · Required fields · When to split
↳ requires azure-devops-cli
Plan · Azure DevOps
Breaking PBIs into half-day to two-day tasks, with external dependencies flagged and the question of whether the sprint actually fits.
when: During sprint planning, or when splitting a large PBI into tasks.
How to ask
Break PBI 3477 into tasks and tell me whether the sprint fits the capacity we have.
Splitting by criteria · Time-boxed spikes · Capacity vs velocity · Dependencies
↳ requires azure-devops-cli
Plan · Azure DevOps
A PBI turned into a plan anchored to the real code before a line is written: a reasoned approach, changes per layer and an executable checklist.
when: Before implementing anything that spans several layers, or to validate the approach with the team.
How to ask
Plan PBI 5104 against this repository and attach the plan to the work item.
Criteria taken as written · Real file paths · Changes per layer · Attaching to the work item
↳ requires azure-devops-cli
Build · Azure DevOps
From work item ID to a tree ready for review: branch, implementation against the criteria, build and tests, changelog and PR note. Nothing committed.
when: When starting a PBI or Bug by its number and taking it to the point of review.
How to ask
Implement Bug 5210 and leave it ready for review, without committing anything.
Branching from the base · Plan or fast mode · Build and test before stopping · Why it never commits
↳ requires azure-devops-cli
Audit · Azure DevOps
A snapshot of the code across several repos at once: activity, vulnerable dependencies, hotspots, divergence and secrets in the history.
when: When assessing the state of a project's code, or deciding where to invest maintenance effort.
How to ask
Give me a snapshot of the state of the code across the Expedientes project repos.
Inventory and activity · Vulnerabilities · Hotspots by churn · Five actions
↳ requires azure-devops-cli
Automate · Azure DevOps
YAML pipelines that do not block the team: one artefact for every environment, versioned templates, secrets kept out of the repo.
when: When creating or changing azure-pipelines.yml, or when a build fails only on the agent.
How to ask
Review azure-pipelines.yml: the build passes locally and fails only on the agent.
Stages and environments · Templates and caching · Secrets and approvals · Debugging the agent
REST APIs on .NET 8, correctness bug hunting in C# and checking against the official Microsoft docs.
/plugin install dotnet@jprodriguez-toolkit Build · .NET Core
Structure and checklist for a REST API in .NET 8: Minimal APIs per resource, EF Core without N+1, and errors as ProblemDetails.
when: When creating endpoints, modelling entities with EF Core or debugging slow queries.
How to ask
Build the orders endpoint in .NET 8, following the structure the project already has.
Minimal APIs · EF Core · ProblemDetails · Configuration and secrets
A targeted hunt for correctness bugs in C# and TypeScript: concurrency, nulls, dates, half-finished transactions and swallowed errors.
when: When hunting bugs, reviewing a suspicious module or making sense of an intermittent failure.
How to ask
Hunt for correctness bugs in the billing module: an amount comes out wrong every now and then.
Follow the data · Async and concurrency · Dates and decimals · Reports with a scenario
Document · .NET Core
Checking the official docs before writing code against Azure or .NET SDKs: that the method exists, that the signature is right, and that the pattern is not deprecated.
when: When using a Microsoft API for the first time, or when an error does not match what you expected.
How to ask
Check the official docs on whether BlobClient.UploadAsync accepts that overload.
Queries that narrow down · Verifying signatures · Mixed SDK versions · Deprecated patterns
Static Astro sites, local-business landing pages and ranking in your own city.
/plugin install web@jprodriguez-toolkit Build · Astro
Conventions for Astro sites with static output: content collections, optimised images and islands only where they are needed.
when: When creating .astro pages or components, defining collections or reviewing performance.
How to ask
Add a notes content collection to this Astro site, with its listing page.
Content collections · astro:assets · Islands and client:* · Core Web Vitals
Build · Conversion
A one-page site for a local business: structure, second-person copy, a single call to action and fast loading on mobile.
when: When building a client landing page, or working out why a pretty site brings no calls.
How to ask
Build the landing page for a dental clinic in Alcorcón, with a single contact form.
Block-by-block structure · Copy and objections · A 3-field form · Legal and handover
Ranking in your own city: business profile, NAP consistency, LocalBusiness JSON-LD and per-service pages with original content.
when: When publishing a local business site, or when it does not show up in searches for its area.
How to ask
This site for a garage in Getafe does not show up for “garage Getafe”: tell me why.
Business profile · NAP consistency · LocalBusiness JSON-LD · What not to do
The cross-cutting set: GitHub PR review, guided code tours, editable diagrams, Python automation, PDF reports and layered explanations.
/plugin install ingenieria@jprodriguez-toolkit 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
The catalogue also reads without a browser: the index carries the sha256 of every file, so checking whether something changed does not mean downloading it again.
Ecosystem & Community
My skills focus on Azure DevOps, .NET, architecture, and team workflows. For TypeScript, frontend, or open component libraries for Claude Code, these are the two references I recommend most:
The most downloaded skills repository on GitHub. Focused on engineering discipline and prompting dynamics (/grill-me, /to-spec, /wayfinder, TypeScript).
Open catalogue with over 1,000 components, specialized agents, commands, and MCPs ready to use in Claude Code.
A catalogue in progress: I publish more as I refine them on real projects. The rest of my stack lives in Tools.
Where these come from
They are not templates: they are the calls I made reviewing real PRs, planning sprints that had to ship, and debugging builds that only failed on the agent. If you want to set up the same flow in your team, tell me the context.
Get in touch