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-lorenc-machine-speed-security/references/

Patch-to-production modernization worksheet

This is Tessl's recommended application of Lorenc's talk. Use it for defensive maintenance of a system the user is authorized to manage.

Dependency and flow

Record the dependency, resolved version, upstream project, transitive consumers, and running artifact. Map discovery, maintainer acceptance, release, packaging, application integration, validation, and deployment. Identify ownership, evidence, and waiting time at each stage.

Keep “patch available,” “release available,” “rebuilt,” and “running” separate. Mark missing evidence instead of assuming completion.

Upgrade plan

Choose a regular maintenance path or a specific incident response. Describe compatibility constraints and the operational reason for delay. For a large version gap, propose small steps with checkpoints and behavior comparisons. Record recovery for code, state, and external effects.

State whether the work repairs one defect or removes a recurring unsafe pattern. For modernization, define the dangerous capability and behavior a replacement must preserve. A language or library choice does not guarantee security.

Release-policy tradeoff

If using a cooldown, specify delayed-release risk, new-package risk, exception criteria, and transitive-dependency handling. Do not copy seven or fourteen days merely because those examples appear in the talk.

If copying or forking code, retain origin, version, modifications, update tracking, and a maintenance owner. Explain how future vulnerability information will reach the copied component.

Verification and decision

List evidence needed to confirm affected versions, migration correctness, deployment identity, and operational health. Use authoritative current advisories for live vulnerability claims; the transcript is not one.

Finish with the first bottleneck, proposed action, expected benefit, unmeasured cost, and expansion condition. Keep experiment results and speaker anecdotes separate from outcomes actually verified in this system.

skills

talk-lorenc-machine-speed-security

tile.json