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-huntley-patch-ready-factories/references/

Patch-readiness worksheet

This is Tessl's recommended application of Huntley's talk. Fill it for one dependency and one failure. Unknown versions, results, or owners remain unknown.

Repair target

Describe the affected behavior and the evidence that the dependency participates in it. List direct consumers and transitive consumers separately. Record the version and source actually resolved in each environment, including local modifications. Do not treat a manifest entry as proof that production uses that build.

Environment map

SurfaceDefinition and resolved inputsIntentional differencesEvidence of parity
Developer machine
CI
Agent sandbox
Production artifact

Explain where drift can occur. Identify which common definition could produce all four outputs and what remains specific to each environment.

Patch lifecycle

State the chosen option: upstream update, local patch, vendored component, or narrowly scoped replacement. Give the reason and ongoing maintenance owner. Describe the required behavioral change without inventing a runnable Nix command.

List consumers that must be rebuilt, validation inputs, resulting artifact identity, and distribution route. Define one regression check for the defect and one compatibility check for an affected consumer. These check categories are suggestions, not claims that the speaker ran them.

Enforcement and feedback

Identify one action the agent should be unable to perform. Record the enforcing mechanism, alternate paths that need inspection, and the test that would demonstrate the restriction. A patched Git binary alone is not evidence that credentials cannot force-push through another route.

State one system invariant suitable for property-based exploration and the counterexample needed to reproduce a failure. Separate unit, architecture, and infrastructure checks.

Retirement and decision

Record the upstream correction to watch, review date, removal criteria, and rollback condition. Seven days is an anecdotal reminder interval, not an expiry policy. Finish with the evidence needed before adopting or retiring this patch, and keep production access outside the experiment unless separately authorized.

skills

talk-huntley-patch-ready-factories

tile.json