← All speakers

Bio, Work & Ideas

Barry Zhang

Conference affiliation: Anthropic · 2025

Barry Zhang is a member of Anthropic’s technical staff and a co-creator of Agent Skills, a framework that gives general-purpose AI agents specialized expertise through reusable files. He focuses on making agents reliable enough for consequential work without unnecessary complexity, cost, or autonomy.

From practical AI products to agent architecture

Zhang studied computer science and industrial engineering at Northwestern University and previously worked at Meta, where he was a technical lead on its generative-AI monetization team. While building AI products there in 2023, he adopted the emerging identity of an AI engineer, drawn to its emphasis on practical usefulness.

His earlier projects anticipated several directions in applied AI: BKMK uses retrieval-augmented generation to answer questions about saved bookmarks, while Auto-distill-GPT explores language-model knowledge distillation. Under his full name, Yijing Barry Zhang, he coauthored research on fine-tuned language models for text classification, including intent detection and slot filling.

At Anthropic, Zhang developed a practical philosophy of agent design before helping create Agent Skills with Mahesh Murag and colleagues. His priorities are consistent: choose autonomy carefully, give models usable tools, and preserve expertise in forms that people and agents can improve.

  • Autonomy should justify its costs. In Building effective agents, coauthored with Erik Schluntz, Zhang distinguishes predefined workflows from agents that choose actions based on environmental feedback. Predictable tasks usually warrant explicit workflows; agents make more sense when valuable work requires judgment and results can be checked. Software development fits that description because unit tests, continuous integration, and human review make outputs verifiable. His own coding workflow starts with a design document and verified tests before delegating implementation.
  • Agent-computer interfaces determine reliability. Zhang models an agent as a system using tools in a loop, shaped by its environment, instructions, and available actions. A computer-use agent given a screenshot without screen dimensions or clear tool descriptions can fail for reasons invisible to its developer. He recommends examining complete execution trajectories and improving the model’s context before adding elaborate orchestration.
  • Agent Skills package portable procedural knowledge. Skills organize instructions, scripts, examples, and supporting resources into ordinary directories. One reusable presentation-styling script, for example, can replace a procedure an agent would otherwise rewrite repeatedly. Progressive context disclosure keeps these libraries manageable: the model initially sees concise metadata, loads detailed instructions when needed, and retrieves additional files selectively.
  • Connectivity and expertise are separate layers. The Model Context Protocol connects agents to external systems; skills tell them how to perform useful work with that access. Zhang envisions shared, evolving libraries of organizational knowledge that agents can reuse across tasks and sessions. His public introduction to Skills describes this as a practical approximation of continuous learning. His account of multi-agent search adds a crucial constraint: impressive prototypes are comparatively easy; dependable production systems demand substantially more engineering.

Talks by Barry Zhang

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 ↓

Barry Zhang explains when autonomous agents are worth their cost, how to construct them around a simple tool-use loop, and why better agent behavior starts with understanding the model’s limited perspective.

  • Use an agent when the task is ambiguous, valuable, and difficult to encode as a fixed decision tree; otherwise, a predefined workflow typically offers better cost control and predictability. 1:18 ↗ 2:30 ↗
  • Evaluate token economics, critical model capabilities, error severity, and error discoverability before granting autonomy; unit tests and CI make coding particularly amenable to verification. 3:29 ↗ 4:29 ↗
  • Begin with the minimal agent architecture: an environment, a set of tools, and a system prompt, connected by a model-driven tool-use loop. 5:39 ↗ 6:53 ↗
  • Optimize only after the basic behavior works, using techniques such as trajectory caching, parallel tool calls, and progress reporting when they address actual cost, latency, or trust requirements. 6:53 ↗ 7:46 ↗
  • Debug from inside the agent’s limited context window, supplying missing environmental details and examining prompts, tool descriptions, and complete trajectories to understand unexpected decisions. 7:46 ↗ 9:01 ↗ 10:05 ↗ 11:10 ↗
  • Treat budget-aware execution, self-evolving tools, and asynchronous multi-agent communication as open engineering questions rather than solved production capabilities. 11:10 ↗ 12:11 ↗ 13:13 ↗

References