Prepare the CLI in the environment your agent uses

Verify a native CLI installation in the actual OS and terminal environment where the agent will run.

Keep agent skill installation, executable availability and account login as separate readiness steps.

Request TeamBoostAI access Get the work brief Task table (.csv)

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Give each stage an exit condition

Illustrative delivery gates

Illustrative case: a Windows CLI exists, but an agent runs in WSL and cannot resolve teamboost on its own PATH.

Identify the runtime

Owner role · Operator

Evidence: OS/CPU and the terminal used by the agent are confirmed.

Verify the supported artifact

Owner role · Operator

Evidence: The distribution checksum and runtime prerequisites are checked before installation.

Check local discovery

Owner role · Agent user

Evidence: Version/help resolve in that runtime; the full skill folder is discoverable separately.

Decision to make: Use the supported executable for the agent’s runtime and verify its command interface there.

Illustrative installation checklist

Invented planning text. Adapt it to your evidence and confirmed owners.

Agent runtime: confirm before choosing the archive.
Executable: supported TeamBoost distribution with matching checksum.
Skill: full folder including references, installed for that agent.
Session: normal browser-authenticated login, not copied credentials.

Put the outline to work

Identify Windows, WSL or another actual execution environment.
Use TeamBoost’s supported distribution and checksum.
Check version/help, then authenticate through the normal browser flow when ready.

Questions about this workflow

Does installing the skill install the executable?

No. The source skill contains guidance, not the native binary or a user session.

Do Windows and WSL share PATH automatically?

Treat them as distinct runtimes and verify the command where the agent actually executes it.

Does this create tasks in the product?

No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.

From a useful outline to team work

Explore TeamBoostAI for your team

Prepare the executable, agent instructions and account context separately before using the source-backed TeamBoost CLI workflow. Confirm the workflows available in your account before adopting this outline.

Request TeamBoostAI access