AI Native DevCon 2026 New York — practical agent skills grounded in conference talks
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
This worksheet is Tessl's recommended application of the talk. Field names and controls are design prompts, not an official agent-contract, APM, in-toto or other executable schema. Fill unknowns with explicit placeholders. Do not create fake hashes, signatures, run results or compliance claims.
| Field | Draft value |
|---|---|
| Factory purpose and owner | To define |
| Factory definition version and immutable digest | To resolve from the actual artifact |
| Contract graph and handoffs | For each edge: output artifact → next contract input |
| Input repository revision / assignment artifact | To pin for this run |
| Approved harness and runtime configuration | To verify against the chosen implementation |
| Resolved dependency inventory | Names, versions and digests of skills/tools; link to lock record |
Version the process, not just its generated code. The graph may include loops or other compositions appropriate to the task; the talk's linear demo is one example.
Stable role: What this unit of work is responsible for.
Per-run assignment: The specific change or question it is being asked to handle.
Inputs: Required intent/specification, repository state and other artifacts, with their identity and expected form.
Dependencies: Resolved skills, tools and other resources required to perform the role.
Budget: Cost, time or execution limits selected for this project; the talk does not mandate numerical thresholds.
Deliverables: Named output artifacts and the downstream consumer's expectations.
Required checks:
| Check | Exact definition/version | Relevant inputs and output | Executor and protection boundary | Required result and evidence |
|---|---|---|---|---|
| To specify | Immutable reference | What it actually verifies | Who runs it; why the implementing agent cannot replace it | Result plus verifiable evidence |
Use deterministic checks where appropriate, following the speaker's Q&A. A deterministic formatting check can establish format compliance; it cannot by itself establish that business behavior is correct. Select tests for the actual task.
| Evidence | What needs to be bound together |
|---|---|
| Output identity | The exact diff/artifact submitted for admission |
| Factory provenance | Factory version/digest and the contract steps that produced the output |
| Dependency inventory | Resolved dependencies used in this run, rather than declarations alone |
| Check integrity | Exact check definitions and their results, tied to the relevant output |
| Run context | Inputs and relevant environment identity needed to interpret or reuse results; added implementation recommendation |
| Attestation | Signer identity, evidence covered and verification method supported by the chosen implementation |
Keep the agent's execution authority separate from the authority that validates and signs its evidence. This is a recommended trust boundary; the talk's descriptions of the signer's deployment location conflict. Document who can change the checks, submit results, access signing credentials, and update policy. Verify those permissions rather than inferring isolation from machine names.
Specify the organization's rules for accepted factory identities, permitted dependencies, trusted signers, required checks, and the binding between evidence and the output under review.
| Condition | Recommended gate response |
|---|---|
| Missing or invalid signature / untrusted signer | Do not count the receipt as trusted evidence; route for investigation |
| Receipt refers to a different output or check definition | Reject the evidence for this output |
| Required check missing, failed or unverifiable | Do not admit as a passing run |
| Denied dependency or unapproved factory identity | Block admission under the specified policy |
| Evidence valid and all policy conditions satisfied | Mark this policy satisfied; apply any remaining release requirements |
These are suggested policy behaviors, not authorization to merge or deploy. A policy pass establishes satisfaction of that policy, not universal correctness or regulatory compliance. Preserve testing, scanning or review required by the actual project.
| Finding | Observed evidence | Consequence | Proposed control | Validation |
|---|---|---|---|---|
| Supported / missing / unverified | Exact supplied artifact or absent evidence | What remains uncertain | Smallest useful change | Concrete test or inspection |
Close with unresolved assumptions, the next design decision, and the evidence that would support it.
.tessl-plugin
skills
talk-boeckeler-context-lifecycles
talk-chanezon-gordon-agent-experience-evaluation
talk-meppiel-versioned-agent-contracts