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-zuber-leadership-through-coding/references/

Leadership learning experiment

This worksheet is a recommended application of Zuber's talk, not a mandate to code.

Decision to improve

State the company, product or operating decision at stake. Explain why direct participation could reveal evidence that current reports do not provide.

Name the alternative use of the leader's time and why this experiment is worthwhile now. Record the peers or team members whose context should inform that choice.

Representative work

Choose one real task and include its review, verification and delivery path. Define a bounded time or effort allocation appropriate to the organization.

Clarify who owns the work, how existing commitments are protected and whether the result is a learning prototype or a maintained deliverable.

Observation record

ObservationEvidenceImplicationAlternative explanation
Actual friction or resultTrace, task outcome or discussionDecision it may affectWhat remains uncertain

Track waits and rework as well as generated output. Treat token spend and PR count as prompts for investigation rather than performance rankings.

Adoption conversation

Ask what people believe they are measured on, where experimentation time comes from and which support would reduce friction. Include both hesitant users and enthusiastic people constrained by current assignments.

Draft one concrete question and state how feedback will be acted on. Avoid equating a different preference with resistance.

Decision and follow-through

Choose one change, its accountable owner and the evidence that would validate it. Separate a prototype's success from customer delivery or broad adoption.

Record what the leader learned, what remains unknown and when the experiment ends or is revisited. If the result is not worth maintaining, state that explicitly without transferring surprise ownership to the team.

Finish with a decision-ready recommendation, not a claim that hands-on activity alone is strategic impact.

skills

talk-zuber-leadership-through-coding

tile.json