agentclash-cli-setup

Configure and validate the AgentClash CLI environment for hosted or self-hosted backends.

25|2|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/agentclash/agentclash --skill agentclash-cli-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentclash-cli-setup
Source: https://github.com/agentclash/agentclash/tree/main/web/content/agent-skills/agentclash-cli-setup
Command: npx skills add https://github.com/agentclash/agentclash --skill agentclash-cli-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves configuration friction when setting up the AgentClash CLI, ensuring that authentication, workspace selection, and backend connectivity are correctly established before running evaluations.

Core Features & Use Cases

  • Environment Configuration: Automatically handles API URL precedence for hosted, local, or self-hosted backends.
  • Identity & Access: Manages secure device login and token-based authentication for both interactive and CI environments.
  • Diagnostic Readiness: Uses the doctor command to validate workspace access, deployment visibility, and baseline readiness.

Quick Start

Use the agentclash-cli-setup skill to authenticate your session and verify that your workspace is correctly linked for running evaluations.

Frequently Asked Questions about agentclash-cli-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure the AgentClash CLI for a self-hosted backend?

Configure the AgentClash CLI for a self-hosted backend by setting the API URL precedence to route commands to your local or self-hosted target. The skill automatically handles environment configuration to ensure commands execute against the correct backend.

Can I use token-based authentication for non-interactive CLI setup in CI?

Yes, you can use token-based authentication for non-interactive CLI setup in CI environments. The skill manages secure device login and tokens for both interactive sessions and automated CI pipelines to establish backend connectivity.

What is the best way to verify workspace access and CLI readiness?

The best way to verify workspace access and CLI readiness is by running the doctor command. This diagnostic check validates workspace access, deployment visibility, and baseline readiness before executing evaluations.

How does the AgentClash CLI resolve workspace and project-local configuration files?

The AgentClash CLI resolves workspaces and project-local configuration files by managing environment variable precedence and authentication tokens. This ensures CLI commands execute against the correct target backend.

Why does my CLI environment configuration fail to link the correct workspace?

CLI environment configuration fails to link the correct workspace when API URL precedence is improperly set or authentication tokens are missing. Use the doctor command to diagnose workspace resolution and deployment visibility issues.