CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-graphs

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.

64

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/agentcontrol/agent-graphs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with a well-structured workflow and good verification steps. Its main weakness is verbosity — the 'Core Concepts', 'When to Use', and 'Core Principles' sections explain things Claude already knows or can infer, consuming tokens without adding operational value. The concrete JSON example and clear tool-to-step mapping are strong points.

Suggestions

Remove or drastically condense the 'Core Concepts' and 'When to Use Agent Graphs' sections — Claude understands directed graphs and routing patterns; focus on LaunchDarkly-specific details only.

Trim the 'Core Principles' section to a brief inline note or remove it entirely — principles like 'One Agent, One Job' are general software design advice Claude already knows.

DimensionReasoningScore

Conciseness

The skill includes some unnecessary sections like 'Core Concepts' explaining what agent graphs are and 'When to Use Agent Graphs' — Claude can infer these from context. The 'Core Principles' section is mostly platitudes ('Design Before Building', 'One Agent, One Job'). However, the workflow steps and JSON example are reasonably tight.

2 / 3

Actionability

Provides a concrete JSON example for graph creation that is copy-paste ready with realistic field values. MCP tool names are explicitly listed with their purposes, and the workflow steps specify exactly which tools to call at each stage.

3 / 3

Workflow Clarity

The 4-step workflow is clearly sequenced (Design → Ensure Nodes Exist → Create Graph → Verify) with an explicit verification step that includes specific checks (edge connections, root config, handoff data). The edge cases table handles error scenarios and the 'What NOT to Do' section adds guardrails.

3 / 3

Progressive Disclosure

The content is a single monolithic file with no references to external files, which is acceptable given no bundle exists. However, the 'Core Concepts' and 'When to Use' sections add ~40 lines of context that could be trimmed or separated, and the file is long enough (~130 lines) that some content could benefit from being split out.

2 / 3

Total

10

/

12

Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-structured with a clear 'Use when' clause and targets a distinct niche, making it strong on completeness and distinctiveness. However, it could benefit from more specific concrete actions beyond 'create and manage' and broader trigger term coverage to capture more natural user phrasings.

Suggestions

List more specific actions such as 'add/remove nodes, configure edges, define handoff conditions, visualize graph topology' to improve specificity.

Add natural trigger term variations like 'orchestration', 'agent routing', 'workflow DAG', 'agent pipeline' to improve discoverability.

DimensionReasoningScore

Specificity

Names the domain (agent graphs) and some actions ('create and manage'), and describes the structure ('directed graphs of configs connected by edges with handoff logic'), but doesn't list multiple concrete actions like editing edges, adding nodes, configuring handoff conditions, etc.

2 / 3

Completeness

Clearly answers both 'what' (create and manage agent graphs — directed graphs of configs connected by edges with handoff logic) and 'when' (Use when building multi-agent workflows where configs route to each other), with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Includes relevant terms like 'agent graphs', 'multi-agent workflows', 'handoff logic', 'configs', and 'edges', but misses common variations users might say such as 'orchestration', 'agent routing', 'agent pipeline', 'workflow graph', or 'DAG'.

2 / 3

Distinctiveness Conflict Risk

The description targets a very specific niche — agent graphs with directed edges and handoff logic for multi-agent workflows. This is unlikely to conflict with general coding, workflow, or configuration skills due to its specialized terminology.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
launchdarkly/ai-tooling
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.