https://chatgpt.com/share/6a079b4e-29c4-83eb-a708-51f401e75268
https://osf.io/ae8cy/files/osfstorage/69ffbfc888878a0f3e78fda2
Portable Agent Skills as Interface Contracts
A Technical Specification Method for Cross-Platform AI Skill Design
Part 1 — From Prompt Templates to Skill Interface Engineering
Abstract
Modern AI development is moving from simple prompt usage toward reusable Agent Skills: structured capabilities that can analyze documents, operate tools, manage workflows, transform code, audit outputs, call external systems, and coordinate multi-stage reasoning. Yet complex Agent Skills are difficult to standardize because every platform has different assumptions about tools, memory, state, file access, orchestration, human approval, safety policy, and execution semantics.
The common mistake is to treat an Agent Skill as if it were only a better prompt template. This works for simple tasks such as summarization, rewriting, classification, or extraction. It fails for complex tasks that require multiple stages, intermediate artifacts, validation gates, audit traces, residual handling, and adaptation across different AI runtimes.
This article proposes a different approach:
A portable Agent Skill is not a universal prompt template; it is a declared interface contract whose invariant logic can survive platform-specific implementation. (0.1)
A Technical Skill Specification is the human-readable and machine-adaptable document that defines this interface contract. It declares the skill’s purpose, non-purpose, input artifacts, output artifacts, runtime assumptions, pipeline stages, gates, tools, state policy, trace policy, residual audit, platform adapter mapping, test harness, failure modes, and revision rules.
The deeper conceptual foundation comes from Philosophical Interface Engineering, where an interface is understood as boundary, observables, gate, trace, residual, invariance, and revision. In that framework, a system becomes usable when its world of operation is declared clearly enough to be inspected, tested, corrected, and transferred.
This article applies that principle to AI engineering. It argues that the next stage of Agent Skill design is not merely prompt engineering, nor even workflow engineering, but Skill Interface Engineering.
Prompt Engineering → Workflow Engineering → Skill Interface Engineering. (0.2)
The result is a practical specification method for building Agent Skills that are portable, auditable, testable, residual-honest, and adaptable across platforms such as Codex-style Skills, Claude-style Skills, OpenAI Agents SDK workflows, LangGraph graphs, CrewAI processes, AutoGen conversations, MCP tool layers, A2A agent networks, and custom local LLM harnesses.
0. Reader’s Guide: What This Article Is and Is Not
This article is written for AI engineers, agent framework designers, prompt engineers, technical writers, workflow architects, enterprise AI teams, and researchers interested in making complex AI capabilities reusable across platforms.
It is also written for people who sense that “prompt templates” are no longer enough.
A simple prompt can tell an AI what to do once. A complex Agent Skill must define how a class of tasks should be handled repeatedly, safely, inspectably, and adaptably.
This article is therefore about the missing middle layer between:
loose prompt
and:
full software implementation
That missing layer is the Technical Skill Specification.
.png)
.png)
.png)
.png)
.png)
.png)
.png)