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 recommended design artifact based on Knox's talk, not an automation to execute.
Observed signal: Choose cost per PR, review rounds, merge time, volume or a directly observed failure. Record the actual baseline, comparison period and task mix. Mark missing measurements.
Supporting examples: Include representative trace excerpts, comments or CI failures. Distinguish the observed symptom from the suspected cause.
Category: Agent access/tooling, architecture, repetition, test quality or CI capacity. Explain why that category fits better than the alternatives.
Input: Name the evidence the loop can read and its existing access boundary.
Analysis: State the pattern it should identify. For example, repeated malformed calls to the same issue-tracker operation may suggest a small validated wrapper rather than more prose.
Output: Choose a recommendation, issue or reviewable change. Define the intended consumer and preserve the existing merge policy.
Cadence and budget: Select a schedule appropriate to the evidence rate and cost. These are proposed settings, not numbers mandated by the talk.
Describe one representative fresh task and the failure the change should prevent. Record outcome, retries, relevant cost and verification quality. If a test or CI change is proposed, explain what meaningful coverage remains and what moves to another execution bucket.
For architectural signals, inspect before splitting: a large file or weakly connected cluster is a reason to investigate, not automatic proof of bad design.
State when to keep, revise or stop the loop, including repeated failures, noisy suggestions or rising cost without better outcomes.
Next action: Identify one concrete change and the evidence still required. Keep planned evaluations separate from completed results; do not claim improvement until the task has been observed after the change.
.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