Skills vs MCP vs RAG vs Memory: What AI Agents Need to Know



Learn more about Types of AI Agents here →

AI agents need more than training data to solve real-world problems. Martin Keen breaks down four core techniques used in modern AI agents: Skills, MCP, RAG, and Memory. Learn when each approach should be used, how they work together, and why they play different roles in helping AI agents access information, follow procedures, and learn from experience.

AI news moves fast. Sign up for a monthly newsletter for AI updates from IBM →

AI was used in the creation of the transcript and metadata for this video.

#skills #mcp #retrievalaugmentedgeneration #memory #aiagents

source

35 Comments

  1. i actually created something that combines all the first 3, i wrote an MCP server that wraps around copilot 365 retrieval RAG api for sharepoint documents (like SysRS and PRD documents) and it has a skill that tells it how to call the api, where to look for etc.. it has worked so far EXTREMELY well, so much that in some cases i'd ask it why something isn't working right, it''d run to read the docs and implement the fix CORRECTLY.
    it doesn't have to be vs. it can be all of the above.
    i'm curious to know if githubcopilot has a concpet of memory.

  2. Sorry, but I think this is unprecise and a bit fuzzy. A real-world MCP example would be better. And what exactly do you mean with "Memory"? Which technology are you talking about? Finetuning the model, Lora?

  3. The content in this video was explained with a master-class skill, making it easy to internalize in our Memory. I feel like I am building a solid RAG-style understanding of AI, without needing to have MCP for any other learning site.

  4. Normally, if you want a robot to learn a new task, you may need to collect training data, retrain the model, and test it again.

    ICL tries to change that.

    Imagine you have a robot and say:

    “Pick up this object, put it in the box, and then close the lid.”

    Instead of retraining the robot, you give it instructions, examples, or demonstrations. The robot uses that context to figure out what to do right now.

    So:

    Traditional robot:
    New task → collect data → train → deploy

    ICL robot:
    New task → show/instruct → understand context → act

    The exciting part about Gen-1.5 is the possibility that robots can handle more complicated, unfamiliar tasks from context, rather than being trained specifically for every individual task.

    But there's an important distinction:

    ICL isn't necessarily permanent learning.

    The robot may successfully adapt during the current task without actually changing its underlying model permanently.

    If this technology works reliably, robots could become much more general-purpose.

    Instead of manufacturing:

    one robot for one task

    you could have:

    one capable robot + instructions/examples → many different tasks.

    That's a major step toward general-purpose physical AI.

    LLMs showed that AI can adapt to new problems from context. ICL for robots is trying to bring that same flexibility into the physical world.

  5. When an AI scans five different policy documents 📄 to find a hidden contradiction , does that count as a basic data retrieval job, or are you witnessing the model use its own logic and context to figure it out?

  6. A pie chart 📈 or a complex table is meant to be scanned with human eyes , not parsed by an AI database. How difficult is it for modern RAG systems to convert those shapes and columns into something a language model can read?BTW, I am also aware that Multimodal RAG is actually one of the biggest battlegrounds in AI development right now.

  7. A useful way to operationalize this distinction is to define ownership boundaries: Skills encode repeatable procedures, MCP standardizes tool access, RAG supplies relevant evidence, and memory preserves task-specific state. The key governance question is what may be written to memory—and when retrieved evidence should override it.

  8. This is the kind of AI content I wish I’d found sooner. Clear, practical, and easy to follow without oversimplifying the topic. The explanation of how these pieces work together in real AI agents was especially helpful. Great job!

  9. It looks like MCP is only used for the "tools" part of it. It can however, provide "resources", too. Which could be interface to, or substitute for, RAG. I don't like RAG as it never picks the right document when you have lots of similar documents with little variations in it (e.g. manual pages of a software with different versions).

  10. Since RAG relies entirely on human written knowledge, what happens when two different people write down conflicting facts in the company database, and the RAG system pulls both? How does AI decide who to believe?

  11. WRT RAG, what happens to information that is never written down? If a team relies on un-documented know-how, how do we capture that for AI (without asking humans to write ✍️ manuals)?

Leave a Reply

Your email address will not be published. Required fields are marked *

You might like

© 2026 Cantinho do Vídeo - WordPress Video Theme by WPEnjoy