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
This is a Tessl adaptation of Singhal’s operating approach. Use it for one decision about a specific setup. Fill missing evidence with “unknown”; do not replace it with an assumed improvement.
Define adoption as access, setup, recent use, and retained use with explicit denominators and dates. Define delivery outcomes separately: merged work, follow-up changes, reverts, and cost per merged change. Choose an observation window suitable for those delayed outcomes.
List tokens, sessions, requests, tool calls, and cache behavior only as diagnostic signals. Explain how rising activity could indicate either useful work or retries.
| Checkpoint | Required evidence | Observed result | Remaining blind spot |
|---|---|---|---|
| Gateway | Version-tagged cost, latency, errors, identity | Agent behavior | |
| Traces | Common event structure, timings, retries | Alternative setup performance | |
| Internal evaluations | Pinned code, real tasks, repeated runs, graded explanations | Unrepresented real work | |
| Small rollout | Baseline comparison, cohort, observation period | Delayed outcomes |
Record any additional data collection separately from the structure-and-timing approach described in the talk. Do not assume prompt or code collection is necessary.
For each task, inspect tests, intended patterns in the diff, agent actions, and judge explanation. Record individual regressions and repeated-run variation even when average quality is unchanged. Examine cache reuse and whether the candidate overrides existing model choices.
State retain, investigate, trial, expand, or revert; cite the supporting evidence and what is still pending. Identify the existing owner for configuration, approved models, vetted tools, and merge controls. Specify the prior version, rollback trigger, observation owner, and next review date. Distinguish this proposed decision from any action actually taken.
.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