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-fahmy-harness-api-design/references/

Harness and workspace API decision

This worksheet is a recommended application of Fahmy's design lessons. It is not executable SDK documentation.

Workflow obligation

Task: Describe the tool being built and what must happen deterministically.

Model judgment: Identify where an agent may choose an approach and where every input must be processed.

Coverage record: State how scheduled, completed, failed and unprocessed items are distinguished. Invoking a harness does not prove its analysis is correct.

Responsibility split

Harness: List required invocation, progress, steering, interruption, completion and error behavior.

Workspace: List files, history, settings, skills and integrations needed for the task. Separate portable content from machine-specific configuration and credential references.

For each operation, name the owner and the evidence that it succeeded. Leave API names conceptual until the actual library is inspected.

Adapter capabilities

RequirementHarness AHarness BUnsupported-case behavior
Fill from the workflowVerified, unknown or absentVerified, unknown or absentExplicit fallback or stop

Include child-process cleanup, approval semantics and error channels if relevant. Preserve meaningful differences rather than hiding them in a generic success string.

Handoff contract

Record the source and destination environment, files copied, history exported, configuration restored and state deliberately omitted.

State that message-history portability is different from transferring a model's exact effective context or hidden reasoning. Identify missing dependencies before calling a session resumable.

Validation and decision

Propose one representative local-to-remote task and one failure case. Check output integrity, coverage, observable errors, cleanup and permission boundaries.

Decision: Adopt the minimum surface needed, list unsupported scenarios and define when broader abstraction would be justified. Mark all tests as planned until performed; do not claim universal harness compatibility from a single successful handoff.

skills

talk-fahmy-harness-api-design

tile.json