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 Tessl's recommended application of Poulter's talk. Complete it before promoting a change to reusable instructions, evaluation, orchestration, or runtime behavior.
Describe the triggering failure and link its actual artifacts or traces. State the reusable unit being changed, intended gain, and plausible downside. Keep the product fix distinct from the proposed factory improvement.
Record inputs, resolved instruction version, model, effort, tools, environment, output contract, and grading method. Explain what can be replayed and what remains variable.
Choose a local comparison with and without the change. State repetitions and why they are sufficient for the decision; the talk's ten is an example. Choose a regression set representing ordinary work and important edge cases beyond the original incident.
| Case group | Quality | Cost | Latency | Failure or regression | Evidence |
|---|
Leave results blank until measured. Include uncertainty and trace inspection where aggregate scores conceal different behavior.
Define acceptable gains and tolerable losses before deciding. Record the process version to promote, evidence retained, observation period, and rollback condition. A local success with missing regression evidence remains a provisional result.
If the change concerns infrastructure, map model loop, tools, source checkpoints, and code execution separately. Identify isolation, credentials, state ownership, and execution sizing. Compare startup, resource use, and added operational complexity; do not assume that moving tools removes security obligations.
If the change selects tests from a symbol graph, record known coverage gaps and how selective checks will be compared with a broader reference run.
Finish with promote, revise, reject, or gather more evidence. State the strongest evidence, the largest unresolved downside, and the next smallest experiment. Use actual workload measurements instead of copying the talk's reported costs or timings.
.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