Skills

Every module in this repository carries a skill/ directory, and the wizard copies the ones you picked into the skills directory of the coding agent you picked — chatfuel-deals, chatfuel-contacts, one per module. Each holds that module's structure, the GraphQL operations it uses and the traps in the API behind it.

The thirteen skills

core is installed on every run and has no interface of its own. It is also implicit in every module's dependencies, which is why no manifest lists it: everything else builds on its transport, its proxy spec, its bundled schema and its validator, and every other skill's description says so.

The two opt-in skills are offered in the picker and never installed by --yes, because both modules need credentials the wizard cannot invent. Name them to get them.

Two layouts, one tree

Neither CLI reads the other's skills directory, so the layout follows whichever agent is going to open the app. --agent claude or --agent codex settles it before anything is copied.

Only one layout is ever written. Copying both would leave two trees to drift apart instead of one to maintain, so the skills are moved rather than duplicated in the single case that needs it: a run that started with no agent on PATH at all, wrote Claude's layout for want of a better guess, and then had you accept the Codex install at the handoff. The move takes the vacated directories with it, but only while they are empty — a global ~/.claude holds more than ours.

Project, or your home directory

The wizard asks where the skills go, in the same layout either way: into the scaffolded project, or into your home directory, which is worth it when you plan to scaffold more than one app and want one copy of the notes. Under --yes it takes the project without asking.

What a skill directory holds

SKILL.md is the entry point every agent reads first, and it carries a table of what sits beside it, so nothing in the directory is found by guesswork.

The sidecar

Beside every copy the wizard writes chatfuel.skill.json, and it holds three things:

interface SkillSidecar {
  module: string;
  wizardVersion: string;
  installedAt: string;
}

That is what lets a later run tell its own installs apart from a directory you wrote yourself. On the second run the wizard reads it back and asks by name, quoting the wizard version that put the skill there, when it did it, and the version about to replace it. A directory with no sidecar gets the blunter question, because it was not ours to begin with. Decline either and that one skill is skipped; the rest of the run continues.