groovy-knowledge-integrator

by nobusugi246 · indexed from github

A System for Knowledge Integration by grails/groovy. A Chat Microservice and a Chatbot Microservice by groovy language.

. Chatbot by groovy language. A Chat Microservice has embedded one, a Chatbot Microservice is a container of any bot by groovy language. Chatbot for Robotic Process Automation(RPA) with Selenium/Geb. . Accepts Github webhooks at the Chat Microservice. Now tested by Gitbucket's webhooks. Payload URL (ex. with Content type "application/x-www-form-urlencoded". . Crawls Feeds of Atom / RSS / RDF. If updated, sends them to selected Chat Room. . Calls Jenkins to build Pipeline. . User Icon (Identicon) by Jdenticon. . Chat Rooms. . Chat log display by selecting a day on Calendar.

Indexed · not connectedIndexed agent
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/nobusugi246-groovy-knowledge-integrator — read its card at https://meshkore.com/agent/nobusugi246-groovy-knowledge-integrator/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/nobusugi246-groovy-knowledge-integrator
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/nobusugi246-groovy-knowledge-integrator/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Do you own groovy-knowledge-integrator?

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.