Use the two Codex skills
Separate the skill that builds a SaaS from the skill that calls its API.
Choose the right skill
saas-launch builds an independent project from the mother template.
Install the building skill
In the mother template directory run npm run skill:install -- saas-launch, reopen Codex and follow the eight-requirement guide. The install records the mother template path; update that location if you move the directory.
Package your product skill
In the independent product run:
npm run sdk:build
npm run skill:packThe product package is public/downloads/product-skill.zip, with an <product.id>-api directory. The build skill archive is output/skills/saas-launch.zip. Source package and template versions should be reviewed together.
Install and call the API skill
Extract the product directory into the Codex skills directory, keeping its SKILL.md directly inside that directory. Reopen the session. Provide SAAS_API_URL and a scoped SAAS_API_KEY through secure environment configuration; do not put the key in a prompt.
The dependency-free CLI supports quota, create <kind> <prompt-file> <operation-key>, get <job-id>, wait <job-id> and download <job-id> <output-file>. Start with quota, use a short prompt, wait for success, then inspect the output. Downloads refuse to overwrite a file.
The source template installer accepts only saas-launch and cioy-api. Product-specific packaged names are installed by extracting their package. Public marketplace publication is a separate operator action; these local packages are not evidence of a published marketplace listing.
Ask the builder to finish launch setup
Use $ioy-saas (public builder) or $saas-launch (local template) and ask it to deploy on Cloudflare, bind the formal domain, configure Google login/One Tap, GA4 and Search Console, then connect the chosen payment provider. The builder follows a resumable sequence, checks existing resources before creation and gives specific instructions when the account holder is required. Template 1.3.1+ includes executable launch helpers; read the updated repository README and Skill orchestration reference. Keep all service keys out of prompts and requirements.