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 worksheet is a Tessl adaptation of Hossain’s prepare, practice, sustain and improvement discussion. Complete it for one cohort using observed conditions; unknown entries are work to resolve, not evidence of readiness.
Separate purchased seats and session attendance from accepted work. Record the baseline only if it is available.
| Track | Owner | Existing permitted path or decision | Open issue | Next action |
|---|---|---|---|---|
| Security and governance | ||||
| Technical readiness | ||||
| People and enablement |
For each restriction, record its documented origin and the person able to interpret it. If a smaller approved scope is viable, state the exact cohort, data, and tools it covers. Do not describe an unapproved workaround as readiness.
Use a representative account. Record invitations, license, login, repository access, task data, plugins, MCP or other integrations, and review permissions as passed, blocked, or unknown. Name the owner of each blocker. Include one check that the artifact can be inspected by the intended reviewer.
Describe the short demonstration, participant exercise, expected intermediate observations, and how confusion or failures will be captured. Identify local champions, including administrators or platform owners where useful.
Before the session ends, assign a real next task, a support contact or channel already available to the cohort, and a check-in date. State who will inspect results and what evidence they need.
At the check-in, compare expected and observed access, task results, review quality, and unresolved questions. Choose one change to the experience, its owner, and a review date. Record whether it improves preparation, practice, or sustained support. Keep any claimed business impact separate until the organization supplies 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