Readable source
Every ZIP includes the same plain SKILL.md linked on the page. There are no bundled credentials, executable hooks, or hidden remote services.
Maintained · downloadable · reviewable
This is no longer a catalogue of every possible agent role. It is a maintained set of engineering workflows that match the tools and field notes on this site. Each package exposes its instructions in plain text, states where human judgment is required, and can be reviewed before installation.
Current collection · 8 skills
The collection is intentionally limited. A skill stays here only when it has a specific input contract, a reproducible output shape, a safety boundary, and a portable download.
Plan a WCAG 2.2 review across automated checks, keyboard navigation, screen readers, zoom, and cognitive load.
Review the audit skill → OperationsAssign roles, structure updates, preserve a decision log, and define recovery criteria during an outage.
Review the incident skill → SecurityMap trust boundaries, rank credible threats, and produce fixes tied to evidence and ownership.
Review the security skill → ReliabilityDefine user-centered SLIs and SLOs, interpret error budgets, and identify automation candidates.
Review the SRE skill → API qualityBuild risk-based coverage for contracts, authorization, failure modes, idempotency, and performance.
Review the API testing skill → Software qualityReview a change for correctness, security, maintainability, performance, and missing tests.
Review the code review skill → ContainersDesign reproducible multi-stage builds with deliberate caching, permissions, health checks, and verification.
Review the Dockerfile skill → Web qualityPlan coverage across user behavior, integrations, accessibility, performance, visuals, and browsers.
Review the web testing skill →What “maintained” means
Every ZIP includes the same plain SKILL.md linked on the page. There are no bundled credentials, executable hooks, or hidden remote services.
Each workflow says what evidence it needs, what it should return, and which decisions still belong to a human owner.
The site source and issue history live on GitHub. The testing and editorial method explains how examples and updates are reviewed.