Azuredatastudio

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The command may fail or could refer to a different local executable if one already exists on the system.

Why it was flagged

The SKILL.md examples invoke `azuredatastudio`, but there is no install specification declaring how that command is installed or bound to the included scripts.

Skill content
No install spec — this is an instruction-only skill.
Recommendation

Before use, confirm which `azuredatastudio` command will run and prefer invoking a reviewed script path directly if needed.

What this means

Sensitive query text or file names entered as command arguments could remain in a local history file.

Why it was flagged

The skill explicitly persists command history locally, which may include query terms, filenames, or other user-provided arguments.

Skill content
**History log:** `$DATA_DIR/history.log` — tracks all command executions with timestamps
Recommendation

Avoid putting secrets in command arguments and periodically review or delete the local data directory if the history should not be retained.

What this means

Users may overestimate the skill's maturity or assume it provides real Azure Data Studio-style import/export/validation features.

Why it was flagged

One included script shows the main functionality is a stub, while the documentation presents a broader Azure Data Studio-like data toolkit.

Skill content
run)
        echo "TODO: Implement main functionality"
Recommendation

Treat this as an unofficial lightweight local script and verify any data-processing results before relying on them.