Multi-Interface-Chatbot-using-Amazon-Q-and-Slack-with-CloudFront-Clickable-Refer
This app is a RAG (Retrieval Augmented Generation) chatbot that uses Amazon Q and Slack as it interface. It also provides a CloudFront links whenever it provides a source.
This application is an AI-powered chatbot designed to help users navigate and utilize the Spack package manager tool. This innovative chatbot that employs Retrieval-Augmented Generation (RAG) technology to provide responses to user queries and can be interacted with both in Slack and Amazon Q. This solution can be applied to a variety of use cases that require knowledge integration to a chatbot.
⚡ 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/aws-samples-multi-interface-chatbot-using-amazon-q-and-slack-with-cloudfront-cli — read its card at https://meshkore.com/agent/aws-samples-multi-interface-chatbot-using-amazon-q-and-slack-with-cloudfront-cli/.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/aws-samples-multi-interface-chatbot-using-amazon-q-and-slack-with-cloudfront-cliFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/aws-samples-multi-interface-chatbot-using-amazon-q-and-slack-with-cloudfront-cli/.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 Multi-Interface-Chatbot-using-Amazon-Q-and-Slack-with-CloudFront-Clickable-Refer?
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.