CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

ainativedev/aidevcon-2026-nyc

AI Native DevCon 2026 New York — practical agent skills grounded in conference talks

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

application-template.mdskills/talk-graciolli-amin-verification-aware-programming/references/

Verification boundary and contract record

This is a recommended application of the joint talk, not executable LemmaScript.

Intended behavior

Feature: Describe the real user outcome and a representative input.

Properties: State each invariant or postcondition in plain language. Separate a property required by the user from an implementation choice.

Assumptions: List preconditions, permitted input domains and environmental assumptions. Explain how an unverified caller establishes them.

Contract decisions

PropertyReasonFrozen or changeableEvidence required
Fill from actual requirementsIntended behavior protectedDecision with rationaleMechanical check and scope

For a splitting feature, conservation of the total is distinct from the allocation of remainders, fairness, input validation and actual payment effects. Do not mark an omitted property as implicitly verified.

Architecture

Pure core: Identify state, initializers and transitions covered by verification.

Invariant boundary: List all ways state can be created or changed. Mark any unverified code that can bypass the intended path.

Effects: Describe UI/API adapters and, if useful, commands represented as data. State what the interpreter does and which parts remain trusted or separately tested.

Candidate loop

Record the candidate artifact, unchanged contracts, verifier verdict, failed obligations and next candidate. Keep an agent's narrative separate from actual mechanical output.

Acceptance statement: “This artifact satisfies [properties] under [assumptions] within [boundary].” Leave unknown fields visible; do not invent proof results.

Evolution and review

For a proposed contract change, identify the changed requirement, rationale, lost guarantees and necessary new checks. Reject weakening that merely hides a failure.

End with the supported guarantee, unverified integration behavior, and the smallest next evidence needed. A valid contract proof does not by itself establish that the contract fully captures user intent.

skills

talk-graciolli-amin-verification-aware-programming

tile.json