Get started with an agent

You do not have to learn the YAML or the CLI first. Every stage of the journey has an agent skill behind it, and your agent (Claude Code, Codex, or anything that reads SKILL.md files) uses wfx through those skills.

Stage	Skill	Status	What it does	Ask your agent
Install	wfnexus-setup	available	Brings wfx-server up (docker compose), installs the CLI and the skills, and checks the wiring with wfx doctor.	“set up wfnexus on this machine”
Build	workflow-author	available	Turns the work you describe into a workflow: it interviews you, drafts the YAML, proves it with wfx dryrun and installs it with wfx apply.	“automate this as a wfnexus workflow”
Deploy	wfnexus-deploy	available	Puts the workflow where it will run: wfx apply on a server, or wfx publish to a host or a git registry.	“deploy this workflow”
Run and approve	approval-desk	available	Shows which runs are waiting on a human, and approves, rejects or answers them (wfx approve, wfx reject, wfx answer).	“what is waiting on me?”

Status is read from the repository

A skill is marked coming when skills/<name>/SKILL.md does not exist on main. The table is rebuilt on every deploy, so a skill changes to available once it lands. Until then, follow the Quickstart for install, and use wfx apply or wfx publish for deploy (see the CLI reference).

Put the skills where your agent looks

wfx install --skills       # every skill into ~/.claude and ~/.agents

After that, ask in plain words. “Take my Friday release-notes chore off my plate” starts the build stage. “What is waiting on me?” starts approval. The Demo video shows the build, run and approve stages in a real session.

See Agent skills for how the skills use wfx, and the skill catalogue for every skill that ships.