---
schema: 1
type: video
title: >-
  500 Skills, Zero Fine-Tuning: LinkedIn's Playbook for AI Agents — Ajay
  Prakash, LinkedIn
description: >-
  LinkedIn exposes roughly 1,300 tools and 600 playbooks to its coding agents,
  and all of them sit behind exactly three. MCP degrades somewhere past thirty
  or forty tools, so Ajay Prakash's team replaced the whole surface with search,
  get schema, and execute, letting an agent find what it needs instead of
  carrying everything in context. Prakash is a senior staff software engineer at
  LinkedIn, and he opens with an on call incident. An alert goes to a coding
  agent, which pulls the debugging instructions for that specific service,
  fetches logs and metrics, finds the root cause, proposes mitigation steps,
  applies them once a human confirms, updates the incident record, and opens a
  PR for the underlying fix. Minutes instead of hours. The rest of the talk is
  about the infrastructure that makes that reliable rather than lucky. It did
  not start there. Agents trained on public repositories knew nothing about a
  thousand internal repos, custom databases, or a configuration system that new
  hires spend a week long boot camp learning, so engineers spent longer
  correcting hallucinations than writing the code themselves. An internal MCP
  server with code search helped, then documents, Jira, Slack, and feature
  flags. Tools alone still fell short, because the knowledge of how to use them
  sat scattered across stale wikis and old Slack threads, and every session
  started from nothing. Playbooks are the answer: instructions published as
  tools, invoked like any other tool, kept self contained and split into small
  referenced pieces so context arrives progressively. Agents are asked to open a
  PR improving any playbook they find stale, which is what keeps the corpus
  alive. Speaker info: - https://x.com/ajay_prakash_ai -
  https://www.linkedin.com/in/ajay-prakash-3780b132/ Timestamps: 0:00 - An on
  call incident, handled end to end 2:48 - Why coding agents failed inside
  LinkedIn 5:10 - A thousand repos on internal frameworks 6:34 - An internal
  MCP, starting with code search 8:30 - Why tools alone were not enough 10:34 -
  Playbooks, instructions served as tools 12:27 - Two rules, self contained and
  broken up 14:23 - The loop that keeps playbooks fresh 15:34 - Architecture,
  local and central playbooks 17:23 - Three meta tools to scale past the MCP
  limit 19:01 - Takeaways --- Watch along with the corrected transcript,
  summary, timestamps and resources on this talk's official AIE page:
  https://ai.engineer/talks/9wZpvF3QleU-youtube-5d35be70109d22d9fffd Join our
  upcoming AI Engineer conferences (see https://ai.engineer landing page): -
  AIEi Shanghai, November 5–6 — the first for meeting top Chinese labs and
  engineers - AIE CODE in SF, November 10–12 — the top AI Coding conference
  returns - AIEi Sydney, December 7–8 — the first AIEi run alongside NeurIPS
  2026 in Sydney ---
canonical: >-
  https://liquidgold.cc/channel/aidotengineer/explore/video/500-skills-zero-fine-tuning-linkedin-s-playbook-for-124a9a2dc1c1
markdown: >-
  https://liquidgold.cc/channel/aidotengineer/video/500-skills-zero-fine-tuning-linkedin-s-playbook-for-124a9a2dc1c1.md
llms: null
parent: 'https://liquidgold.cc/channel/aidotengineer.md'
channel: aidotengineer
updated: '2026-10-24T03:59:46.642Z'
language: null
children: []
videoId: 9wZpvF3QleU
durationSeconds: 1225
publishedAt: '2026-09-09T14:00:06.000Z'
searchChunks:
  - ordinal: 0
    text: null
    startSeconds: 25
    endSeconds: 170
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=25'
    heldReason: rights
  - ordinal: 1
    text: null
    startSeconds: 181
    endSeconds: 318
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=181'
    heldReason: rights
  - ordinal: 2
    text: null
    startSeconds: 181
    endSeconds: 318
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=181'
    heldReason: rights
  - ordinal: 3
    text: null
    startSeconds: 329
    endSeconds: 402
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=329'
    heldReason: rights
  - ordinal: 4
    text: null
    startSeconds: 412
    endSeconds: 513
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=412'
    heldReason: rights
  - ordinal: 5
    text: null
    startSeconds: 524
    endSeconds: 638
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=524'
    heldReason: rights
  - ordinal: 6
    text: null
    startSeconds: 524
    endSeconds: 638
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=524'
    heldReason: rights
  - ordinal: 7
    text: null
    startSeconds: 524
    endSeconds: 638
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=524'
    heldReason: rights
  - ordinal: 8
    text: null
    startSeconds: 651
    endSeconds: 755
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=651'
    heldReason: rights
  - ordinal: 9
    text: null
    startSeconds: 766
    endSeconds: 869
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=766'
    heldReason: rights
  - ordinal: 10
    text: null
    startSeconds: 766
    endSeconds: 869
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=766'
    heldReason: rights
  - ordinal: 11
    text: null
    startSeconds: 766
    endSeconds: 869
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=766'
    heldReason: rights
  - ordinal: 12
    text: null
    startSeconds: 880
    endSeconds: 937
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=880'
    heldReason: rights
  - ordinal: 13
    text: null
    startSeconds: 948
    endSeconds: 1047
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=948'
    heldReason: rights
  - ordinal: 14
    text: null
    startSeconds: 1058
    endSeconds: 1147
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=1058'
    heldReason: rights
  - ordinal: 15
    text: null
    startSeconds: 1058
    endSeconds: 1147
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=1058'
    heldReason: rights
  - ordinal: 16
    text: null
    startSeconds: 1158
    endSeconds: 1225
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=1158'
    heldReason: rights
  - ordinal: 17
    text: null
    startSeconds: 1158
    endSeconds: 1225
    watch: 'https://liquidgold.cc/watch/9wZpvF3QleU?t=1158'
    heldReason: rights
---


# 500 Skills, Zero Fine-Tuning: LinkedIn's Playbook for AI Agents — Ajay Prakash, LinkedIn

LinkedIn exposes roughly 1,300 tools and 600 playbooks to its coding agents, and all of them sit behind exactly three. MCP degrades somewhere past thirty or forty tools, so Ajay Prakash's team replaced the whole surface with search, get schema, and execute, letting an agent find what it needs instead of carrying everything in context. Prakash is a senior staff software engineer at LinkedIn, and he opens with an on call incident. An alert goes to a coding agent, which pulls the debugging instructions for that specific service, fetches logs and metrics, finds the root cause, proposes mitigation steps, applies them once a human confirms, updates the incident record, and opens a PR for the underlying fix. Minutes instead of hours. The rest of the talk is about the infrastructure that makes that reliable rather than lucky. It did not start there. Agents trained on public repositories knew nothing about a thousand internal repos, custom databases, or a configuration system that new hires spend a week long boot camp learning, so engineers spent longer correcting hallucinations than writing the code themselves. An internal MCP server with code search helped, then documents, Jira, Slack, and feature flags. Tools alone still fell short, because the knowledge of how to use them sat scattered across stale wikis and old Slack threads, and every session started from nothing. Playbooks are the answer: instructions published as tools, invoked like any other tool, kept self contained and split into small referenced pieces so context arrives progressively. Agents are asked to open a PR improving any playbook they find stale, which is what keeps the corpus alive. Speaker info: - https://x.com/ajay_prakash_ai - https://www.linkedin.com/in/ajay-prakash-3780b132/ Timestamps: 0:00 - An on call incident, handled end to end 2:48 - Why coding agents failed inside LinkedIn 5:10 - A thousand repos on internal frameworks 6:34 - An internal MCP, starting with code search 8:30 - Why tools alone were not enough 10:34 - Playbooks, instructions served as tools 12:27 - Two rules, self contained and broken up 14:23 - The loop that keeps playbooks fresh 15:34 - Architecture, local and central playbooks 17:23 - Three meta tools to scale past the MCP limit 19:01 - Takeaways --- Watch along with the corrected transcript, summary, timestamps and resources on this talk's official AIE page: https://ai.engineer/talks/9wZpvF3QleU-youtube-5d35be70109d22d9fffd Join our upcoming AI Engineer conferences (see https://ai.engineer landing page): - AIEi Shanghai, November 5–6 — the first for meeting top Chinese labs and engineers - AIE CODE in SF, November 10–12 — the top AI Coding conference returns - AIEi Sydney, December 7–8 — the first AIEi run alongside NeurIPS 2026 in Sydney ---

Canonical: https://liquidgold.cc/channel/aidotengineer/explore/video/500-skills-zero-fine-tuning-linkedin-s-playbook-for-124a9a2dc1c1 · Channel: [AI Engineer](https://liquidgold.cc/channel/aidotengineer.md)

> Search chunk text is held until public-source provenance is verified.

## Document chunks

> Missing: no stored document chunks are available.
