botify-mcp
Call Botify MCP tools correctly, and fan a tool out with batch_run so lists of URLs or rows never enter the conversation. Use whenever the user is on the Botify MCP, asks to run a tool on many URLs, pages or rows, mentions batch_run, batch_status, batch_sample, batch_cancel, or wants to keep I/O out of the LLM. Also use as soon as there are more than about ten items to process.
Install
With your agent
Install OMGSkills skill "botify-hq/ai-plugins:skills/botify-mcp" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/botify-hq/ai-plugins /tmp/ai-plugins && ln -s /tmp/ai-plugins/skills/botify-mcp ~/.claude/skills/botify-mcpFrom README
Botify MCP Every Botify MCP tool processes exactly one item. Fanning a tool out is batchrun's job: the records are read from a SQL query, a table or a file, and the results are written to a sink. They do not pass through this conversation. For SQL over the catalog (tableslist, tablesquery, catalog. prefix), also read ../botify-tables-sql/SKILL.md. Tools may be deferred: call toolsearch (e.g. toolsearch(query="batchrun htmlcodeexecutor")) before the first use. Every call except listprojects needs organization and project. If the slugs are unknown, call listprojects rather than guessing. Retry a timed-out connector once or twice before treating it as a failure. One item per call items is an array of length 1. A second element is refused with an error that names batchrun. Do not loop the same tool tens of times as a workaround. Standalone tools (no items): listprojects, batchstatus, batchsample, batchcancel.