prompt-engineering

A portable prompt is an agent-agnostic instruction file with standardized frontmatter and semantic Markdown structure. It ensures your reusable workflows, policies, and instructions load consistently across multiple agent products without requiring migration rewrites.

To create a SKILL.md file, structure it with required frontmatter like name and description, use semantically formatted Markdown for the body, and define explicit load conditions for optional supporting files like references, assets, and scripts to keep the main artifact lean.

You set explicit load conditions for references and scripts within the semantic Markdown body of your SKILL.md. This ensures optional supporting files are fetched only when needed, keeping the core prompt lean and efficient for the agent.

Use portable prompts when creating reusable workflows and policies that need clear trigger boundaries and must survive agent migrations. Standardizing them as SKILL.md files guarantees they load consistently across multiple agent products.

The best way to structure an agent-agnostic prompt file is using semantic Markdown sections with clear trigger boundaries. Include frontmatter for metadata, keep the core guidance lean, and separate optional assets or scripts into supporting files loaded on demand.

Yes, you can attach references, assets, and scripts to your portable prompt. By defining explicit load conditions in the SKILL.md file, these supporting documents are only loaded when the agent specifically needs them, preserving performance.