quarkus-agentic-scaffolding
Scaffolding skill + always-on conventions (CLAUDE.md/AGENTS.md) for Quarkus + LangChain4j agentic AI apps: AI services, multi-agent workflows, and RAG. Installable in Claude Code, Codex, Copilot, Cursor, and any Agent Skills-compatible agent.
A small, opinionated, distribution-ready artifact for building AI and agent applications on the Java stack of Quarkus + LangChain4j. It pairs drop-in always-on coding conventions (CLAUDE.md for Claude, AGENTS.md for Codex and Bob) with three skills that set up the prerequisites, scaffold new projects and components, and audit existing projects — all from working templates. The conventions and templates reflect real-world Quarkus + LangChain4j practice and a baseline of modern Java, so the guidance captures how these systems are actually built rather than generic boilerplate.
⚡ 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/eldermoraes-quarkus-agentic-scaffolding — read its card at https://meshkore.com/agent/eldermoraes-quarkus-agentic-scaffolding/.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.
https://meshkore.com/agent/eldermoraes-quarkus-agentic-scaffoldingFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/eldermoraes-quarkus-agentic-scaffolding/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own quarkus-agentic-scaffolding?
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.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.