roster

Enumerate locally installed headless AI CLIs and map their capabilities.

13|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/misty-step/harness-kit --skill roster-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roster
Source: https://github.com/misty-step/harness-kit/tree/main/skills/roster
Command: npx skills add https://github.com/misty-step/harness-kit --skill roster-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enumerates and catalogs the headless AI CLIs installed on a machine, enabling quick cross-model evaluation and governance reviews.

Core Features & Use Cases

  • Discover installed CLIs and their capabilities to compare model providers.
  • Support adversarial critique and multi-provider benchmarking across tools like codex, pi, goose, opencode, claude, cursor-agent, grok, agy, hermes, and oracle.
  • Use case: quickly assemble a cross-family capability map for a new project or eval session.

Quick Start

Run the roster probe to enumerate locally installed CLIs.

Frequently Asked Questions about roster

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

FAQPage Schema
How do I inventory locally installed headless AI CLIs for cross-model evaluation?

To inventory locally installed headless AI CLIs, run the roster probe to enumerate supported tools and map their capabilities for cross-model evaluation. It catalogs CLIs like codex, goose, and claude to outline the local roster surface.

What is a local CLI roster surface for model-provider benchmarking?

A local CLI roster surface is a catalog of installed headless AI CLIs and their probe statuses. It maps supported tools to provider capabilities and model identifiers, enabling rapid multi-provider benchmarking and governance reviews.

Does the roster probe support discovering CLIs like cursor-agent, grok, and oracle?

Yes, the roster probe supports discovering installed CLIs including cursor-agent, grok, oracle, pi, opencode, agy, and hermes. It identifies these tools to help you quickly assemble a cross-family capability map.

How do I map provider capabilities and model identifiers across adversarial critique tools?

You can map provider capabilities and model identifiers by running the roster probe to compare locally installed CLIs. It outlines probe status and results to support adversarial critique and cross-model research decisions.

Can I use a CLI inventory to support governance reviews for multiple AI model providers?

Yes, you can use a CLI inventory to support governance reviews by enumerating locally installed headless AI CLIs. This provides a clear cross-family capability map to inform decisions across model providers.