talk-walter-runtime-intelligence-agents

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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

85%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted skill for grounding answers in a specific talk transcript. Its strengths are the clear verification workflow, explicit fallback behavior for missing information, and good progressive disclosure across referenced files. The main weakness is minor verbosity in the grounding rules and example outputs, where some points are restated in slightly different ways.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some redundancy — the grounding rules repeat the idea of verbatim quoting multiple times, and the example outputs are somewhat lengthy. However, it avoids explaining concepts Claude already knows and stays focused on task-specific instructions.	2 / 3
Actionability	The skill provides highly concrete, actionable guidance: a clear lookup workflow (outline.md → transcript.md → verify), explicit grounding rules with specific do/don't behaviors, example Q&A pairs showing expected output format, and a fallback pattern for when information isn't found. Claude knows exactly what to do.	3 / 3
Workflow Clarity	The multi-step process is clearly sequenced: (1) read outline.md to locate section, (2) read that section of transcript.md, (3) draft answer with verbatim quotes, (4) verify quotes appear verbatim before presenting. There's an explicit validation checkpoint (rule 4) and a clear error-handling path (rule 3 for missing claims). For a retrieval/grounding task, this is thorough.	3 / 3
Progressive Disclosure	The skill clearly references three supporting files (outline.md, transcript.md, quotes.md) with well-signaled purposes for each. The SKILL.md serves as a concise overview with grounding rules and examples, while detailed content lives in the referenced files. Navigation is one level deep and clearly explained.	3 / 3
	Total	11 / 12 Passed

Description

100%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly defines its scope around a specific talk, lists concrete actions it performs, and provides extensive explicit trigger guidance. The description is thorough without being padded, uses third-person voice correctly, and includes a rich set of natural trigger terms that would help Claude accurately select this skill. The only minor concern is its length, but the detail is justified given the specificity of the domain.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'detailed answers, analysis, verbatim-grounded summaries, framework applications, and workflow audits'. It also enumerates specific concepts covered like 'runtime code sensor', 'prod-to-code mapping', 'scoring fixes by impact and risk', and the 'layered architecture'.	3 / 3
Completeness	Clearly answers both 'what' (provides detailed answers, analysis, summaries, framework applications, workflow audits based on the talk) and 'when' (explicit 'Use when the user asks about May Walter's talk' followed by an extensive list of specific trigger scenarios).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms a user would say: 'May Walter's talk', 'Hud's runtime code sensor', 'prod-to-code mapping', 'automating the performance-investigation phase', 'scoring fixes by impact and risk', 'automated pull requests', 'layered architecture', 'four takeaways', 'agentic engineering', 'AI agents into the SDLC'. These are highly specific and natural phrases someone familiar with the talk would use.	3 / 3
Distinctiveness Conflict Risk	Extremely distinctive — it is scoped to a single specific talk by a named speaker with highly specific concepts (Hud's runtime code sensor, prod-to-code mapping, the four takeaways). This is very unlikely to conflict with any other skill.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: AINativeDev/aidevcon-2026-ldn
Path: talk-walter-runtime-intelligence-agents/SKILL.md
Commit: 1887349

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.