api-agent-ux

Guide API design reviews for agent guessability and deterministic behavior.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/clawperator/clawperator --skill api-agent-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-agent-ux
Source: https://github.com/clawperator/clawperator/tree/main/.agents/skills/api-agent-ux
Command: npx skills add https://github.com/clawperator/clawperator --skill api-agent-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clawoperator's CLI and Node API surfaces can be hard for AI agents to predict and use reliably. This skill standardizes an agent-centric UX review process to improve clarity, determinism, and documentation quality so agents can correctly anticipate how to interact with commands, flags, selectors, and error contracts.

Core Features & Use Cases

  • Read the design guiding principles and the agent-UX review frame to ground decisions.
  • Identify the surface under review (CLI command, flag, selector contract, Node API surface, or runtime surface) and map it to agent expectations.
  • Read the code that owns the surface (e.g., registry.ts, selectorFlags.ts, contracts, and serve paths) to validate implementation against UX goals.
  • Apply the agent-UX test to decide whether a change is a small alias/redirect or a broader API redesign, favoring deterministic behavior.
  • Recommend or implement the minimum fix (parser alias, renamed flag, ergonomic selectors, or did-you-mean redirects) and update docs and tests accordingly.
  • Verify outcomes with tests and reviews to ensure the surface remains guessable, deterministic, and well-documented.

Quick Start

Review a CLI or Node API surface using the guiding principles, identify the surface, examine the code, apply the agent-UX test, implement the smallest fix, and verify with tests.

Frequently Asked Questions about api-agent-ux

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

FAQPage Schema
How do I make CLI commands more predictable for AI agents to use?

To make CLI commands predictable for AI agents, apply an agent-centric UX review that enforces deterministic outputs, single primary command names, silent synonyms, and clear error contracts. This ensures command surfaces map cleanly to agent expectations.

What is agent UX review for API design?

Agent UX review for API design is a structured evaluation process that checks whether CLI commands, flags, selectors, and error schemas maximize agent guessability and deterministic behavior. It validates implementation against guiding principles to ensure reliable agent interaction.

How do I structure error messages so AI agents can recover automatically?

To structure error messages for automatic AI agent recovery, implement clear error schemas with did-you-mean redirects. This allows agents to parse the error contract, identify the correct command or flag, and retry the interaction deterministically.

When should I use a parser alias versus a full API redesign for CLI flags?

You should use a parser alias or renamed flag when the agent-UX test identifies a small guessability gap, whereas a broader API redesign is necessary when the surface fundamentally violates deterministic behavior or mapping principles.

Can I review Node API surfaces and runtime paths for agent guessability?

Yes, you can review Node API surfaces and runtime paths for agent guessability. The review process involves reading the owning code, mapping the surface to agent expectations, and verifying that outputs remain deterministic and well-documented.

Why does my AI agent fail to interact with CLI selectors deterministically?

AI agents fail to interact with CLI selectors deterministically when the selector contracts lack ergonomic mapping and clear documentation. Applying an agent-UX review identifies these gaps and recommends minimum fixes to ensure deterministic behavior.