CLI-Anything is a meta-framework for generating agent-native CLI interfaces for arbitrary GUI applications. The repository contains 40+ pre-built CLI harnesses (e.g., Blender, GIMP, Audacity, LibreOffice, OBS Studio) each structured as a self-contained Python package under `cli_anything.<name>/`. These harnesses provide a consistent Click-based CLI with `--json` output, interactive REPL mode, session management with undo/redo, and backend abstraction over subprocess or API calls. The project also includes a CLI-Hub package manager, agent plugins for Claude Code, Pi, Codex, Hermes, and a skill generation system. The primary data flow is: agent/user invokes a CLI command → harness translates to subprocess/API calls to the target software → structured output returned. External dependencies are the target software binaries (must be pre-installed). The codebase is well-tested (2,461 tests passing) and actively maintained, though significant code duplication exists across harnesses.
This repository is a distribution and development monorepo for "Agent Skills" — packaged instruction sets, rule files, and CLI tooling that extend AI coding agents to work more effectively with Vercel, React, Next.js, and React Native. The dominant artifact is the `vercel-optimize` skill, a sophisticated performance/cost audit pipeline. It starts by collecting real signals from the Vercel CLI (metrics, usage, project config, route data), then applies deterministic pure-JS gates and AST-based code scanners to generate candidate investigation targets. LLM sub-agents receive structured investigation briefs with playbooks, citations, and support-topic guardrails; their outputs are collected, mechanically verified, sanitized, deduplicated, graded, and rendered into a customer-safe markdown report. This is not a web service or library in the traditional sense — it is a toolchain of executable scripts plus knowledge artifacts designed to be installed into agent environments via `npx skills add`. The repository also contains curated knowledge bases (`react-best-practices`, `react-native-skills`, `composition-patterns`, `react-view-transitions`, `web-design-guidelines`) stored as markdown rules with YAML frontmatter. A build package (`react-best-practices-build`) parses these rules, validates them, and compiles them into `AGENTS.md` files for consumption by agents. The engineering quality is strongest in `vercel-optimize`: it has extensive `node:test` coverage, real CLI output fixtures, a modular gate/scanner/sanitizer architecture, claim-based verification, and careful handling of Vercel API rate limits. The main risks are external dependency drift — Vercel CLI output schemas, metric IDs, Observability Plus availability, and Next.js/React framework versions all change over time — and the inherent fragility of parsing LLM sub-agent output. Although the repo contains large amounts of markdown knowledge content, the dominant character is application/tooling: it ships executable entry points, has unit tests, CI workflows, and a build pipeline. It is not a data-research repository, and the metric fixtures exist to test the tooling rather than to answer analytical questions.