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 applies Meijer's thesis; its validation requirements are implementation recommendations.
Problem the user needs solved: Existing general-purpose component: Smallest useful subset to investigate: Explicitly excluded behavior: Who or what depends on compatibility:
Describe success in terms of the user's outcome. Avoid defining success solely as removing a library. Identify behavior that is easy to overlook, such as error handling, data persistence, or platform differences, when it actually applies.
| Input or assumption | Evidence it is stable | Remaining variability | Invalidation condition |
|---|---|---|---|
Write the intended relationship in plain language: with the chosen static value, the specialized component should behave like the baseline for all supported dynamic inputs. Mark unproven assumptions.
Baseline implementation and version: Candidate artifact: Supported input domain: Expected outputs and side effects: Normal cases: Boundary and invalid cases: Out-of-domain rejection or fallback: How equivalent behavior will be assessed:
Record tests as planned until they have actually run. A successful demonstration on one input does not establish equivalence across the domain. For a model example, distinguish retained-task accuracy from simply reducing the number of output labels.
Measure correctness first, then relevant resource use. Record generation effort, runtime, memory, footprint, and maintenance responsibility as appropriate. Compare like-for-like workloads and disclose gaps.
Baseline results: Candidate results: Unresolved behavior: Dependency updates that require regeneration: Rollback or fallback path: Decision and evidence needed for the next step:
Keep rights and permissions as a separate unresolved input when reuse is involved. The talk's legal discussion cannot settle them. Drafting this experiment does not authorize copying assets, removing dependencies, or deploying changes.
.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