AI Native DevCon 2026 London — all conference sessions as interactive skills
66
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Guy Podjarny (founder of Tessl, previously founder of Snyk) argues that skills are the new unit of software being authored in the agentic-development stack, and that they deserve the same engineering rigour — static analysis, evals, security testing, dependency management, and observability — applied to code.
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 hallucinate or extrapolate beyond what the transcript contains.transcript.md in turn, quoting from each, and clearly label which section each quote comes from.outline.md, then draw one verbatim quote per section to support the synthesis. Do not infer connections the speaker did not make.Every substantive answer should follow this pattern:
User: What does Guy Podjarny say about evals for skills?
Response: In the section on engineering disciplines (transcript lines 312–340), Podjarny states: "[verbatim quote from transcript.md]" He goes on to argue "[second verbatim quote if needed]" (lines 341–355). This means that [brief, clearly-labelled paraphrase — no quotation marks].
Key formatting rules:
This skill requires two files to be present in the bundle:
outline.md — section map of the talk, used for navigationtranscript.md — full verbatim transcript, used for grounding all claimsIf either file is missing or unreadable, inform the user that the required transcript files are unavailable and that answers cannot be reliably grounded without them.
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.
.tessl-plugin
talk-batey-building-product-teams-age-of-ai
talk-birgitta-closing-keynote
talk-debois-agent-enablement
talk-douglas-training-ai-on-your-own-code
talk-dubnov-merge-rate-ai-adoption
talk-farley-vibe-coding-best-we-can-do
talk-firtman-web-mcp-agentic-web
talk-foxwell-reinvention-dev-team
talk-graziano-spec-driven-development
talk-groetzinger-skills-everywhere
talk-jones-odevo-ai-native-transformation
talk-jourdan-pipelines-to-prompts
talk-katsioloudes-code-security-ai
talk-lamis-context-engineering-dreaming
talk-lawson-agent-experience
talk-luebken-embedding-pi-coding-agent
talk-maleix-collective-intelligence
talk-maple-ai-native-devcon-welcome-slick
talk-maple-ai-native-devcon-welcome-spec-reviewer
talk-maple-aind-devcon-welcome
talk-maple-context-engineering-skills
talk-maple-continuous-ai-github-workflows
talk-maple-harness-engineering
talk-maple-tldraw-ai-canvas-experiments
talk-marsden-agent-desktops
talk-martinelli-spec-driven-development
talk-moss-skills-team-workflow
talk-overweg-one-brain-no-filtering
talk-podjarny-skills-are-the-new-code
talk-roberts-ai-native-brownfield
talk-roberts-brownfield-ai-native
talk-scheire-artificial-intelligence
talk-selajev-docker-sandboxes-agents
talk-sloan-harness-engineering-beyond-code
talk-stack-humans-architect-ai-writes-code
talk-stoneham-product-brain
talk-tal-skills-security
talk-thomas-ai-native-engineering
talk-walter-runtime-intelligence-agents
talk-wilson-cq-stack-overflow-for-agents
talk-wotherspoon-humans-vs-slop