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
Use this worksheet to define behavior before implementing an assistant. It is an adaptation of the talk's examples.
User outcome: Legacy intent and fallback: Read-only capabilities: Consequential capabilities: Required arguments: Existing authorization: Unsupported requests:
Describe what the tool does independently of the phrases that might invoke it. Name effects on money, external records, or people when relevant.
Current intended action: Known arguments and their evidence: Ambiguous references: Superseded values: Dependent information now invalid: External action already completed:
For the flight example, a corrected airport may invalidate route, departure time, and price. Keep the old value only as history, not as an equally valid current destination.
| Tool | Inputs | Result | Side effect | Execution boundary |
|---|---|---|---|---|
What is shown before a required confirmation: What counts as approval of these arguments: Behavior on denial: Behavior on a material correction: Behavior if confirmation expires: Behavior on tool error or uncertain completion: Recovery if cancellation arrives after commitment:
Use conceptual behavior rather than inventing an interrupt API. Respect existing authorization for routine steps.
For each case, record expected action, arguments, non-action, state transition, and evidence. Choose project-specific turn and latency budgets.
Behavior sufficiently specified: Unresolved tool semantics: Persistence and recovery requirements: Verification needed: Smallest next implementation step:
Do not mark the flow validated until these cases have actually been exercised against the intended implementation.
.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