← All speakers

Bio, Work & Ideas

Mahesh Murag

Conference affiliation: Anthropic · 2025

Mahesh Murag is a member of Anthropic’s technical staff and a co-creator of Agent Skills, a system for giving AI agents reusable, specialized expertise through instructions, scripts, and reference materials. His work addresses three practical requirements for capable agents: connecting to external systems, applying domain-specific knowledge, and retaining useful experience.

At the University of California, Berkeley, Murag contributed to Flow’s research on traffic systems and autonomous vehicles. He subsequently worked at Scale AI on annotated machine-learning data, then joined Tecton, where he became a product manager overseeing compute-platform teams.

At Tecton, he worked on Rift, a Python-native managed compute engine for developing and deploying machine-learning features across batch, streaming, and real-time workloads. The platform addressed a familiar production tension: giving data scientists flexible Python workflows while maintaining reliable orchestration and low-latency serving.

At Anthropic, Murag applied that infrastructure perspective to the Model Context Protocol, then co-created Agent Skills with Barry Zhang and other colleagues. His more recent work explores memory and dreaming for self-learning agents.

Contributions and technical ideas

  • Model Context Protocol as shared infrastructure. Murag frames MCP as a standardized interface between AI applications and external tools, data, and services. He distinguishes model-controlled tools, application-controlled resources, and user-controlled prompts, preserving separate responsibilities across the agent, application, and user. His architectural concerns include authorization, server discovery, composability, evaluation, and the security implications of third-party integrations.
  • Agent Skills as portable expertise. Murag co-authored Anthropic’s engineering guide to Agent Skills with Barry Zhang and Keith Lazuka. Skills package procedural knowledge, scripts, and supporting files around a SKILL.md document, making specialized capabilities reusable, shareable, and accessible to domain experts outside software engineering. The format is also documented as an open Agent Skills standard.
  • Progressive disclosure. Agents initially see concise skill metadata and retrieve detailed instructions or supporting resources only when needed, preventing large capability libraries from overwhelming the context window. Murag applies similar thinking to searchable and hierarchically organized tools.
  • One runtime, many capabilities. A general-purpose agent equipped with code execution and a filesystem can combine MCP connectivity with task-specific skills instead of requiring separate scaffolding for every workflow. His subsequent work on memory and dreaming extends that architecture toward agents that retain, verify, and improve useful knowledge between sessions.

Talks by Mahesh Murag

2 talks

Key ideas

Scroll to read ↓

Barry Zhang and Mahesh Murag explain how reusable folders of instructions, scripts, and assets can give general-purpose agents specialized expertise without rebuilding their underlying architecture.

  • A capable general-purpose agent still needs domain expertise; reusable skills package that expertise without requiring a different agent architecture for every field. 1:20 ↗ 2:18 ↗
  • Skills are organized folders containing procedural instructions, reusable scripts, and supporting assets, with skill.md acting as the main instruction and navigation file. 2:18 ↗ 3:33 ↗ 4:39 ↗
  • Progressive disclosure protects the context window by exposing skill metadata first and loading detailed instructions or files only when a task requires them. 3:33 ↗ 4:39 ↗ 9:07 ↗
  • In the emerging agent stack, MCP supplies connectivity to external tools and data, while skills supply the procedural expertise needed to orchestrate useful workflows. 8:08 ↗ 9:07 ↗
  • As skills become more sophisticated, teams need software-style evaluation, versioning, dependency management, and runtime predictability; the speakers present these as active development priorities. 10:09 ↗ 11:14 ↗
  • Shared, agent-created skills offer a path toward transferable procedural learning, but they are not a complete memory system and do not capture every type of information. 12:26 ↗ 13:20 ↗ 14:24 ↗

Key ideas

Scroll to read ↓

Mahesh Murag explains how Model Context Protocol standardizes access to tools and data, separates model, application, and user control, and creates a foundation for more capable agents while leaving important security, observability, and governance challenges unresolved.

  • MCP standardizes the connection between AI clients and external systems, reducing duplicated integrations while allowing specialized teams to own and maintain shared data or tool interfaces. 2:59 ↗ 5:32 ↗ 6:32 ↗ 7:29 ↗
  • Tools, resources, and prompts divide control among the model, application, and user; deterministic application behavior remains possible without placing every interaction inside an LLM loop. 9:40 ↗ 10:43 ↗ 12:57 ↗ 14:04 ↗ 1:33:07 ↗
  • MCP complements agent frameworks rather than replacing them: frameworks still manage orchestration, context, memory, model choice, and iterative execution while MCP supplies interoperable capabilities. 16:52 ↗ 18:05 ↗ 19:20 ↗ 27:12 ↗ 36:32 ↗
  • Sampling and composability enable richer agent architectures, but the protocol does not automatically solve error propagation, observability, debugging, or direct server-to-server data transfer. 53:01 ↗ 55:34 ↗ 56:32 ↗ 58:09 ↗ 1:03:42 ↗ 1:34:17 ↗
  • Remote authorization increases the importance of server trust and governance; permission elevation, least-privilege practices, tool annotations, and some operational conventions are described as incomplete or still emerging. 1:08:17 ↗ 1:16:33 ↗ 1:16:57 ↗ 1:18:06 ↗ 1:27:31 ↗
  • Registries and service-owned discovery metadata could help agents find new tools, but autonomous discovery requires verification, approved-server controls, version-aware evaluation, and clear separation between proposed capabilities and existing functionality. 1:20:21 ↗ 1:22:42 ↗ 1:35:39 ↗ 1:37:53 ↗ 1:38:57 ↗ 1:40:07 ↗

References