Andrew Qu traces Vercel's data agent from a Snowflake-schema mega-prompt through specialist chains, stateful execution, a sandboxed file system, and roughly 100 distilled skills. Those lessons became Eve, a convention-based framework for composing knowledge, skills, tools, channels, and runtime services, supporting the talk's thesis that useful business agents depend on company-specific context rather than generic vertical automation.
AI Engineer18 minTranscript found
Quick learning frame
Read this before watching.
AI strategy chooses where agents create durable leverage, then manages scope, adoption, risk, and measurable outcomes.
New playlist item from AI Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to turn a recurring business bottleneck into a file-system agent whose company knowledge, skills, tools, channels, and runtime services are explicit and reusable.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Use case
02Workflow pain
03Agent role
04Adoption path
05Risk
06Metric
07Pilot
Deep lesson
Turn this video into working knowledge.
3,385 cleaned transcript words reviewed across 953 timed caption segments.
Thesis
How We Solved Agent Building — Andrew Qu, Vercel teaches a practical ai strategy move: Andrew Qu traces Vercel's data agent from a Snowflake-schema mega-prompt through specialist chains, stateful execution, a sandboxed file system, and roughly 100 distilled skills. Those lessons became Eve, a convention-based framework for composing knowledge, skills, tools, channels, and runtime services, supporting the talk's thesis that useful business agents depend on company-specific context rather than generic vertical automation.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:58
Find the Bottleneck
“agents. And we've been embarking on a similar journey to make it easy for people to build agents and agentic applications easier. We built this thing called the AIDK. So instead of needing to switch out 300 400...”
Vercel's useful starting point was not a general-purpose agent but a concrete organizational constraint: its lean data team repeatedly stopped higher-value work to translate questions from marketing and sales into queries, analysis, and recommendations. Interview one team about the task they most dislike and map the repeated request, manual steps, and higher-value work that the interruption displaces.
5:04
Preserve Working State
“passes on a query to the planning agent that will then have an execution agent etc. And if you chain all of these together, you actually get something that looks like this where each agent has a very...”
Chaining narrowly scoped planning, SQL, execution, and reporting agents enabled an end-to-end loop, but each handoff exposed only a summary of prior work. Moving to one agent that managed its own state let it revisit earlier exploration when a query or join failed. Diagram a multi-step agent workflow and mark what context is lost at each handoff, then sketch how one stateful agent could recover from an execution error.
12:30
Package Company Context
“the middle. And we thought, you know, building agents should be this simple. You should only have to create a skills folder, a tools folder, a channels folder, and you should be able to just declare these very...”
A sandbox with the semantic layer and familiar file operations doubled D0's eval score, while a recurring job distilled common queries into roughly 100 skills. Vercel packaged that pattern into Eve's convention-based knowledge, skills, tools, and channels, backed by runtime durability, isolation, models, and connections; the talk argues that company-specific relationships are what generic vertical agents lack. Draft an Eve-style agent map for one business workflow: list its proprietary knowledge, reusable skills, custom tools, user channels, and required runtime services, then mark which company relationships an off-the-shelf agent would miss.
01
Use case
Start with this video's job: Andrew Qu traces Vercel's data agent from a Snowflake-schema mega-prompt through specialist chains, stateful execution, a sandboxed file system, and roughly 100 distilled skills. Those lessons became Eve, a convention-based framework for composing knowledge, skills, tools, channels, and runtime services, supporting the talk's thesis that useful business agents depend on company-specific context rather than generic vertical automation. Treat "Use case" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:58, where the video says: “agents. And we've been embarking on a similar journey to make it easy for people to build agents and agentic applications easier. We built this thing called the AIDK. So instead of needing to switch out 300 400...”
02
Workflow pain
Use "Workflow pain" to locate the part of the ai strategy mechanism the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 5:04, where the video says: “passes on a query to the planning agent that will then have an execution agent etc. And if you chain all of these together, you actually get something that looks like this where each agent has a very...”
03
Agent role
Turn "Agent role" into the reusable artifact for this lesson: A one-page AI workflow decision memo with use case, leverage claim, risks, metric, and pilot plan. This is where watching becomes something you can inspect and reuse.
04
Adoption path
Use "Adoption path" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Risk
Use "Risk" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Metric
Use "Metric" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
07
Pilot
Connect "Pilot" to How We Solved Agent Building — Andrew Qu, Vercel by naming the claim, the evidence, and the artifact it should produce.
Example
Source-backed artifact packet
Convert the video into a scoped artifact request that includes the transcript claim, mechanism, acceptance criteria, and proof. The output should be a one-page ai workflow decision memo with use case, leverage claim, risks, metric, and pilot plan..
Example
AI strategy proof brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the ai strategy pattern.
Example
Teach-back module
Transform the lesson into a definition, a Use case -> Workflow pain -> Agent role -> Adoption path -> Risk -> Metric -> Pilot diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
hype laundering
market claims without operational proof
strategy with no pilot
Letting the lesson drift into generic AI business advice.
Letting the lesson drift into unsupported market forecasts.
Letting the lesson drift into no-risk adoption plans.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: Andrew Qu traces Vercel's data agent from a Snowflake-schema mega-prompt through specialist chains, stateful execution, a sandboxed file system, and roughly 100 distilled skills. Those lessons became Eve, a convention-based framework for composing knowledge, skills, tools, channels, and runtime services, supporting the talk's thesis that useful business agents depend on company-specific context rather than generic vertical automation.
02
Explain the practical stakes without hype: New playlist item from AI Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Use case -> Workflow pain -> Agent role -> Adoption path -> Risk -> Metric -> Pilot sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A one-page AI workflow decision memo with use case, leverage claim, risks, metric, and pilot plan.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: How We Solved Agent Building — Andrew Qu, Vercel
- URL: https://www.youtube.com/watch?v=9dYcwOkpCE8
- Topic: Codex + Claude Workflows
- My current learning frame: Choose one recurring internal request, prototype it with file tools, distill a successful procedure into a skill, and specify the company knowledge, channels, and runtime services needed to make the agent production-ready.
- Why this matters: New playlist item from AI Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:58 / Evidence 1: "agents. And we've been embarking on a similar journey to make it easy for people to build agents and agentic applications easier. We built this thing called the AIDK. So instead of needing to switch out 300 400..."
- 5:04 / Evidence 2: "passes on a query to the planning agent that will then have an execution agent etc. And if you chain all of these together, you actually get something that looks like this where each agent has a very..."
- 8:43 / Evidence 3: "really just use a file system. You know, we we saw the learnings from claw code and how powerful it was given that it just executes locally. And we tried to rebuild it in a way that was..."
- 11:00 / Evidence 4: "layer and the system prompt. But with a skill, it already starts off with a lot of contextual knowledge that has otherwise already been done. And this is roughly how it looks. It's very similar to the previous..."
- 12:30 / Evidence 5: "the middle. And we thought, you know, building agents should be this simple. You should only have to create a skills folder, a tools folder, a channels folder, and you should be able to just declare these very..."
- 14:22 / Evidence 6: "a mini claw to go and test people's services. It goes to websites, installs them, it tries to use them. And they've seen incredible success on building their own agent from the ground up using Eve compared to..."
- 15:57 / Evidence 7: "a squeeze, you should really try to build your own agent and add in as much company specific knowledge as you can. Today, you know, we've had 20 roughly decently PMF agents adversel that range from anything from..."
Video-aware target:
- Prompt lane: AI strategy
- Mechanism to extract: Separate strategic signal from launch noise by identifying the workflow change and the evidence needed to trust it.
- Artifact to produce: A one-page AI workflow decision memo with use case, leverage claim, risks, metric, and pilot plan.
- Artifact must include: use case; workflow change; risk; metric; pilot scope
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Separate strategic signal from launch noise by identifying the workflow change and the evidence needed to trust it. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A one-page AI workflow decision memo with use case, leverage claim, risks, metric, and pilot plan.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Use case -> Workflow pain -> Agent role -> Adoption path -> Risk -> Metric -> Pilot
- answers to these source questions: What work changes? | Who benefits? | What evidence would make the claim decision-grade?
- 3 concrete examples that apply the video idea to real agentic work, such as agent pilot memo; skill-library adoption plan; model-release triage note
- 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: hype laundering; market claims without operational proof; strategy with no pilot
- a checklist for the next real workflow, focused on: workflow, leverage, risk, metric, pilot
- one practical exercise with a clear done signal: Convert one strategy claim into a two-week pilot with a measurable done signal.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "How We Solved Agent Building — Andrew Qu, Vercel", not a generic Codex + Claude Workflows essay.
- Tie each strategic claim to transcript anchors, then label any market/news context that is not proven by the video.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic AI business advice; unsupported market forecasts; no-risk adoption plans.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
One agent should do every task.
Different tools have different strengths. Routing is part of the workflow.
More context is always better.
Relevant context helps; stale context causes drift and cost.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a one-page ai workflow decision memo with use case, leverage claim, risks, metric, and pilot plan..
A reusable artifact with a done signal and one verification step.03
AI strategy teach-back card
Explain the ai strategy mechanism to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
Why did Vercel choose the data team's query workflow for its early internal agent experiment?
What advantage did one state-managing agent have over the earlier chain of specialized agents?
What does Eve package, and why does the talk favor a company-specific agent?
Source shelf
Use the video as a doorway, then verify with primary sources.
