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 a scenario design template adapted from Gruenbaum's talk. It describes a future test until execution evidence is attached.
Domain expert's question: Expected answer: Required facts and relationships: Time at which the answer is valid: Deterministic derivation: Correct response when evidence is absent: Information withheld from the agent:
Choose a question that exposes a real reasoning or retrieval failure. Keep the oracle outside the agent-visible data.
Entities and identifiers: Relationships: Authoritative records: Historical records: Distractors: Cross-system identity mapping:
Build the smallest sufficient company. Add scale only when the evaluation requires it.
| Mutation | Record affected | Reason for realism | Oracle impact | Expected agent behavior |
|---|---|---|---|---|
| Alias or duplicate | ||||
| Stale or conflicting record | ||||
| Missing link or migration |
If a mutation makes the answer genuinely ambiguous, change the expected response accordingly. Do not punish appropriate uncertainty.
Documents and tables: Service or protocol views: Pagination and update behavior: Fault cases: Supported operations: Unsupported operations: Permission assumptions:
State the tested subset. A local twin is not the full external service.
Answer still derivable: Temporal and identity invariants: Distribution or shape checks: Realism review: Scenario and grader versions: Generation seed or recorded choices: Cached artifacts: Held-out scenarios: Trace and score location:
Keep deterministic correctness, perceived realism, and representativeness distinct.
Failure stage: Evidence from execution: Smallest agent or data-pipeline change: Regression case: Remaining real-world gap:
Do not infer production readiness from a synthetic pass. Record the limits that the next evaluation must address.
.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