---
name: agent-graphs
description: "Create and manage agent graphs — directed graphs of configs connected by edges with handoff logic. Use when building multi-agent workflows where configs route to each other."
license: Apache-2.0
compatibility: Requires the remotely hosted LaunchDarkly MCP server
metadata:
  author: launchdarkly
  version: "0.1.0"
title: agent-graphs
canonical_url: https://skilld.dev/gh/launchdarkly/ai-tooling/agent-graphs
last_updated: 2026-11-12T08:16:54.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install launchdarkly/ai-tooling/agent-graphs`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/agent-graphs`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/launchdarkly/ai-tooling/agent-graphs) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/agent-graphs`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/agent-graphs --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/agent-graphs --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Config Agent Graphs

You're using a skill that will guide you through creating and managing agent graphs in LaunchDarkly. Your job is to design the graph topology, create it with the right edges and handoffs, and verify the routing between config nodes.

## Prerequisites

This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment.

**Required MCP tools:**
- `create-agent-graph` -- create a new graph with nodes and edges
- `get-agent-graphs` -- browse existing graphs in the project; with `graphKey`, inspect one graph's structure and edges

**Optional MCP tools:**
- `update-agent-graph` -- modify edges, root config, or description
- `delete-agent-graph` -- permanently remove a graph
- `get-agent-configs` -- inspect individual configs that serve as nodes
- `create-agent-config` (`resource: "config"`) -- create new configs to use as graph nodes

## Core Concepts

### What Are Agent Graphs?

An agent graph is a directed graph where:
- **Nodes** are configs (each config is an agent with its own model, prompt, and tools)
- **Edges** define routing between configs (source -> target)
- **Handoff data** on edges controls how context is passed between agents
- **Root config** is the entry point — the first agent that receives user input

### When to Use Agent Graphs

| Scenario | Example |
|----------|---------|
| **Multi-step workflows** | Triage agent -> Specialist agent -> Summary agent |
| **Routing by intent** | Router agent decides which specialist handles the request |
| **Escalation chains** | L1 support -> L2 support -> Human handoff |
| **Pipeline processing** | Extract -> Transform -> Validate -> Store |

### Graph Structure

```
[Root Config] --edge--> [Config A] --edge--> [Config C]
                  \--edge--> [Config B]
```

Each edge has:
- `key` -- unique identifier for the edge
- `sourceConfig` -- the config key that routes FROM
- `targetConfig` -- the config key that routes TO
- `handoff` (optional) -- data/instructions passed during the transition

## Core Principles

1. **Design Before Building**: Map out nodes and edges on paper/whiteboard first
2. **One Agent, One Job**: Each node should have a clear, focused responsibility
3. **Root Config Is the Router**: The entry point should understand how to dispatch
4. **Handoff Data Matters**: Define what context flows between agents
5. **Verify the Full Path**: Test that routing works end-to-end

## Workflow

### Step 1: Design the Graph

Before creating anything:

1. Identify the agents (configs) needed — each is a graph node
2. Map the routing: which agent hands off to which?
3. Define handoff data: what context does each edge carry?
4. Identify the root config: which agent receives initial input?
5. Check existing graphs with `get-agent-graphs` to avoid duplicates
6. Check existing configs with `get-agent-configs` to see what nodes already exist

### Step 2: Ensure Nodes Exist

Each node in the graph must be an existing config. If configs don't exist yet:
1. Use `create-agent-config` with `resource: "config"` to create each agent config
2. Set up variations with appropriate models and prompts for each agent's role (`resource: "variation"`, or pass the first variation's fields in the same call)
3. Verify each config exists with `get-agent-configs`

### Step 3: Create the Graph

Use `create-agent-graph` with:
- `projectKey` -- the project containing the configs
- `key` -- unique identifier for the graph
- `name` -- human-readable display name
- `description` (optional) -- explain the graph's purpose
- `rootConfigKey` -- the entry-point config key
- `edges` -- array of connections between configs

```json
{
  "projectKey": "my-project",
  "key": "support-triage-graph",
  "name": "Customer Support Triage",
  "description": "Routes customer queries to the appropriate specialist agent",
  "rootConfigKey": "triage-agent",
  "edges": [
    {
      "key": "triage-to-billing",
      "sourceConfig": "triage-agent",
      "targetConfig": "billing-specialist",
      "handoff": {"category": "billing", "priority": "normal"}
    },
    {
      "key": "triage-to-technical",
      "sourceConfig": "triage-agent",
      "targetConfig": "technical-specialist",
      "handoff": {"category": "technical", "priority": "normal"}
    }
  ]
}
```

### Step 4: Verify

1. Use `get-agent-graphs` to confirm the graph was created with the correct structure
2. Verify edges connect the right source and target configs
3. Check that the root config key matches the intended entry point
4. Confirm handoff data is present on edges that need it

**Report results:**
- Graph created with N nodes and M edges
- Root config set correctly
- All edges verified

## Edge Cases

| Situation | Action |
|-----------|--------|
| Config doesn't exist yet | Create it first with `create-agent-config` before referencing in a graph |
| Circular routing | Allowed but warn user — ensure there's a termination condition in the agent logic |
| Single-node graph | Valid but unusual — consider if a graph is actually needed |
| Updating edges | Use `update-agent-graph` with `confirm: true` — provide the complete new edge list |

## What NOT to Do

- Don't create a graph before the config nodes exist
- Don't forget handoff data when agents need context from predecessors
- Don't create overly complex graphs — start simple and add nodes as needed
- Don't delete a graph without understanding if it's actively used in agent workflows

## Other Resources

To learn more, read [Agent graphs](https://launchdarkly.com/docs/home/agentcontrol/agent-graphs.md).
