runtype-templateslisted

# Runtype Templates Use this skill when a Runtype product should become a portable artifact that another workspace, team, customer, or marketplace user can import. ## Source Of Truth When MCP is available, fetch current schema docs before writing or validating templates: - `get_platform_documentation(topic="product-schema")` - `get_platform_documentation(topic="types-fpo")` - `get_platform_documentation(topic="surface-types")` - `get_platform_documentation(topic="flow-step-types")` - `get_platform_documentation(topic="builtin-tools")` - `get_platform_documentation(topic="orthogonal-tools")` - `get_platform_documentation(topic="external-tools")` - Direct resource when available: `runtype://types/fpo-template` - Direct resource when available: `runtype://types/surface-configs` Prefer the live MCP docs over this skill's local fallback references. ## Template Shape An FPO template wraps a product object and import-time variables: - `productObject`: the full product definition. - `template.variables`: non-secret values the importer supplies. - Tool `auth.setupRequired: true` plus `auth.secrets[]`: pending-secret declarations. Template variables are for names, public URLs, recipient lists, selected models, and other non-secret configuration. Credentials must use the pending-secret pattern. ## Pending Secrets Use this pattern for every credential: 1. Declare the needed key on the target tool's `auth.secrets` array. 2. Set `auth.setupRequired: true`. 3. Reference the key