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.

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/agentcontrol/agent-graphs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

A well-structured, actionable instruction-only skill with concrete MCP tool guidance, a complete JSON example, and an explicit verification step. It sits just below the top band due to mild section redundancy, one vague sub-step, the absence of a retry feedback loop, and no progressive split into bundle files.

Suggestions

Tighten redundancy: fold "Core Principles" into the workflow steps or "When to Use" so each idea appears once.

Make Step 2 concrete by specifying the create-ai-config parameters and what a "variation" entails, or link to a reference for config creation.

Add an explicit feedback loop to Step 4, e.g. "If get-agent-graph shows a wrong edge, update via update-agent-graph and re-verify before reporting."

DimensionReasoningScore

Conciseness

The body is efficient and the product-specific model explanation is earned, but the "Core Principles" section restates the workflow and overlaps with "When to Use", leaving minor trimmable redundancy.

4 / 5

Actionability

Named MCP tools with full parameter lists and a copy-paste JSON example make the core flow executable, but Step 2's "Set up variations with appropriate models and prompts" is vague, a minor gap.

4 / 5

Workflow Clarity

A clear 4-step sequence ends in a dedicated Verify step with four concrete checks, but there is no explicit validate→fix→retry feedback loop, which the top anchor requires.

4 / 5

Progressive Disclosure

Sections are well-organized with one clearly signaled external doc link and no nested references, but all content is inline in a ~145-line file with no split into separate reference files.

4 / 5

Total

16

/

20

Passed

Description

70%Weight 40%Scale 1-5

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

A solid description with a clear explicit "Use when" trigger and a named domain, held back by generic action verbs and limited keyword variety. It is distinct enough but could add synonyms and a richer trigger list to reach the top band.

Suggestions

Replace the generic "manage" with more concrete verbs (e.g., "inspect, update, and verify routing between configs") to lift specificity.

Add common synonyms to the trigger phrase, e.g. "Use when building multi-agent workflows, agent orchestration, or routing/chaining between configs".

Expand the "when" clause with multiple concrete triggers (e.g., "…or when the user mentions agent routing, escalation chains, or pipeline processing").

DimensionReasoningScore

Specificity

The description names the domain ("agent graphs") and two actions ("Create and manage"), but "manage" is generic and the action list is not comprehensive, matching the 1-2-concrete-actions anchor.

3 / 5

Completeness

It has an explicit "what" (create and manage agent graphs…) and an explicit "Use when…" trigger clause, but the when-condition is a single phrase rather than the multi-phrase trigger list of the top anchor.

4 / 5

Trigger Term Quality

It includes natural triggers like "multi-agent workflows" and "configs route to each other", but misses common synonyms such as orchestration, chaining, or routing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The agent-graphs/config-routing niche is mostly distinct, but "multi-agent workflows" still overlaps with general agent-orchestration skills, leaving minor conflict risk.

4 / 5

Total

15

/

20

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.

Validation16 / 16 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.