AI Native DevCon 2026 New York — practical agent skills grounded in conference talks
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Help the user deliver the right context to an agent by distinguishing reusable instructions from information assembled for the current task. Apply Birgitta Boeckeler's lifecycle model to the user's sources, retrieval behavior, and maintenance process.
This is Tessl's adaptation of the talk. It is a planning and reasoning resource, not an Unblocked product manual or an implementation of a context engine.
https://www.youtube.com/watch?v=NxypyNu1944&t=SECONDS when useful. Quote only the transcript's actual words; prefer a paraphrase if the wording is garbled.Start with the task and delivery phase, then classify individual pieces of information. Do not classify a whole system or document solely by file extension or the tool used to retrieve it.
Keep the categories complementary. A reusable retry-review rule can be codified, while an incident discussion supplies the relevant history. Extracting a durable lesson from an incident into reviewed guidance is a recommended application; keep its provenance and separate it from changing incident details.
Avoid codifying frequently changing environmental data into skills, and avoid relying on search to rediscover essential reusable instructions. The speaker makes both points at 25:08–25:39, cues 369–376.
Use the context design and audit template when the user needs an artifact. Draft with explicit assumptions rather than stopping for details that can be marked as unknown.
For codified context, use the generate, evaluate, distribute, observe loop discussed at 07:21–08:12, cues 112–123. Birgitta attributes that framing to Patrick Debois. Check where reusable instructions live, how changes are reviewed and tested, how agents receive the intended version, and how problems are noticed.
For ambient context, use ingest, evaluate, assemble, observe. The talk replaces generate with ingest and distribute with assemble at 12:38–12:59, cues 190–194.
Assess quality using the talk's lenses: clarity, actionability, fidelity, efficiency, with security cutting across them (09:06–09:54, cues 136–148). A relevant answer can still fail if it relies on stale information, hides an unresolved conflict, or exposes material to the wrong audience.
When sources disagree, show the conflicting claims and inspect their date, scope, provenance, author expertise, and relevant implementation evidence. Cross-system identity must be established before treating two accounts as the same expert. Use a person's role or expertise as a signal, not automatic proof.
The speaker calls code a source of reality, rather than an unconditional source of truth (19:52–20:27, cues 297–303). Code can show what currently happens; it does not by itself decide what should happen or override an intended requirement. That distinction is a recommended application of the talk's framing.
If evidence does not resolve the conflict, surface it with the remaining uncertainty and the smallest next verification needed. Do not silently choose the latest message, the highest-ranking author, or code by default. The talk explicitly describes passing unresolved conflicts back to the calling agent at 20:27–20:41, cues 304–306.
Read the material the user supplies and return finding, evidence, consequence, proposed change, verification. Prioritize:
Distinguish inspected findings from hypotheses based only on a description. Produce a design or audit unless the user asks for changes; do not connect new sources, broaden sharing, or post messages as a side effect of applying this skill.
Lead with the practical decision or finding, then give the source evidence and limits. Use a concise artifact when the user wants to apply the ideas, rather than substituting a generic summary of the talk.
.tessl-plugin
skills
talk-arcolano-autonomy-and-trust
talk-aroussi-decision-context
talk-bevin-agent-assisted-instrument-design
talk-boeckeler-context-lifecycles
talk-braun-context-graphs
talk-carmont-evolving-agent-harnesses
talk-chanezon-gordon-agent-experience-evaluation
talk-cox-secure-agentic-workflows
talk-cunniffe-reusable-agent-platform
talk-davis-agent-tool-policies
talk-debois-concurrent-delivery
talk-dzialets-team-automation
talk-fahmy-harness-api-design
talk-finster-continuous-delivery
talk-fowler-regenerative-software
talk-gavrilescu-factory-architecture
talk-graciolli-amin-verification-aware-programming
talk-gruenbaum-reverse-graph-engineering
talk-hassan-agentic-engineering
talk-hossain-enterprise-agent-adoption
talk-huntley-patch-ready-factories
talk-jain-verifying-intent
talk-katsioloudes-montei-agentic-lifecycle
talk-knox-harness-engineering
talk-kovac-deterministic-memory
talk-lee-perkins-code-readiness
talk-lorenc-machine-speed-security
talk-lubken-software-of-one
talk-meijer-software-specialization
talk-meppiel-versioned-agent-contracts
talk-moss-concurrent-agent-risk
talk-myers-understanding-agent-generated-code
talk-ocytko-scaling-agentic-engineering
talk-oza-automating-design-quality
talk-panzica-agentic-sdlc
talk-pari-patel-agent-awareness
talk-podjarny-trustworthy-software-factories
talk-poulter-factory-improvement
talk-pratik-patel-refined-rag-data
talk-re-ferre-development-platforms
talk-sadogursky-factory-of-factories
talk-shah-training-agent-skills
talk-sharma-mohapatra-evolving-intent
talk-singhal-operating-agents-at-scale
talk-stack-incident-dossiers
talk-tyler-team-coding-benchmarks
talk-wotherspoon-agent-execution-environments
talk-yegge-ai-powered-factories
talk-zuber-leadership-through-coding