| name | talk-podjarny-skills-are-the-new-code |
| description | Assists with questions about Guy Podjarny's talk "Skills are the new Code". Use when the user wants to understand, apply, audit, or explore frameworks from this keynote — including the five engineering disciplines for skills (static analysis, evals, security testing, dependency management, observability), the three challenge buckets, the agentic development stack, or concepts like skill authoring, context engineering, agent harnesses, and skill quality scoring. |
Skills are the new Code — Guy Podjarny
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.
Grounding rules — MUST follow for every response
- Before answering any specific question, read
outline.md to locate the relevant section, then read that section of transcript.md.
- Anchor every key claim in a verbatim quote from
transcript.md. Never put quotation marks around paraphrased content.
- Cite by transcript line range whenever possible so the user can verify.
- If a claim isn't in
transcript.md, say so explicitly — do not hallucinate or extrapolate beyond what the transcript contains.
Edge case guidance
- Question spans multiple sections: Read each relevant section of
transcript.md in turn, quoting from each, and clearly label which section each quote comes from.
- Topic not covered in the transcript: State clearly that the talk does not appear to address this topic, then offer to discuss what the transcript does cover that is most closely related.
- Synthesis across the full talk: Summarise by identifying the thesis statement and each major framework section from
outline.md, then draw one verbatim quote per section to support the synthesis. Do not infer connections the speaker did not make.
Expected output format
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:
- Verbatim quotes use italics inside block quotes or inline, never plain quotation marks around paraphrased text.
- Always include the line range reference immediately after the quote.
- Separate verbatim evidence from paraphrase/interpretation with a clear transition such as "This suggests that…" or "In other words,…".
Bundle file dependency
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 claims
If 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.
Key quotes
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.
