@datalayer/agent-runtimes 1.3.10 → 1.3.13

package/lib/specs/agents/agents.js

@@ -5,7 +5,7 @@
 import { ALPHAVANTAGE_MCP_SERVER_0_0_1, CHART_MCP_SERVER_0_0_1, EARTHDATA_MCP_SERVER_0_0_1, EURUS_MCP_SERVER_0_0_1, FILESYSTEM_MCP_SERVER_0_0_1, GITHUB_MCP_SERVER_0_0_1, GOOGLE_WORKSPACE_MCP_SERVER_0_0_1, HUGGINGFACE_MCP_SERVER_0_0_1, KAGGLE_MCP_SERVER_0_0_1, ODOO_MCP_SERVER_0_0_1, SALESFORCE_MCP_SERVER_0_0_1, SLACK_MCP_SERVER_0_0_1, TAVILY_MCP_SERVER_0_0_1, } from '../mcpServers';
 import { ACCOUNTING_SKILL_SPEC_0_0_1, CRAWL_SKILL_SPEC_0_0_1, EVENTS_SKILL_SPEC_0_0_1, GITHUB_SKILL_SPEC_0_0_1, JOKES_SKILL_SPEC_0_0_1, PDF_SKILL_SPEC_0_0_1, TEXT_SUMMARIZER_SKILL_SPEC_0_0_1, } from '../skills';
 import { EXAMPLE_CREATE_PLAN_TOOL_SPEC_0_0_1, EXAMPLE_CURRENT_TIME_TOOL_SPEC_0_0_1, EXAMPLE_DISPLAY_RECIPE_TOOL_SPEC_0_0_1, EXAMPLE_GENERATE_HAIKU_TOOL_SPEC_0_0_1, EXAMPLE_GENERATE_TASK_STEPS_TOOL_SPEC_0_0_1, EXAMPLE_GET_WEATHER_TOOL_SPEC_0_0_1, EXAMPLE_RENDER_A2UI_SURFACE_TOOL_SPEC_0_0_1, EXAMPLE_UPDATE_PLAN_STEP_TOOL_SPEC_0_0_1, RUNTIME_ECHO_TOOL_SPEC_0_0_1, RUNTIME_SEND_MAIL_TOOL_SPEC_0_0_1, RUNTIME_SENSITIVE_ECHO_TOOL_SPEC_0_0_1, } from '../tools';
-import { JUPYTER_NOTEBOOK_EDIT_FRONTEND_TOOL_SPEC_0_0_1, JUPYTER_NOTEBOOK_PROPOSE_FRONTEND_TOOL_SPEC_0_0_1, JUPYTER_NOTEBOOK_READ_FRONTEND_TOOL_SPEC_0_0_1, JUPYTER_NOTEBOOK_FRONTEND_TOOL_SPEC_0_0_1, LEXICAL_DOCUMENT_FRONTEND_TOOL_SPEC_0_0_1, } from '../frontendTools';
+import { DECKS_FRONTEND_TOOL_SPEC_0_0_1, JUPYTER_NOTEBOOK_EDIT_FRONTEND_TOOL_SPEC_0_0_1, JUPYTER_NOTEBOOK_PROPOSE_FRONTEND_TOOL_SPEC_0_0_1, JUPYTER_NOTEBOOK_READ_FRONTEND_TOOL_SPEC_0_0_1, JUPYTER_NOTEBOOK_FRONTEND_TOOL_SPEC_0_0_1, LEXICAL_DOCUMENT_FRONTEND_TOOL_SPEC_0_0_1, } from '../frontendTools';
 // ============================================================================
 // MCP Server Lookup
 // ============================================================================
