Provides detailed answers, analysis, verbatim-grounded summaries, framework applications, and workflow audits based on May Walter's talk "From Blind Spots to Merged PRs: Runtime Intelligence for Continuous Agentic Performance Optimization". Use when the user asks about May Walter's talk — including questions about Hud's runtime code sensor, the prod-to-code mapping concept, automating the performance-investigation phase, scoring fixes by impact and risk, why automated pull requests didn't work, the layered architecture (query language → skills → automations), the four takeaways (define what matters, automate investigation, context over cleverness, agentic engineering ≠ coding with an agent), or applying Walter's approach to integrating AI agents into the SDLC.
73
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
May Walter presents a real customer case study of adding runtime intelligence to coding agents to continuously surface high-ROI performance fixes in production. All answers must be grounded verbatim in transcript.md; use outline.md to navigate to the relevant section first.
outline.md to locate the relevant section, then read that section of transcript.md.transcript.md. Never put quotation marks around paraphrased content.transcript.md, say so explicitly — do not infer, extrapolate, or fill gaps with plausible-sounding content. Respond with something like: "That specific point does not appear in the transcript. Here is what Walter does say about the closest related topic: …"transcript.md before presenting it.outline.md — a structured table of contents for the talk, mapping topic headings to approximate timestamp ranges or section numbers. Use this as a navigation index before diving into the full transcript.transcript.md — the full verbatim transcript of Walter's talk. All quotations and factual claims must be grounded here.(After locating the relevant section via
outline.mdand reading it intranscript.md)Walter explains that automated PRs failed because engineers didn't trust them — they had no visibility into why a fix was suggested. In her words (verbatim from transcript): "[paste exact quote here]." The takeaway she draws is that context over cleverness matters: a human-readable explanation of the evidence behind a fix drives more merges than a polished PR with no provenance.
(If the term appears in
transcript.md)Walter defines prod-to-code mapping as … [verbatim quote]. She uses it to describe how Hud's runtime code sensor links production telemetry back to the specific function or query responsible.
(If the exact term does not appear in
transcript.md)The phrase "prod-to-code mapping" does not appear verbatim in the transcript. Here is what Walter does say about the closest related topic: she describes how Hud's runtime code sensor connects production signals to specific functions and queries, enabling agents to surface fixes with full provenance. [verbatim quote from the relevant section of transcript.md].
quotes.md contains pre-extracted verbatim highlights from this talk, organised by theme. When formulating answers, check quotes.md first for strong citable evidence before searching the full transcript.md.
1887349
Also appears in
on Aug 28, 2026
since Jun 18, 2026
since Jun 4, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.