How do I install the Wta Install skill?

Run npx skillmds@latest add langgenius/wta-install 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 Wta Install 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 Wta Install?

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 Wta Install free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Wta Install?

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

Wta Install by langgenius — Agent Skill

Name: Wta Install
Author: langgenius

Wta Install

Install the WTA Rust CLI from source. Clone the public repository, build with cargo, and place the wta binary on PATH. Use when the user wants to start using WTA but does not yet have the wta binary installed, or wants to upgrade to the latest commit on main.

langgenius e53c2e6 2.8 KB Updated Sep 17, 2026

File contents

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:

cargo and rustc (Rust 1.70 or newer). Check with rustc --version.
git with 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:

git clone https://github.com/langgenius/wta-workflow.git
cd wta-workflow

Build and install with cargo install:
```
cargo install --path . --locked
```
This compiles WTA in release mode and copies the resulting binary to ~/.cargo/bin/wta.
Verify the install:
```
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 — run rustup 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 found after 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.

---name: wta-installdescription: Install the WTA Rust CLI from source. Clone the public repository, build with cargo, and place the wta binary on PATH. Use when the user wants to start using WTA but does not yet have the wta binary installed, or wants to upgrade to the latest commit on main.license: MIT---# Install WTAWTA is a Rust binary CLI distributed as source on GitHub. There is nocrates.io publish or prebuilt binary today, so installation alwaysgoes through `cargo build`.## PrerequisitesConfirm the user has these before continuing. If any are missing,stop and explain what to install:- `cargo` and `rustc` (Rust 1.70 or newer). Check with `rustc --version`.- `git` with 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`:```shecho "$PATH" | tr ':' '\n' | grep -F "$HOME/.cargo/bin"```If the output is empty, instruct the user to add `~/.cargo/bin` totheir shell rc file (`.zshrc`, `.bashrc`, etc.) and re-source itbefore continuing.## Steps1. Clone the public WTA source: ```sh git clone https://github.com/langgenius/wta-workflow.git cd wta-workflow ```2. 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`.3. 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 laterTo upgrade to the latest commit:```shcd /path/to/wta-workflowgit pull --ff-onlycargo install --path . --locked --force```## Common failures- **`error: rustc 1.x is not supported`** — run `rustup 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 found` after 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 installWTA is now available as `wta`. The next step depends on the user'sgoal:- 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.

Frequently asked questions