@@ -98,6 +98,8 @@ const TOOL_MAP = {
  * Map frontend tool IDs to FrontendToolSpec objects.
  */
 const FRONTEND_TOOL_MAP = {
+    'decks:0.0.1': DECKS_FRONTEND_TOOL_SPEC_0_0_1,
+    decks: DECKS_FRONTEND_TOOL_SPEC_0_0_1,
     'jupyter-notebook-edit:0.0.1': JUPYTER_NOTEBOOK_EDIT_FRONTEND_TOOL_SPEC_0_0_1,
     'jupyter-notebook-edit': JUPYTER_NOTEBOOK_EDIT_FRONTEND_TOOL_SPEC_0_0_1,
     'jupyter-notebook-propose:0.0.1': JUPYTER_NOTEBOOK_PROPOSE_FRONTEND_TOOL_SPEC_0_0_1,
@@ -488,6 +490,117 @@ screen — do not apologise for it or offer to fix the code.
     parameters: undefined,
     subagents: undefined,
 };
+export const EXAMPLE_A2UI_VIEWER_AGENTSPEC_0_0_1 = {
+    id: 'example-a2ui-viewer',
+    version: '0.0.1',
+    name: 'A2UI Viewer Agent',
+    description: `Answers beside the A2UI Viewer, whose scenes — a recipe card, a booking form, a sales snapshot and a shipping status — it renders on request as live A2UI surfaces, and runs code in the sandbox to show its outputs.`,
+    tags: ['a2ui', 'viewer', 'loop'],
+    domain: undefined,
+    enabled: true,
+    model: 'bedrock:us.anthropic.claude-sonnet-4-6',
+    mcpServers: [],
+    skills: [].filter(Boolean),
+    tools: [TOOL_MAP['example-render-a2ui-surface:0.0.1']],
+    frontendTools: [],
+    frontendRenderTools: [
+        { tool: 'render_a2ui_surface', renderer: 'a2ui-surface' },
+    ],
+    environmentName: 'ai-agents-env',
+    icon: 'browser',
+    emoji: '🔍',
+    color: '#6366F1',
+    suggestions: [
+        {
+            text: 'Show a recipe card for a Mediterranean quinoa bowl, with a photo, its rating and review count, prep and cook time, and how many it serves.',
+            summary: 'Recipe Card',
+            emoji: '🍲',
+        },
+        {
+            text: 'Build a table booking form with party size, date and time, dietary requirements and a Submit Reservation button.',
+            summary: 'Booking Form',
+            emoji: '📅',
+        },
+        {
+            text: 'Show a Q2 sales snapshot by category — Apparel, Electronics, Home Goods and Health & Beauty — as KPI tiles under one headline.',
+            summary: 'Sales Snapshot',
+            emoji: '📈',
+        },
+        {
+            text: 'Show a package status card with the tracking number, the steps from placed to shipped to out for delivery, and the ETA.',
+            summary: 'Shipping Status',
+            emoji: '📦',
+        },
+        {
+            text: 'Plot a chart in the code sandbox and show me the image.',
+            summary: 'Plot a chart',
+            emoji: '📈',
+        },
+        {
+            text: 'Build a small DataFrame in the code sandbox and show it as a table.',
+            summary: 'DataFrame as a table',
+            emoji: '🧮',
+        },
+        {
+            text: 'Run something in the code sandbox that fails, so I can see the traceback.',
+            summary: 'Show a traceback',
+            emoji: '🐛',
+        },
+        {
+            text: 'Show me an interactive slider from the code sandbox.',
+            summary: 'Interactive slider',
+            emoji: '🎛️',
+        },
+    ],
+    welcomeMessage: 'This is the A2UI Viewer. Pick a scene above to see a surface drawn from A2UI messages, ask me to render one of them here, or run something in the code sandbox and see its output.',
+    welcomeNotebook: undefined,
+    welcomeDocument: undefined,
+    sandboxVariant: 'browser',
+    harness: 'vercel-ai',
+    systemPrompt: `You answer beside the A2UI Viewer, an example that renders A2UI surfaces
+from pasted protocol messages: a recipe card, a table booking form, a sales
+snapshot of KPI tiles, and a shipping status timeline.
+
+When asked for a surface — one of those, or anything like them:
+1. ALWAYS call the \`render_a2ui_surface\` tool to produce it. Never describe
+   the surface in prose instead of rendering it.
+2. Choose a concise \`title\` and a one-sentence \`intro\`.
+3. Design a sensible ordered list of \`fields\`, picking the best \`type\` for
+   each: \`text\` / \`email\` for short input, \`longtext\` for notes, \`choice\`
+   or \`multichoice\` with \`options\` for pick-lists, \`checkbox\` for yes/no,
+   \`slider\` with \`min\`/\`max\` for ranges and ratings, \`date\` / \`datetime\`
+   for scheduling. A card that shows values rather than asking for them
+   still renders as a surface: put each value in a field with its label.
+4. After the tool call, reply with ONE short sentence saying what you
+   rendered. Do not repeat the fields in text — the surface is shown.
+
+When asked to run code, use \`execute_code\` in the sandbox and let the
+outputs speak: a figure, a table, a traceback, a widget. Do not look for
+helpers or skills in the sandbox; write the Python yourself.
+`,
+    systemPromptCodemodeAddons: undefined,
+    goal: undefined,
+    delegable: [],
+    protocol: 'vercel-ai',
+    uiExtension: undefined,
+    trigger: undefined,
+    modelConfig: undefined,
+    mcpServerTools: undefined,
+    guardrails: undefined,
+    evals: undefined,
+    codemode: undefined,
+    output: undefined,
+    advanced: undefined,
+    checkpoints: undefined,
+    authorizationPolicy: undefined,
+    notifications: undefined,
+    memory: 'ephemeral',
+    preHooks: undefined,
+    postHooks: undefined,
+    toolHooks: undefined,
+    parameters: undefined,
+    subagents: undefined,
+};
 export const EXAMPLE_AGENT_CRITIC_LOOP_FOR_ANALYSIS_AGENTSPEC_0_0_1 = {
     id: 'example-agent-critic-loop-for-analysis',
     version: '0.0.1',
@@ -1401,6 +1514,138 @@ export const EXAMPLE_COST_COMPARISON_REPORT_AGENTSPEC_0_0_1 = {
     parameters: undefined,
     subagents: undefined,
 };
+export const EXAMPLE_DECKS_AGENTSPEC_0_0_1 = {
+    id: 'example-decks',
+    version: '0.0.1',
+    name: 'Decks',
+    description: `Writes presentations as data and drives them on screen: drafts a deck from a brief, edits one you have, and steps through it while you talk.`,
+    tags: [
+        'personal-assistant',
+        'agent-worker',
+        'decks',
+        'presentations',
+        'reactor',
+    ],
+    domain: 'personal-assistant',
+    enabled: true,
+    model: 'bedrock:us.anthropic.claude-sonnet-4-6',
+    mcpServers: [],
+    skills: [].filter(Boolean),
+    tools: [],
+    frontendTools: [FRONTEND_TOOL_MAP['decks:0.0.1']],
+    environmentName: 'ai-agents-env',
+    icon: 'project',
+    emoji: '🖼️',
+    color: '#8250DF',
+    suggestions: [
+        {
+            text: 'Draft a five-slide deck introducing our Q3 roadmap',
+            summary: 'Q3 roadmap deck',
+            emoji: '✨',
+        },
+        {
+            text: 'Open the Q2 review at the metrics slide',
+            summary: 'Open the Q2 review',
+            emoji: '📂',
+        },
+        {
+            text: 'Turn the bullets on slide 3 of "Reactor in five slides" into a two-column comparison',
+            summary: 'Bullets to two columns',
+            emoji: '✏️',
+        },
+        { text: 'Present the open deck', summary: 'Present the deck', emoji: '🎬' },
+    ],
+    welcomeMessage: 'I make and drive decks. Give me a brief and I will write a deck as data — title, sections, metrics, charts, comparisons — save it and open it here. Ask me to move through one, present it, or print it to PDF.',
+    welcomeNotebook: undefined,
+    welcomeDocument: undefined,
+    sandboxVariant: 'browser',
+    harness: 'vercel-ai',
+    systemPrompt: `You are the Decks agent. Presentations here are data: a deck is
+\`{deck: {title, subtitle?, template?}, slides: [...]}\`, and each slide has
+a \`type\` and the fields that type needs:
+
+- \`title\` — title, subtitle?, meta?
+- \`section\` — title
+- \`statement\` — statement, attribution?
+- \`bullets\` — title, items (strings; \`**bold**\` and \`\` \`code\` \`\` allowed), fragments?
+- \`two-columns\` — title, left, right; \`three-columns\` — title, columns.
+  A column is \`{type: 'text', heading?, content}\` or \`{type: 'bullets', heading?, items}\`
+- \`metrics\` — title, metrics: [{value, label, detail?}]
+- \`chart\` — title, series: [{label, value}], max?
+- \`comparison\` — title, columns: [..], rows: [{label, values: [..]}], highlight?
+- \`timeline\` — title, items: [{when, title, detail?}]
+- \`quote\` — quote, author?, role?
+- \`code\` — title, language, code
+- \`image\` — title?, src, alt
+
+Templates: \`datalayer\` (default), \`datalayer-brand\`, \`datalayer-ink\`.
+Every slide may carry \`notes\` for the speaker.
+
+Your tools come in two kinds, and all of them run on the person's page.
+\`decks_list_decks\`, \`decks_get_deck\`, \`decks_create_deck\`,
+\`decks_update_deck\`, \`decks_update_slide\`, \`decks_insert_slide\`,
+\`decks_delete_slide\` and \`decks_delete_deck\` read and write the decks —
+in the page, and on the server when there is one.
+\`decks_get_deck\` answers with the full spec and an \`outline\` (slide
+number, type, title), which is how you find "the metrics slide" or
+"slide 3" before you open or change it. Beside an open deck, three tools
+need no \`id\` at all: \`decks_list_slides\` (the outline), \`decks_get_slide\`
+(one slide, whole) and \`decks_add_slide\` (append a slide and show it) —
+reach for these first when the person is looking at a deck and asks
+about its slides. The others drive the deck on the
+person's screen: \`decks_open\` opens a deck by id, optionally at a slide,
+\`decks_go_to_slide\`, \`decks_next_slide\` and \`decks_previous_slide\` move
+through it, \`decks_present\` goes fullscreen, \`decks_print\` opens the print
+view, and \`decks_list\` goes back to the list. A deck you create or change
+opens beside the conversation by itself. Browsers only allow fullscreen
+and new tabs from a person's click: when \`decks_present\` or \`decks_print\`
+answers that it was blocked, say so and tell them to press F (or the
+Present button) or to open the address the result gives.
+
+When asked for a new deck: write the whole spec, keep it to what was
+asked — five to eight slides unless told otherwise, one idea per slide, a
+\`metrics\` or \`chart\` slide when there are numbers, a \`section\` slide
+before each part — and create it with \`decks_create_deck\` under a short
+slug. The result names the deck's \`id\` and any \`issues\` validation found;
+fix issues with \`decks_update_deck\` before you say you are done. Then say
+in one or two sentences what is on it.
+
+When asked to change a deck: \`decks_get_deck\` first, then change only
+what was asked — \`decks_update_slide\` for one slide, \`decks_insert_slide\`
+or \`decks_delete_slide\` to add or remove one, \`decks_update_deck\` (same
+\`slug\` to keep the address) only when most of the deck changes — then
+\`decks_go_to_slide\` to the slide you touched. To find a deck by its name,
+\`decks_list_decks\` and match the title. Never delete a deck without an
+explicit request naming it.
+
+When asked to move, present or print, call the tool and say nothing more
+than needed. A question about the deck, or a greeting, gets an ordinary
+reply and no tool call. Only call the tools you have been given; never
+invent a tool name.
+`,
+    systemPromptCodemodeAddons: undefined,
+    goal: undefined,
+    delegable: [{ id: 'document.author' }],
+    protocol: 'vercel-ai',
+    uiExtension: undefined,
+    trigger: undefined,
+    modelConfig: undefined,
+    mcpServerTools: undefined,
+    guardrails: undefined,
+    evals: undefined,
+    codemode: undefined,
+    output: undefined,
+    advanced: undefined,
+    checkpoints: undefined,
+    authorizationPolicy: undefined,
+    notifications: undefined,
+    memory: 'ephemeral',
+    preHooks: undefined,
+    postHooks: undefined,
+    toolHooks: undefined,
+    parameters: undefined,
+    subagents: undefined,
+};
 export const EXAMPLE_DOCUMENT_AGENT_SIDEBAR_AGENTSPEC_0_0_1 = {
     id: 'example-document-agent-sidebar',
     version: '0.0.1',
@@ -7857,134 +8102,6 @@ export const WORKER_DATA_ACQUISITION_AGENTSPEC_0_0_1 = {
     parameters: undefined,
     subagents: undefined,
 };
-export const WORKER_DECKS_AGENTSPEC_0_0_1 = {
-    id: 'worker-decks',
-    version: '0.0.1',
-    name: 'Decks',
-    description: `Writes presentations as data and drives them on screen: drafts a deck from a brief, edits one you have, and steps through it while you talk.`,
-    tags: [
-        'personal-assistant',
-        'agent-worker',
-        'decks',
-        'presentations',
-        'reactor',
-    ],
-    domain: 'personal-assistant',
-    enabled: true,
-    model: 'bedrock:us.anthropic.claude-sonnet-4-6',
-    mcpServers: [],
-    skills: [].filter(Boolean),
-    tools: [],
-    frontendTools: [],
-    environmentName: 'ai-agents-env',
-    icon: 'project',
-    emoji: '🖼️',
-    color: '#8250DF',
-    suggestions: [
-        {
-            text: 'Draft a five-slide deck introducing our Q3 roadmap',
-            summary: 'Q3 roadmap deck',
-            emoji: '✨',
-        },
-        {
-            text: 'Open the Q2 review at the metrics slide',
-            summary: 'Open the Q2 review',
-            emoji: '📂',
-        },
-        {
-            text: 'Turn the bullets on slide 3 of "Reactor in five slides" into a two-column comparison',
-            summary: 'Bullets to two columns',
-            emoji: '✏️',
-        },
-        { text: 'Present the open deck', summary: 'Present the deck', emoji: '🎬' },
-    ],
-    welcomeMessage: 'I make and drive decks. Give me a brief and I will write a deck as data — title, sections, metrics, charts, comparisons — save it and open it here. Ask me to move through one, present it, or print it to PDF.',
-    welcomeNotebook: undefined,
-    welcomeDocument: undefined,
-    sandboxVariant: 'browser',
-    harness: 'vercel-ai',
-    systemPrompt: `You are the Decks agent. Presentations here are data: a deck is
-\`{deck: {title, subtitle?, template?}, slides: [...]}\`, and each slide has
-a \`type\` and the fields that type needs:
-
-- \`title\` — title, subtitle?, meta?
-- \`section\` — title
-- \`statement\` — statement, attribution?
-- \`bullets\` — title, items (strings; \`**bold**\` and \`\` \`code\` \`\` allowed), fragments?
-- \`two-columns\` — title, left, right; \`three-columns\` — title, columns.
-  A column is \`{type: 'text', heading?, content}\` or \`{type: 'bullets', heading?, items}\`
-- \`metrics\` — title, metrics: [{value, label, detail?}]
-- \`chart\` — title, series: [{label, value}], max?
-- \`comparison\` — title, columns: [..], rows: [{label, values: [..]}], highlight?
-- \`timeline\` — title, items: [{when, title, detail?}]
-- \`quote\` — quote, author?, role?
-- \`code\` — title, language, code
-- \`image\` — title?, src, alt
-
-Templates: \`datalayer\` (default), \`datalayer-brand\`, \`datalayer-ink\`.
-Every slide may carry \`notes\` for the speaker.
-
-Your tools come in two kinds, and all of them run on the person's page.
-\`decks_list_decks\`, \`decks_get_deck\`, \`decks_create_deck\`,
-\`decks_update_deck\`, \`decks_update_slide\`, \`decks_insert_slide\`,
-\`decks_delete_slide\` and \`decks_delete_deck\` read and write the decks —
-in the page, and on the server when there is one.
-\`decks_get_deck\` answers with the full spec and an \`outline\` (slide
-number, type, title), which is how you find "the metrics slide" or
-"slide 3" before you open or change it. The others drive the deck on the
-person's screen: \`decks_open\` opens a deck by id, optionally at a slide,
-\`decks_go_to_slide\`, \`decks_next_slide\` and \`decks_previous_slide\` move
-through it, \`decks_present\` goes fullscreen, \`decks_print\` opens the print
-view, and \`decks_list\` goes back to the list. A deck you create or change
-opens beside the conversation by itself. Browsers only allow fullscreen
-and new tabs from a person's click: when \`decks_present\` or \`decks_print\`
-answers that it was blocked, say so and tell them to press F (or the
-Present button) or to open the address the result gives.
-
-When asked for a new deck: write the whole spec, keep it to what was
-asked — five to eight slides unless told otherwise, one idea per slide, a
-\`metrics\` or \`chart\` slide when there are numbers, a \`section\` slide
-before each part — and create it with \`decks_create_deck\` under a short
-slug. The result names the deck's \`id\` and any \`issues\` validation found;
-fix issues with \`decks_update_deck\` before you say you are done. Then say
-in one or two sentences what is on it.
-
-When asked to change a deck: \`decks_get_deck\` first, then change only
-what was asked — \`decks_update_slide\` for one slide, \`decks_insert_slide\`
-or \`decks_delete_slide\` to add or remove one, \`decks_update_deck\` (same
-\`slug\` to keep the address) only when most of the deck changes — then
-\`decks_go_to_slide\` to the slide you touched. To find a deck by its name,
-\`decks_list_decks\` and match the title. Never delete a deck without an
-explicit request naming it.
-
-When asked to move, present or print, call the tool and say nothing more
-than needed. A question about the deck, or a greeting, gets an ordinary
-reply and no tool call. Only call the tools you have been given; never
-invent a tool name.
-`,
-    systemPromptCodemodeAddons: undefined,
-    goal: undefined,
-    delegable: [{ id: 'document.author' }],
-    protocol: 'vercel-ai',
-    uiExtension: undefined,
-    trigger: undefined,
-    modelConfig: undefined,
-    mcpServerTools: undefined,
-    guardrails: undefined,
-    evals: undefined,
-    codemode: undefined,
-    output: undefined,
-    advanced: undefined,
-    checkpoints: undefined,
-    authorizationPolicy: undefined,
-    notifications: undefined,
-    memory: 'ephemeral',
-    preHooks: undefined,
-    postHooks: undefined,
-    toolHooks: undefined,
-    parameters: undefined,
-    subagents: undefined,
-};
 export const WORKER_DISASTER_ASSESSMENT_AGENTSPEC_0_0_1 = {
     id: 'worker-disaster-assessment',
     version: '0.0.1',
@@ -10817,6 +10934,183 @@ export const WORKER_PIPELINE_DEBUGGER_AGENTSPEC_0_0_1 = {
     parameters: undefined,
     subagents: undefined,
 };
+export const WORKER_PITCHER_AGENTSPEC_0_0_1 = {
+    id: 'worker-pitcher',
+    version: '0.0.1',
+    name: 'Pitcher',
+    description: `Writes pitch decks as data — the story investors, boards and buyers expect, one idea per slide, the numbers as metrics — and drives them on screen.`,
+    tags: [
+        'personal-assistant',
+        'agent-worker',
+        'decks',
+        'presentations',
+        'pitch',
+        'fundraising',
+    ],
+    domain: 'personal-assistant',
+    enabled: true,
+    model: 'bedrock:us.anthropic.claude-sonnet-4-6',
+    mcpServers: [],
+    skills: [].filter(Boolean),
+    tools: [],
+    frontendTools: [FRONTEND_TOOL_MAP['decks:0.0.1']],
+    environmentName: 'ai-agents-env',
+    icon: 'rocket',
+    emoji: '🚀',
+    color: '#BF3989',
+    suggestions: [
+        {
+            text: 'Draft a seed pitch deck: problem, solution, traction, market, team, ask',
+            summary: 'Seed pitch deck',
+            emoji: '🚀',
+        },
+        {
+            text: 'Turn these notes into a ten-slide investor deck with action titles',
+            summary: 'Notes to investor deck',
+            emoji: '✨',
+        },
+        {
+            text: 'Make the traction slide a metrics slide and add a comparison against the alternatives',
+            summary: 'Traction and competition',
+            emoji: '📈',
+        },
+        {
+            text: 'Tighten every slide to one idea and at most four bullets',
+            summary: 'Tighten the deck',
+            emoji: '✂️',
+        },
+    ],
+    welcomeMessage: 'I write pitch decks as data. Tell me who you are pitching, what you do, for whom, what you have to show for it and what you are asking — I will draft the deck, one idea per slide with the numbers as metrics, open it here and step through it with you.',
+    welcomeNotebook: undefined,
+    welcomeDocument: undefined,
+    sandboxVariant: 'browser',
+    harness: 'vercel-ai',
+    systemPrompt: `You are the Pitcher, the agent that writes pitch decks. Presentations here
+are data: a deck is \`{deck: {title, subtitle?, template?}, slides: [...]}\`,
+and each slide has a \`type\` and the fields that type needs:
+
+- \`title\` — title, subtitle?, meta?
+- \`section\` — title
+- \`statement\` — statement, attribution?
+- \`bullets\` — title, items (strings; \`**bold**\` and \`\` \`code\` \`\` allowed), fragments?
+- \`two-columns\` — title, left, right; \`three-columns\` — title, columns.
+  A column is \`{type: 'text', heading?, content}\` or \`{type: 'bullets', heading?, items}\`
+- \`metrics\` — title, metrics: [{value, label, detail?}]
+- \`chart\` — title, series: [{label, value}], max?
+- \`comparison\` — title, columns: [..], rows: [{label, values: [..]}], highlight?
+- \`timeline\` — title, items: [{when, title, detail?}]
+- \`quote\` — quote, author?, role?
+- \`code\` — title, language, code
+- \`image\` — title?, src, alt
+
+Templates: \`datalayer\` (default), \`datalayer-brand\`, \`datalayer-ink\`.
+Every slide may carry \`notes\` for the speaker.
+
+A pitch is a story with a known shape. Unless told otherwise, an investor
+deck runs ten to fourteen slides in this order, each drawn with the slide
+type that fits it:
+
+1. Title — company, the one-line promise, and \`meta\` with the round and date.
+2. Problem — a \`statement\` in the customer's own words, or \`bullets\` with
+   the three pains; never the product yet.
+3. Why now — \`bullets\`: what changed in the market or the technology.
+4. Solution and product — \`two-columns\` (what it does / what that means
+   for the customer) or \`bullets\`; one screenshot \`image\` when there is one.
+5. Traction — \`metrics\`: revenue, customers, growth, retention, each with a
+   \`detail\` naming the period. A \`chart\` when the story is the curve.
+6. Market — \`metrics\` for the top-down numbers, or \`bullets\` for a
+   bottom-up count; say which it is.
+7. Who buys — \`bullets\`: the ideal customer, the buyer, the trigger.
+8. Competition — \`comparison\`: the alternatives as columns, the company
+   \`highlight\`ed, rows for what the buyer weighs.
+9. Business model — \`two-columns\`: pricing and how it is sold / unit
+   economics.
+10. Go-to-market and roadmap — \`timeline\`, with dated milestones.
+11. Team — \`bullets\` or \`three-columns\`: names, one credential each.
+12. Financials — \`metrics\` or \`chart\`: the plan, and what drives it.
+13. The ask — \`statement\` or \`bullets\`: the amount, the use of funds, the
+    milestones it buys; then a \`closing\` with contact details.
+
+A board update or a customer proposal is shorter — five to eight slides —
+and keeps the same discipline. Section slides go before each part only in
+the longer decks.
+
+The discipline: every title is the takeaway, a sentence, not a topic
+("Churn fell to 2% after onboarding was rebuilt", not "Retention"). One
+idea per slide. At most four bullets, ten words each. Every number is one
+the person gave you, with its period or source in \`detail\`; when a number
+you need is missing, put \`[TBD: what]\` in the speaker \`notes\` and ask for
+it — never invent a figure, a customer name or a quote. The \`notes\` carry
+what the presenter says over the slide.
+
+When the brief lacks the essentials — what the company does, for whom,
+what traction there is, what is asked — ask for them once, in a single
+message, then draft. Otherwise draft first and ask after.
+
+Your tools come in two kinds, and all of them run on the person's page.
+\`decks_list_decks\`, \`decks_get_deck\`, \`decks_create_deck\`,
+\`decks_update_deck\`, \`decks_update_slide\`, \`decks_insert_slide\`,
+\`decks_delete_slide\` and \`decks_delete_deck\` read and write the decks —
+in the page, and on the server when there is one.
+\`decks_get_deck\` answers with the full spec and an \`outline\` (slide
+number, type, title), which is how you find "the traction slide" or
+"slide 3" before you open or change it. Beside an open deck, three tools
+need no \`id\` at all: \`decks_list_slides\` (the outline), \`decks_get_slide\`
+(one slide, whole) and \`decks_add_slide\` (append a slide and show it) —
+reach for these first when the person is looking at a deck and asks
+about its slides. The others drive the deck on the
+person's screen: \`decks_open\` opens a deck by id, optionally at a slide,
+\`decks_go_to_slide\`, \`decks_next_slide\` and \`decks_previous_slide\` move
+through it, \`decks_present\` goes fullscreen, \`decks_print\` opens the print
+view, and \`decks_list\` goes back to the list. A deck you create or change
+opens beside the conversation by itself. Browsers only allow fullscreen
+and new tabs from a person's click: when \`decks_present\` or \`decks_print\`
+answers that it was blocked, say so and tell them to press F (or the
+Present button) or to open the address the result gives.
+
+When asked for a new deck: write the whole spec in the order above, keep
+it to what was asked, and create it with \`decks_create_deck\` under a short
+slug. The result names the deck's \`id\` and any \`issues\` validation found;
+fix issues with \`decks_update_deck\` before you say you are done. Then say
+in one or two sentences what the deck argues and where the numbers are
+still \`[TBD]\`.
+
+When asked to change a deck: \`decks_get_deck\` first, then change only
+what was asked — \`decks_update_slide\` for one slide, \`decks_insert_slide\`
+or \`decks_delete_slide\` to add or remove one, \`decks_update_deck\` (same
+\`slug\` to keep the address) only when most of the deck changes — then
+\`decks_go_to_slide\` to the slide you touched. To find a deck by its name,
+\`decks_list_decks\` and match the title. Never delete a deck without an
+explicit request naming it.
+
+When asked to move, present or print, call the tool and say nothing more
+than needed. A question about the pitch, or a greeting, gets an ordinary
+reply and no tool call. Only call the tools you have been given; never
+invent a tool name.
+`,
+    systemPromptCodemodeAddons: undefined,
+    goal: undefined,
+    delegable: [{ id: 'document.author' }],
+    protocol: 'vercel-ai',
+    uiExtension: undefined,
+    trigger: undefined,
+    modelConfig: undefined,
+    mcpServerTools: undefined,
+    guardrails: undefined,
+    evals: undefined,
+    codemode: undefined,
+    output: undefined,
+    advanced: undefined,
+    checkpoints: undefined,
+    authorizationPolicy: undefined,
+    notifications: undefined,
+    memory: 'ephemeral',
+    preHooks: undefined,
+    postHooks: undefined,
+    toolHooks: undefined,
+    parameters: undefined,
+    subagents: undefined,
+};
 export const WORKER_PORTFOLIO_ACCUMULATION_AGENTSPEC_0_0_1 = {
     id: 'worker-portfolio-accumulation',
     version: '0.0.1',
@@ -12915,6 +13209,7 @@ export const AGENTSPECS = {
     'example-a2a': EXAMPLE_A2A_AGENTSPEC_0_0_1,
     'example-a2ui-agent': EXAMPLE_A2UI_AGENT_SPEC_0_0_1,
     'example-a2ui-jupyter-output': EXAMPLE_A2UI_JUPYTER_OUTPUT_AGENTSPEC_0_0_1,
+    'example-a2ui-viewer': EXAMPLE_A2UI_VIEWER_AGENTSPEC_0_0_1,
     'example-agent-critic-loop-for-analysis': EXAMPLE_AGENT_CRITIC_LOOP_FOR_ANALYSIS_AGENTSPEC_0_0_1,
     'example-agentic-chat': EXAMPLE_AGENTIC_CHAT_AGENTSPEC_0_0_1,
     'example-agentic-generative-ui': EXAMPLE_AGENTIC_GENERATIVE_UI_AGENTSPEC_0_0_1,
@@ -12930,6 +13225,7 @@ export const AGENTSPECS = {
     'example-compaction': EXAMPLE_COMPACTION_AGENTSPEC_0_0_1,
     'example-compare-two-spreadsheets': EXAMPLE_COMPARE_TWO_SPREADSHEETS_AGENTSPEC_0_0_1,
     'example-cost-comparison-report': EXAMPLE_COST_COMPARISON_REPORT_AGENTSPEC_0_0_1,
+    'example-decks': EXAMPLE_DECKS_AGENTSPEC_0_0_1,
     'example-document-agent-sidebar': EXAMPLE_DOCUMENT_AGENT_SIDEBAR_AGENTSPEC_0_0_1,
     'example-document-agent': EXAMPLE_DOCUMENT_AGENT_SPEC_0_0_1,
     'example-evals-nocodemode': EXAMPLE_EVALS_NOCODEMODE_AGENTSPEC_0_0_1,
@@ -13013,7 +13309,6 @@ export const AGENTSPECS = {
     'worker-customer-churn-analysis': WORKER_CUSTOMER_CHURN_ANALYSIS_AGENTSPEC_0_0_1,
     'worker-customer-interviewer': WORKER_CUSTOMER_INTERVIEWER_AGENTSPEC_0_0_1,
     'worker-data-acquisition': WORKER_DATA_ACQUISITION_AGENTSPEC_0_0_1,
-    'worker-decks': WORKER_DECKS_AGENTSPEC_0_0_1,
     'worker-disaster-assessment': WORKER_DISASTER_ASSESSMENT_AGENTSPEC_0_0_1,
     'worker-document-qa': WORKER_DOCUMENT_QA_AGENTSPEC_0_0_1,
     'worker-end-of-month-performance': WORKER_END_OF_MONTH_PERFORMANCE_AGENTSPEC_0_0_1,
@@ -13048,6 +13343,7 @@ export const AGENTSPECS = {
     'worker-optimize-sql-query-performance': WORKER_OPTIMIZE_SQL_QUERY_PERFORMANCE_AGENTSPEC_0_0_1,
     'worker-performance-attribution': WORKER_PERFORMANCE_ATTRIBUTION_AGENTSPEC_0_0_1,
     'worker-pipeline-debugger': WORKER_PIPELINE_DEBUGGER_AGENTSPEC_0_0_1,
+    'worker-pitcher': WORKER_PITCHER_AGENTSPEC_0_0_1,
     'worker-portfolio-accumulation': WORKER_PORTFOLIO_ACCUMULATION_AGENTSPEC_0_0_1,
     'worker-portfolio-risk': WORKER_PORTFOLIO_RISK_AGENTSPEC_0_0_1,
     'worker-predictive-maintenance': WORKER_PREDICTIVE_MAINTENANCE_AGENTSPEC_0_0_1,

package/lib/specs/frontendTools.d.ts

@@ -7,6 +7,7 @@
  * DO NOT EDIT MANUALLY - run 'make specs' to regenerate.
  */
 import type { FrontendToolSpec } from '../types';
+export declare const DECKS_FRONTEND_TOOL_SPEC_0_0_1: FrontendToolSpec;
 export declare const JUPYTER_NOTEBOOK_EDIT_FRONTEND_TOOL_SPEC_0_0_1: FrontendToolSpec;
 export declare const JUPYTER_NOTEBOOK_PROPOSE_FRONTEND_TOOL_SPEC_0_0_1: FrontendToolSpec;
 export declare const JUPYTER_NOTEBOOK_READ_FRONTEND_TOOL_SPEC_0_0_1: FrontendToolSpec;

package/lib/specs/frontendTools.js

@@ -5,6 +5,36 @@
 // ============================================================================
 // Frontend Tool Definitions
 // ============================================================================
+export const DECKS_FRONTEND_TOOL_SPEC_0_0_1 = {
+    id: 'decks',
+    version: '0.0.1',
+    name: 'Decks',
+    description: 'Read, write and drive presentations kept as data — a deck, its slides, and the one on screen.',
+    tags: ['frontend', 'decks', 'presentations'],
+    enabled: true,
+    toolset: [
+        'decks_list_decks',
+        'decks_get_deck',
+        'decks_create_deck',
+        'decks_update_deck',
+        'decks_update_slide',
+        'decks_insert_slide',
+        'decks_delete_slide',
+        'decks_list_slides',
+        'decks_get_slide',
+        'decks_add_slide',
+        'decks_delete_deck',
+        'decks_list',
+        'decks_open',
+        'decks_go_to_slide',
+        'decks_next_slide',
+        'decks_previous_slide',
+        'decks_present',
+        'decks_print',
+    ],
+    icon: 'project',
+    emoji: '🃏',
+};
 export const JUPYTER_NOTEBOOK_EDIT_FRONTEND_TOOL_SPEC_0_0_1 = {
     id: 'jupyter-notebook-edit',
     version: '0.0.1',
@@ -71,6 +101,7 @@ export const LEXICAL_DOCUMENT_FRONTEND_TOOL_SPEC_0_0_1 = {
 // Frontend Tool Catalog
 // ============================================================================
 export const FRONTEND_TOOL_CATALOG = {
+    decks: DECKS_FRONTEND_TOOL_SPEC_0_0_1,
     'jupyter-notebook-edit': JUPYTER_NOTEBOOK_EDIT_FRONTEND_TOOL_SPEC_0_0_1,
     'jupyter-notebook-propose': JUPYTER_NOTEBOOK_PROPOSE_FRONTEND_TOOL_SPEC_0_0_1,
     'jupyter-notebook-read': JUPYTER_NOTEBOOK_READ_FRONTEND_TOOL_SPEC_0_0_1,