How do I install the Slot Scaffolder skill?

Run npx skillmds@latest add openqa-cn/slot-scaffolder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Slot Scaffolder safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Slot Scaffolder?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Slot Scaffolder free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Slot Scaffolder?

openqa-cn (@openqa-cn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Slot Scaffolder by openqa-cn — Agent Skill

Name: Slot Scaffolder
Author: openqa-cn

File contents

Slot scaffolder

Bundled sub-skill of testdata-generation: turn an OpenAPI directory plus a domain name into a slot that matches ../slots/SLOT_SPEC.md, the single copy of that contract.

Inputs

domain and openapi are the prerequisite materials. If either is missing, or the OpenAPI directory has no .yaml / .yml / .json files, stop and ask. Do not invent operations or scaffold an empty slot. After the user provides them, generate the slot. Do not collect executor fields.

Field	Meaning	Required
`domain`	Short English slug (`payments`, `logistics`)	yes
`openapi`	Directory of OpenAPI YAML/JSON files (at least one spec)	yes
`output`	Destination directory (default `../slots/<domain>`)	no

Run

node scripts/scaffold_slot.ts \
  --domain <domain> \
  --openapi <openapi-dir> \
  --output <output-dir>

The script writes slot.yaml (the one config), executor stubs, generated SKILL.md / tools-guide.md, and copies OpenAPI into assets/openapi/.

Slots under ./slots/<domain> are discovered automatically. If the skill lives elsewhere, add one line:

workspace:
  slot_roots:
    - /path/to/company-slots

After generation

Implement each stub main(params) against DATA_BUILD_API_BASE (timeouts; never shell: true; missing required IDs must fail)
Add scenes (and optional aliases / invokeParams) in slot.yaml only. List more specific entities before generic ones
Refresh generated docs: node ../scripts/sync_slot.ts --dir <slot>
Hand-written SKILL.md is left alone unless it is generated-from: slot.yaml or you pass --force
Smoke-test: node ../scripts/search_data_build.ts --keywords <domain> --json

Do not add skill_marketplace.paths or api_catalog.paths. Search, OpenAPI index, and case-pipeline bind all read slots/ + workspace.slot_roots. If slot.yaml is omitted, entities are inferred from scripts/executors/* and assets/openapi operationIds.

Human operators: ../HOW_IT_WORKS.md. Agents stay on this file and ../slots/SLOT_SPEC.md.

---name: slot-scaffolderdescription: Generate a domain data-build slot from OpenAPI files: new business-domain pack, scaffold a data-build skill, or add an enterprise custom domain. Internal helper of the parent pack; reach this through testdata-generation.license: Apache-2.0---# Slot scaffolderBundled sub-skill of `testdata-generation`: turn an OpenAPI directory plus adomain name into a slot that matches [../slots/SLOT_SPEC.md](../slots/SLOT_SPEC.md),the single copy of that contract.## Inputs`domain` and `openapi` are the prerequisite **materials**. If either is missing, or the OpenAPI directory has no `.yaml` / `.yml` / `.json` files, **stop and ask**. Do not invent operations or scaffold an empty slot. After the user provides them, generate the slot. Do not collect executor fields.| Field | Meaning | Required ||---|---|---|| `domain` | Short English slug (`payments`, `logistics`) | yes || `openapi` | Directory of OpenAPI YAML/JSON files (at least one spec) | yes || `output` | Destination directory (default `../slots/<domain>`) | no |## Run```bashnode scripts/scaffold_slot.ts \ --domain <domain> \ --openapi <openapi-dir> \ --output <output-dir>```The script writes `slot.yaml` (the one config), executor stubs, generated `SKILL.md` / `tools-guide.md`, and copies OpenAPI into `assets/openapi/`.Slots under `./slots/<domain>` are discovered automatically. If the skill lives elsewhere, add one line:```yamlworkspace: slot_roots: - /path/to/company-slots```## After generation1. Implement each stub `main(params)` against `DATA_BUILD_API_BASE` (timeouts; never `shell: true`; missing required IDs must fail)2. Add `scenes` (and optional `aliases` / `invokeParams`) in `slot.yaml` only. List more specific entities before generic ones3. Refresh generated docs: `node ../scripts/sync_slot.ts --dir <slot>` Hand-written `SKILL.md` is left alone unless it is `generated-from: slot.yaml` or you pass `--force`4. Smoke-test: `node ../scripts/search_data_build.ts --keywords <domain> --json`Do **not** add `skill_marketplace.paths` or `api_catalog.paths`. Search, OpenAPI index, and case-pipeline bind all read `slots/` + `workspace.slot_roots`. If `slot.yaml` is omitted, entities are inferred from `scripts/executors/*` and `assets/openapi` operationIds.Human operators: [../HOW_IT_WORKS.md](../HOW_IT_WORKS.md#appendix-add-a-new-scene). Agents stay on this file and [../slots/SLOT_SPEC.md](../slots/SLOT_SPEC.md).

Frequently asked questions

Slot Scaffolder