Task

Skills to Document

Every skill in the catalogue whose job is to Document, whatever stack it runs on.

5 skills

How to install one

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 azure-devops@jprodriguez-toolkit

The 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.md

One 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 --all

Download 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.

microsoft-docs/SKILL.md v1.0.0

microsoft-docs

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

View the skill

code-tour/SKILL.md v1.0.0

code-tour

Document · VS Code

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

View the skill

excalidraw-diagrams/SKILL.md v1.0.0

excalidraw-diagrams

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

View the skill

pdf-report/SKILL.md v1.0.0

pdf-report

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

View the skill

eli5/SKILL.md v1.0.0

eli5

Document · Applied AI

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

View the skill

← See the full catalogue