Slot scaffolder

SkillFiles & storage

Generates a ready-to-fill data-building template for a new business domain from your API definition files.

Use Slot scaffolder in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Slot scaffolder and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Slot scaffolder skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Slot scaffolderStart free
About this skill

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 codexqa-testdata-generator.

What this skill tells your AI

The instructions your AI receives, as published by openqa-cn/codexqa in skills/codexqa-testdata-generator/slot-scaffolder/SKILL.md and read by Ahel’s review.

Bundled sub-skill of codexqa-testdata-generator: 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.

FieldMeaningRequired
domainShort English slug (payments, logistics)yes
openapiDirectory of OpenAPI YAML/JSON files (at least one spec)yes
outputDestination 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

  1. 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 ones
  3. 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. Agents stay on this file and ../slots/SLOT_SPEC.md.

Signals

GitHub stars
101
Forks
2
Last commit
Oct 2026
Advanced
Item type
skill
Key
slot-scaffolder
Source
github.com/openqa-cn/codexqa