Sightglass

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

Installing the skill delegates substantial behavior to an external package that could change over time or be compromised.

Why it was flagged

Setup installs an unpinned global npm package that is not included in the reviewed artifacts, and the other scripts later execute the resulting sightglass command.

Skill content
npm i -g @sightglass/cli
Recommendation

Pin the npm package version, publish an install spec, provide provenance or checksums, and review the CLI before allowing it to monitor projects.

ConcernHigh Confidence
ASI10: Rogue Agents
What this means

The watcher may continue monitoring the project after the immediate agent session setup has completed.

Why it was flagged

The hook starts the watcher as a background process and disowns it, which lets it continue running independently of the hook command.

Skill content
sightglass watch --project "$PROJECT_DIR" &
  disown
Recommendation

Require explicit opt-in for background monitoring, document how to stop it, and consider stopping the watcher in the post-session hook unless the user chooses persistent monitoring.

What this means

Project activity, dependency decisions, and tool-call details could be uploaded to sightglass.dev when cloud features are enabled.

Why it was flagged

The documented data flow includes potentially sensitive project and tool-call telemetry being sent to a third-party cloud service, without clear artifact-level limits on what is collected, redacted, retained, or auto-pushed.

Skill content
Starts the background watcher that monitors agent sessions — file changes, package installs, tool calls. ... All data syncs to [sightglass.dev](https://sightglass.dev) when authenticated.
Recommendation

Use cloud sync only if needed, disable auto-push unless explicitly desired, and require documentation for collected fields, redaction, retention, and deletion controls.

What this means

Using login connects the local watcher/analyzer to a Sightglass cloud account and may enable history or sync features.

Why it was flagged

The skill asks the user to authenticate with the provider for cloud features; this is purpose-aligned but grants the CLI account-level access for that service.

Skill content
sightglass login

Authenticate with [sightglass.dev](https://sightglass.dev) to enable cloud analysis and history.
Recommendation

Only authenticate if you want cloud analysis, and verify where credentials are stored and how to revoke them.