← ClaudeAtlas

prowl-clilisted

Drives the Prowl CLI (`@prowl-ai/cli`) — a shell client for Prowl exposing 448 market-intelligence tools (SEO, backlinks, 60+ SERP engines, ads, web scraping, AI) plus the full Prowl research pipeline, billed pay-as-you-go from a USD wallet. Use when a shell is available and market data is needed in a script, a CI job or a one-off command — competitor research, SERP and keyword data, backlink profiles, ad creative research, pricing and demand validation — without configuring an MCP server.
PROWL-AI/prowl-skill · ★ 1 · Data & Documents · score 68
Install: claude install-skill PROWL-AI/prowl-skill
# Prowl CLI — market intelligence from the shell `@prowl-ai/cli` is the command-line client for [Prowl](https://prowl.chat): one binary that reaches **448 market-intelligence tools** across 15 providers, plus the Prowl analysis pipeline. Every metered call debits a USD wallet. Use this skill when a shell is available. Use the sibling `prowl` plugin instead when the agent should call Prowl as MCP tools inside its own tool loop. ## Setup (one time) Prowl API keys (`prowl_...`) are **billing-bearing** — treat them as secrets and never commit them. ```bash npm install -g @prowl-ai/cli ``` **This page documents CLI `0.2.0`**, which is what npm serves as `latest`. On `0.1.1` or older only `auth`, `tools`, `call`, `analyze`, `wallet` and `version` exist and everything else answers `Unknown command` — `prowl version` says which you have. Every command, flag, exit code and default below was read out of the published tarball, and `npm run check:cli` in this repository re-reads it on every CI run. The human generates a key at [prowl.chat](https://prowl.chat) (MCP Home → API keys), then supplies it one of four ways. They are tried in this order, and the first non-empty one wins: ```bash prowl tools list --key prowl_... # 1. per-invocation flag export PROWL_API_KEY=prowl_... # 2. environment mkdir -p ~/.prowl && printf %s 'prowl_...' > ~/.prowl/prowl_mcp_token && chmod 600 ~/.prowl/prowl_mcp_token