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
Use this worksheet for one workflow before increasing parallel execution. It is a Tessl adaptation, not the queue or budget implementation described by Moss.
Logical work item: Ticket and version: Repository and base revision: Implementation, review, and orchestration actors: Authorized actions and existing merge policy: External systems that record progress:
Draw or describe the transitions between requested, claimed, running, reviewable, completed, failed, and retrying states as appropriate. State which records are authoritative and where disagreement could occur.
| Risk | Concrete probe | Expected response | Evidence |
|---|---|---|---|
| Shared state | Two separate tickets modify one generated history file | ||
| Staleness | Another valid feature lands before rebase | ||
| Convergence | The same concern returns in different wording | ||
| Duplication | Two workers receive one event concurrently | ||
| Budget | An agent comments through a human identity |
Adapt the probes to the real system; do not claim they have run. For shared state, name the correct owner and whether work should be staged. For staleness, identify the old and new behavior that must both survive.
Work-item identifier: How ownership is claimed: What prevents duplicate external effects: How a crashed worker's partial output is reconciled: How repeated findings are recognized: What constitutes meaningful review progress: Cost sources counted across workers: Budget and elapsed-time limits: Stop, preserve-evidence, and continuation behavior:
Treat numeric limits as project choices. Record the reason for each and who can intentionally continue the work. Do not interpret an ordinary comment as unlimited fresh authorization.
Observed weakness: Proposed smallest control: Validation plan: Remaining uncertainty: Scope suitable for the next bounded trial:
Separate reported incidents, inspected local findings, and proposed controls. A clean merge or a green test alone does not show that another feature survived.
.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