SKILL.md
Install WTA
WTA is a Rust binary CLI distributed as source on GitHub. There is no crates.io publish or prebuilt binary today, so installation always goes through cargo build.
Prerequisites
Confirm the user has these before continuing. If any are missing, stop and explain what to install:
cargoandrustc(Rust 1.70 or newer). Check withrustc --version.gitwith SSH or HTTPS access to GitHub.- A Unix-like shell. WTA is tested on macOS and Linux.
Verify the cargo bin directory is on PATH:
echo "$PATH" | tr ':' '\n' | grep -F "$HOME/.cargo/bin"
If the output is empty, instruct the user to add ~/.cargo/bin to their shell rc file (.zshrc, .bashrc, etc.) and re-source it before continuing.
Steps
- Clone the public WTA source:
``sh git clone https://github.com/langgenius/wta-workflow.git cd wta-workflow ``
- Build and install with
cargo install:
``sh cargo install --path . --locked ``
This compiles WTA in release mode and copies the resulting binary to ~/.cargo/bin/wta.
- Verify the install:
``sh wta --help ``
The output should list the WTA top-level commands (init, doctor, info, board, intent, task, release, ...). If wta is not found, return to the prerequisites step and check PATH.
Upgrading later
To upgrade to the latest commit:
cd /path/to/wta-workflow
git pull --ff-only
cargo install --path . --locked --force
Common failures
error: rustc 1.x is not supported— runrustup update stable.error: failed to run custom build command— usually a missing
system dependency (pkg-config, libssl-dev on Debian, etc.). Read the error and install the named library.
wta: command not foundafter install — the cargo bin
directory is not on PATH. Re-read the cargo install output for the exact install location.
Permission denied (publickey)when cloning — use HTTPS instead
of SSH for the clone, or run ssh-add to load the user's key.
After install
WTA is now available as wta. The next step depends on the user's goal:
- To start operating an existing WTA project or set up a new one,
load the wta-using-wta skill.
- To create a new WTA project from scratch, run
wta init --project NAME --ssh-host HOST inside an empty directory. Setup commands are dry-run/plan by default and apply only with --apply. Run wta next once a project is bound to see what to do.