Agent skills for the cloro API. With them, any coding agent can get the answers that ChatGPT, Gemini, Google AI Mode, Bing AI Mode and Google AI Overview give, and the Google Search and Google News results, as structured JSON. The agent can track a brand in AI answers, track Google rankings and collect AI answers at volume.
A skill is a folder with a SKILL.md file and, where necessary, reference files. Any agent that reads SKILL.md files can use these skills: Claude Code, Codex, Cursor and others.
In Claude Code, install the cloro plugin. It adds the 15 skills and connects the cloro MCP server:
/plugin install cloro --marketplace cloro-dev/skills
This works in one step on Claude Code 2.1.275 or later. On an earlier version, run /plugin marketplace add cloro-dev/skills, then /plugin install cloro@cloro. The MCP server asks you to sign in to cloro the first time a tool runs.
For other agents (Codex, Cursor and others), add the skills only:
npx skills add cloro-dev/skillsTo add one skill, add --skill <name>, for example --skill chatgpt. Without Node.js, clone this repo and copy the folders under skills/ into the folder where your agent reads skills.
Then get an API key from the dashboard and set it as CLORO_API_KEY. The free tier gives 500 credits each month and 1 concurrent request, with access to all endpoints. No card is necessary.
For an agent that calls tools at run time, also connect the cloro MCP server at https://mcp.cloro.dev/mcp. The skills tell the agent which tool to call and how to read the result.
| Skill | What it does |
|---|---|
cloro-api |
Start here. Auth, MCP or REST or SDK, sync or async, credits and success billing, retries, rate and concurrency limits. Routes each task to the right skill |
chatgpt |
ChatGPT answers with citations, shopping cards, ads and the query fan-out |
gemini |
Gemini answers with grounded sources, places and shopping cards |
google-ai-mode |
Google AI Mode answers with sources, citation pills, places, shopping cards and ads |
bing-ai-mode |
Bing AI Mode answers with sources and citation pills, by country and US state |
google-ai-overview |
The Google AI Overview and all its cited sources, by keyword and location |
google-search |
Google results as JSON: organic results, People Also Ask, local pack, shopping, ads. City and device targeting, up to 10 pages, raw HTML |
web-search |
Live web search for an agent or a RAG pipeline: one Google search, returned as a short context with the AI Overview, the top results and their links |
google-news |
Google News articles with source, date and thumbnail |
serp-research |
Rank tracking and SERP research at scale: thousands of keywords a day, on a schedule, into a warehouse |
llm-answer-monitoring |
Collect AI answers for a prompt set across engines, once or on a schedule, at volume. Build a dataset of AI answers |
ai-visibility-tracking |
Measure a brand in AI answers: mention rate, citation share and the rival brands that the engines name |
ai-seo-audit |
AI SEO (GEO, AEO) audit: the prompts where rivals are named and the brand is not, the pages the engines cite, and the actions to take |
serp-analysis |
Analyze the Google results page for a keyword: intent, ranking page types, AI Overview sources, People Also Ask, and a content brief |
deep-research |
Research a topic across many Google and Google News searches and AI answers, and write a report with a dated source for each claim |
cloro sends each prompt to the real product, ChatGPT or Google AI Mode for example, in a logged-out browser session in the country you select. The result is what a user in that country sees, parsed into JSON. It is not the answer of the vendor's model API. cloro charges only for results: a request that fails costs nothing.
The skills and the plugin send data to two cloro services only:
https://api.cloro.dev: the REST API. The skills send your prompts, queries and request options, with yourCLORO_API_KEY.https://mcp.cloro.dev/mcp: the MCP server. It sends the same data to the REST API for you, after you sign in to cloro.
The deep-research skill also tells the agent to read the result pages with its own fetch tool. Those requests go to the sites in the results, not to cloro.
cloro deletes finished async tasks about 24 hours after creation. See the privacy policy, the Data Protection Agreement and the terms.
- API reference
- Pricing
- MCP server
- Python SDK, TypeScript SDK
- geo-tracker: a scheduled AI visibility tracker that stores answers in your Postgres
MIT. See LICENSE.