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-lubken-software-of-one/references/

Software-of-one brief and lifecycle decision

This is a recommended application of Lubken's talk, not a platform configuration.

One task

Owner and users: Name the person accountable for the app and who may use it.

Task: State one concrete workflow or decision. Explain why a small deterministic program, an agent or a combination fits.

Inputs and outputs: Identify the real source systems and the useful result. Keep the scope separate from replacing a whole CRM or ERP.

State and access

Persistent state: Describe what must survive compute suspension or replacement. Specify data retention and export needs.

Isolation: Identify what separates this app from neighboring apps and what sharing is intentional.

Backend capabilities: List the exact resources and operations needed. Record app identity, user identity and credential-brokering location separately.

Pending access: Describe how unavailable access is represented. Clearly mark any test or dummy data and avoid presenting it as a live business result.

Portfolio record

Capture usage, task success, owner, last maintenance, known defects, security-update needs and overlap with other apps.

Define a business-value signal suited to the task, such as time saved preparing a quote, while marking causal claims unproven until evaluated. Do not equate frequent use with value automatically.

Lifecycle decision

Choose keep, consolidate, rebuild or retire. State the evidence and a trigger for revisiting the decision.

For rebuilding, preserve the validated task and user learning while specifying data migration, handover and retirement of the old implementation. “Disposable code” does not mean disposable user data.

Operating assumptions

Estimate compute, storage, network, access-layer and maintenance costs separately using verified inputs when available. Mark unknowns rather than importing the talk's napkin estimate as a quote.

End with the smallest next app or platform change and planned validation. Do not claim the design is deployed, secure or free to operate.

skills

talk-lubken-software-of-one

tile.json