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 adapts Braun's talk into a small design and evaluation artifact.
User task: Delivery stage: Question that local code cannot answer: Current failure or missing evidence: Expected useful outcome:
Choose a specific decision. A general ambition to collect more documents is not enough to evaluate whether the context layer helps.
| Source | Relevant evidence | Link to work or code | Owner | Freshness | Caller access |
|---|---|---|---|---|---|
Start with a few sources. Distinguish code ownership from organizational decision ownership. Mark uncertain relationships instead of drawing inferred edges as facts.
Job-oriented entry question: References needed first: Details fetched only after relevance is established: Evidence included in the final answer: Irrelevant context excluded: Conflict or stale-source behavior: Missing-evidence response: Permission restriction and intended audience:
Specify how the same task behaves when the caller cannot access one source. The correct result may be a partial answer with a clear gap, not a broader search through privileged material.
For each prompt, write expected facts and supporting sources before comparison. Keep current and connected runs comparable. Blind the evaluator to the condition when practical, then inspect material judgments.
Measures: Correctness and coverage: Source support: Irrelevant context: Time and tokens: Unresolved evaluation uncertainty:
Observed benefit: Observed failure: Smallest connection or retrieval change: Verification required: Expansion justified by evidence:
Leave results blank until runs exist. Avoid treating an illustrative demo or vendor-reported improvement as a local outcome.
.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