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 Podjarny's talk. Complete it for one bounded outcome before composing a larger factory.
State what the user wants, why it matters, and what observable evidence would count as success. Record inputs, deliverable, reusable guidance, and task-specific assumptions. Separate the skill from the environment and event that will run it.
Describe required tools, data access, execution environment, budget, and stopping behavior. List actions the task permits and plausible ways unrelated source content could redirect the agent. Treat a review comment or CRM field as evidence, not authority to broaden scope.
For each important boundary, specify the enforcing mechanism or verifier. Distinguish a model's judgment from a hard access restriction. Record missing evidence and the appropriate next step.
| Question | Check | Artifact or trace | Actual result |
|---|
For vulnerability remediation, keep “defect fixed” and “required application behavior preserved” as separate questions. Record review and merge status separately from either verification result. A merged change is not proof that every security property holds.
Describe the proposed trigger, run identity, output artifact, telemetry, and feedback source. A plan does not activate a routine. State how failed runs become improvement hypotheses and where changes to the skill, environment, or trigger are recorded.
Choose representative cases for comparing a proposed improvement and a rollback condition if quality deteriorates. Define correct behavior before lowering model cost or shortening execution.
Name adjacent loops, shared components, operational owner, and the business outcome they jointly support. Explain what an operator sees when work is running, failing, or needs a decision.
Finish with the smallest useful experiment and its unresolved assumptions. Use the team's actual costs and results; keep speaker anecdotes and third-party benchmark claims separate from this workflow's evidence.
.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