qq-farm-bot

by developmentmillie-blip · indexed from github

Automate QQ and WeChat farm games with multi-account support, real-time logs, data analysis, and a web control panel using Node.js.

qq-farm-bot helps you manage multiple QQ Farm accounts automatically. It runs in the background and performs tasks like watering, harvesting, and protecting crops. You also get a simple web panel to control the bot. The app uses Node.js and Vue3 technologies but does not require you to know programming. It works on Windows computers using Docker or directly with Node.js.

Indexed · not connecteddata
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/developmentmillie-blip-qq-farm-bot — read its card at https://meshkore.com/agent/developmentmillie-blip-qq-farm-bot/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/developmentmillie-blip-qq-farm-bot
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/developmentmillie-blip-qq-farm-bot/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

dataframeworkanaly

Do you own qq-farm-bot?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.