CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

creating-mermaid-dbt-dag

Generates a Mermaid flowchart diagram of dbt model lineage using MCP tools, manifest.json, or direct code parsing as fallbacks. Use when visualizing dbt model lineage and dependencies as a Mermaid diagram in markdown format.

Quality

88%

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

The canonical home for this skill is dbt-labs/dbt-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 skill body: a clear method-fallback workflow, untrusted-content handling, and proper progressive disclosure across four real reference files. The two dimensions at 4 reflect small gaps — no example Mermaid/classDef output and no validation that the generated diagram renders.

Suggestions

Add a short example Mermaid snippet (with classDef styling) in the Formatting Guidelines so the color rules translate directly to executable output.

Add a final validation step in Step 4 — e.g., check the generated diagram for syntax errors or unexpected node labels before returning it.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout — it never explains what dbt, Mermaid, or MCP tools are — and every line is instruction or decision guidance (e.g., "Check file size first — if too large (>10MB), skip to next method"). Phrases like "Provides production lineage from dbt Cloud" disambiguate method choice rather than pad, matching the lean 5 anchor.

5 / 5

Actionability

Guidance is largely executable: a four-method hierarchy with links, the "graph LR" directive, and an exact color-to-node-type mapping. However, no example Mermaid snippet or classDef/styling syntax is given for actually applying those colors, leaving a minor gap between the concrete instructions and copy-paste-ready output.

4 / 5

Workflow Clarity

Steps 1–4 are clearly sequenced, the fallback chain is explicit, and there is one conditional checkpoint (the >10MB manifest size check). A validation step for the generated output — e.g., confirming the Mermaid renders without syntax errors — is missing, which keeps it at 4 rather than 5.

4 / 5

Progressive Disclosure

The body is a lean overview with four clearly signaled, one-level-deep references (using-get-lineage-dev.md, using-get-lineage.md, using-manifest-json.md, parsing-code-directly.md), all verified to exist with no nested references. ~310 lines of method detail are appropriately split out of SKILL.md, exactly matching the top anchor.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong description: it states a concrete capability, names the three data-source methods with a fallback ordering, and provides an explicit 'Use when' trigger clause with natural phrasing. The only weakness is modest synonym coverage (e.g., no 'DAG' or 'dependency graph' triggers).

DimensionReasoningScore

Specificity

"Generates a Mermaid flowchart diagram of dbt model lineage" names a concrete action and enumerates three methods ("using MCP tools, manifest.json, or direct code parsing as fallbacks"). It lists several specific actions with minor gaps — no mention of legends, coloring, or the markdown output format in the 'what' portion — so it falls just short of the comprehensive coverage of a 5.

4 / 5

Completeness

The 'what' is explicit ("Generates a Mermaid flowchart diagram of dbt model lineage using MCP tools, manifest.json, or direct code parsing as fallbacks") and the 'when' is an explicit, concrete trigger clause ("Use when visualizing dbt model lineage and dependencies as a Mermaid diagram in markdown format"). Both are clearly and concretely answered, matching the top anchor rather than the merely-adequate 'when' of a 4.

5 / 5

Trigger Term Quality

Natural phrases are present — "dbt model lineage", "dependencies", "Mermaid diagram", "visualizing" — which a user with this need would plausibly say. Common synonyms like "DAG", "dependency graph", or "data build tool" are missing, keeping it below the comprehensive synonym coverage of a 5 but well above the partial coverage of a 3.

4 / 5

Distinctiveness Conflict Risk

The dbt-lineage-to-Mermaid niche is highly specific with distinct triggers, and the skill name (creating-mermaid-dbt-dag) reinforces it. Minimal risk of triggering for the wrong skill; no plausible overlap with related skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

dbt-labs/dbt-agent-skills

Path

skills/dbt-extras/skills/creating-mermaid-dbt-dag/SKILL.md

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.