Load this skill when evaluating, designing, or troubleshooting the feedback infrastructure around an agent workflow. Triggers on phrases like "why isn't my agent self-correcting", "how should I structure this project for agents", "review my agent setup", "what MCP servers should I attach", "my agent keeps needing…
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers.…
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Creates useful Mermaid diagrams for SWE, DevOps, and Platform Engineering work — PRs, ADRs, RFCs, runbooks, incident reviews, roadmaps, system architecture, and more. Use this skill whenever the user wants to visualize a technical initiative, system change, workflow, deployment pipeline, data model, service topology…
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
Generate a complete, mental-model-first course on any technology — a landing README, a CHEATSHEET, and dependency-ordered numbered course units, each following a fixed learn → why → concepts → exercises → self-checks → takeaways template, grounded in primary sources before any content is written and with the syllabus…
Orient new contributors and developers to a repository or technology through structured, planned exploration. Uses creative-planner to design the tour path, then tree, ls, eza, and cat to map the filesystem landscape live. When unknowns arise, searches the web for current documentation rather than relying on…
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
AGENTS.md instructions for mcwalrus/oppertunity-party, covering agent instructions, project overview, key paths, data pipeline and operations go through dagster.
Claude Code instructions for mcwalrus/oppertunity-party, a project described as: ETL pipeline for opportunity.org.nz — Dagster orchestration, clean markdown corpus, Astro static site.