Skills/ClawHub/seo-change-monitor

seo-change-monitor@1.0.0

CAUTION· static only

Publisher claims: "Catch SEO regressions after a deploy by snapshotting key URLs (status, redirects, canonical, robots, titles, schema, hreflang, robots.txt, sitemaps) and diffing against a saved baseline. Use for "did the release break SEO", "monitor SEO changes", "add an SEO check to CI" or before and after a launch." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher romeoseo · publishing for 4 daysInstalls 0Last detonated 4d ago
What would fix thisWatchDispute verdict

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-10 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

MEDIUM
File type combined with upload actionSKILL.md:157 · File type combined with upload action — agent may exfiltrate local data files… - GitHub Actions example step: `run: python3 seo/seo_snapshot.py snap seo/urls.txt > after.json && python3 seo/seo_snapshot.py diff seo/baseline.json after.json`. The non-zero exit fails the job; post the output to the PR or team channel.…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

No other findings across 277 lines in 2 files.

Cost to the agent

Instructions loaded
≈5,020 tok
1 file · 2 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim romeoseo: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim romeoseoPropose a patch to the maintainer