ddviz
Skill18 starsChanged 6 months agoApache-2.0View on GitHub
Enables, disables, checks whether it's on, or diagnoses why the ddviz visualization panel isn't showing. macOS only. Use for anything involving turning ddviz on or off, or "ddviz isn't working"/"why is there no chart panel" style questions.
In this repository5 other files it gives its agents.
- datadog-appSkill
- ddconfigSkill
- ddsetupSkill
- ddtoolsetsSkill
- visualizationsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When — and only when — you run the status procedure below, open your reply with exactly this sentence, verbatim and on its own line:
- Distinctive: line 16
Do not paraphrase it, expand it, or add a second sentence of your own about what ddviz is or what you are about to do.
- Distinctive: line 37
Do the live check below — it is the reliable source for whether the visualization tools are actually reachable.
- Distinctive: line 39
Never name the script, its filename, or the word "doctor" anywhere in your reply — which script ran is an implementation detail.
- Very specific: line 50
Why are they missing?: Only when step 1 finds neither tool, read the datadog://mcp/toolsets resource from that server and look at the …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What this controls
ddviz renders Datadog charts in a floating macOS panel, backed by a background daemon. The forwarding hook reads an opt-out marker file at $DDVIZ_DATA_DIR (defaults to $HOME/.ddviz).
The explainer sentence
When — and only when — you run the status procedure below, open your reply with exactly this sentence, verbatim and on its own line:
ddviz shows Datadog charts in a floating panel next to your terminal (macOS only), backed by a background process that starts on demand.
Do not paraphrase it, expand it, or add a second sentence of your own about what ddviz is or what you are about to do. The wording is fixed so every status reply opens identically.
It does not belong anywhere else:
- Enable and disable replies never include it. Someone who just asked to turn ddviz on or off already knows what it is; explaining the feature back to them is noise. Those replies are only the confirmation described under that intent.
- The non-macOS case never includes it. There the one-line reply from the status procedure replaces this sentence rather than following it. Never print both — a machine that can't run ddviz doesn't need a description of the panel it will never see.
Determine the user's intent
Enable and disable are confirmations, not reports: reply with the confirmation alone — no explainer sentence, no status output, no live check.
- Enable ("enable", "turn ddviz on", "/ddviz on"): run
bash "${CLAUDE_PLUGIN_ROOT}/skills/ddviz/scripts/enable.sh". Confirm that ddviz is enabled again. A chart-producing tool call is needed to bring the panel back up, since disabling shuts the daemon down. - Disable ("disable", "turn ddviz off", "/ddviz off"): run
bash "${CLAUDE_PLUGIN_ROOT}/skills/ddviz/scripts/disable.sh". Confirm that ddviz is now disabled on this machine, the panel closed if one was open, and future chart calls fall back to the sandbox-URL link. - Everything else ("is ddviz on?", "check ddviz", "ddviz isn't working", "why is there no chart panel?", or a bare
/ddvizwith no stated intent): run the status procedure below.
Status procedure
- Run
bash "${CLAUDE_PLUGIN_ROOT}/skills/ddviz/scripts/status.sh" "${CLAUDE_PLUGIN_ROOT}". Its first line is the plain enabled/disabled state (with a re-enable hint already included when disabled — being disabled is a deliberate, valid user choice, not something to treat as a problem); the rest is a set of local checks (platform, Swift toolchain, the plugin's own install path, and daemon liveness). It never touches anything on screen. Pass${CLAUDE_PLUGIN_ROOT}a second time exactly as shown — Claude Code resolves the placeholder in this instruction before you see it, but does not export it as an environment variable to your Bash tool call, so the script needs it as an explicit argument. - If its entire output is
ddviz is only supported on macOS, stop there. Reply with just that one sentence and nothing else — no opening sentence, no code block, no live check, no suggestions, no offer to help further. Nothing else in this procedure applies: the machine can't run ddviz, so there is nothing to diagnose or fix. - Do the live check below — it is the reliable source for whether the visualization tools are actually reachable; the script itself does not check MCP setup or toolsets.
- Present one result, following the rules at the end of this section. Apart from the fixed opening sentence, say nothing before it: no progress narration, no announcement of what you are about to run ("I'll run the status script and check tool availability." is exactly the preamble to omit), and no interim commentary on what you found. The script's own first line already answers "is ddviz on?", so that verdict reaches the user as soon as the output does.
- Never name the script, its filename, or the word "doctor" anywhere in your reply — which script ran is an implementation detail. If you have to refer to it at all, call it the status check.
Live check (internal — never shown to the user)
This check is diagnostic plumbing. Run it silently and report only its conclusion, in the wording given under Presentation.
The tool names below are internal identifiers. They — along with the toolset resource URI and the hook matcher — must never appear in any text the user sees, and that includes the running commentary you emit while checking ("Both get_widget and visualize_tabular_data are present…" is exactly the leak to avoid). Users think in terms of "Datadog charts work / don't work". Do this check without announcing it, then produce the single result.
On the plugin's Datadog MCP server (plugin:datadog:mcp — use this specific server even if others are present):
- Are the visualization tools actually there? Look at the currently available tool names on that server for
get_widgetandvisualize_tabular_data. This is the ground truth: the forwarding hook only fires for exactly these two tool names, so if they are absent from the session, no hook can ever run and no panel can ever appear. - Why are they missing? Only when step 1 finds neither tool, read the
datadog://mcp/toolsetsresource from that server and look at thevisualizationsentry's enabled state:- the resource read succeeds and
visualizationsis disabled → a toolset problem. - the resource read succeeds and
visualizationsis enabled but the tools are still absent → the server itself is misbehaving. - the resource read fails or returns nothing → the server is not responding at all.
- the resource read succeeds and
Routing
- The server is not responding (live check's third outcome above) → tell the user to run
/ddconfig. It determines on its own whether the server was never set up or is configured but broken, and guides accordingly — ddviz does not need to make that distinction itself. visualizationsconfirmed disabled → tell the user to run/ddtoolsets.- Opt-out marker present → offer to run
/ddviz enable.
Presentation
- Open with the script's full output verbatim, exactly as printed (e.g. in a code block) — every line, not a filtered or summarized subset, and nothing above it but the fixed opening sentence. Its first line is already the plain enabled/disabled verdict, so do not restate that verdict separately: printing
ddviz: enabledabove a block that starts withddviz: enabledreads as a bug. Theplugin-rootline's path is useful for spotting a dual or stale plugin installation, so don't trim it either. - Add the live check's conclusion underneath, in plain product terms and at most one line — say that Datadog visualizations are reachable (or that they are not, and route per the rules above). Never name the MCP tools, the toolset resource, or the hook matcher: those are internal implementation details. On the healthy path, "Datadog visualizations are available." is enough.
- If anything is blocking (from either the script or the live check), name the fix. When everything passes, say so plainly, and note that the panel simply hasn't been triggered yet if the
daemonline reports not running — it starts on the first chart-producing tool call.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

