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
Agents encounter a product through documentation, examples, tools, diagnostics, and their execution environment. Use Patrick Chanezon and Jay Gordon's approach to discover whether those inputs help an agent choose a product and use it correctly, then turn observed failures into testable improvements.
This is Tessl's adaptation of the talk, not Microsoft's official Scope playbook or a Cosmos DB implementation guide. It provides reasoning and planning context; it does not install Scope or execute experiments automatically.
https://www.youtube.com/watch?v=I81RrZcQaT8&t=SECONDS. Quote only words actually present in the transcript; use paraphrases when transcription is awkward.If a bundled reference is unavailable, identify the missing file and limit source claims accordingly.
Use the distinction at 05:54–06:59 and 21:45–22:49:
Keep these results separate. Better implementation is not evidence of increased preference, and a higher selection rate does not establish correctness.
When asked for a plan, use the evaluation template, adapting its detail to the request. Make a concrete draft with explicit assumptions; ask only for missing information that prevents a useful plan.
Produce a plan rather than provisioning infrastructure or launching paid runs unless the user has requested execution. If execution is requested, use the user's available environment and current tool documentation; do not fabricate Scope syntax.
Read the material supplied by the user and return a short table with finding, evidence, consequence, proposed change, verification. Use these lenses from the talk:
Do not invent findings when the user has supplied only a description. Identify hypotheses to inspect and the smallest evidence needed to resolve them. Do not turn the talk's workload-specific Cosmos DB choices into universal database rules.
Answer with the practical implication first, followed by the evidence and its limits. Use connected prose and useful artifacts rather than a generic talk summary when the user wants help doing the work.
.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