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-sadogursky-factory-of-factories/references/

Approval-signal and evidence map

Use this worksheet for one release or change category. It adapts the talk's scenario to existing organizational authority.

Decision boundary

Change or work item: Existing release policy: Stakeholders actually needed: Actions already authorized: Decisions still unresolved:

Do not recreate the fictional organization's full structure if only a few decisions apply.

Signals

RoleMeaning of approvalEvidence sourceScope and freshnessMissing or failed behavior
Engineering
Security or operations
Finance or product
Other required owner

Tie every material signal to the relevant release, service, or work item. Distinguish a negative finding from unavailable evidence. Record conflicting records explicitly.

Authority and exceptions

Policy owner: Who may change controls: Who may grant the relevant exception: Exception scope and expiry: Decision rationale: Evidence retained: How the factory is prevented from expanding its own authority:

Specify the actual existing boundary. Do not add unnecessary approvals or infer that an agent's access to a tool authorizes policy changes.

Cost and continuation

Delivery unit: Usage attribution: Forecast and basis: Actual spend: Budget boundary: Behavior when exhausted: Remaining work estimate: Authorized continuation path:

Use differences between forecast and actual spending to improve the next estimate. Avoid treating token price alone as a project forecast.

Infrastructure choice

Signals already available: Missing connectors or associations: Permission and freshness gaps: Build effort: Existing-system option: Smallest testable workflow:

For each proposed integration, define the evidence that would demonstrate correct retrieval and access. Keep results unverified until observed.

Review outcome

Supported decisions: Decisions blocked by evidence: Recommended next step: Owner: Verification:

The artifact supports decisions; it does not certify compliance, grant permissions, or release software.

skills

talk-sadogursky-factory-of-factories

tile.json