Geo Seo

PassAudited by ClawScan on May 1, 2026.

Overview

Geo Seo appears to be a coherent GEO/SEO reference skill; the only noteworthy items are optional monitoring examples that use a third-party toolkit, cron scheduling, and an external search service.

This skill looks suitable as an informational GEO/SEO reference. If you follow its monitoring examples, review the external toolkit before running it, avoid sharing confidential search queries, and understand any cron job you install.

Findings (3)

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

If the user follows the example, they may download and run third-party code on their machine.

Why it was flagged

The monitoring guidance suggests using an external GitHub toolkit. This is purpose-aligned, but the external dependency is not pinned in the example.

Skill content
git clone https://github.com/aronhy/geo-llms-toolkit.git ~/geo-llms-toolkit
Recommendation

Review the external repository, pin a trusted commit or release, and run it with least privilege.

What this means

If copied into crontab, the scan script would continue running several times per day.

Why it was flagged

The skill provides an optional crontab example for repeated GEO scans. This is disclosed and user-directed, but it creates ongoing scheduled activity if installed.

Skill content
# 45 5,11,17,23 * * * /bin/bash ~/geo-scan.sh > /tmp/geo-scan.log 2>&1
Recommendation

Only add the cron job if continuous monitoring is intended, and remove or disable it when no longer needed.

What this means

Search terms and related domain-checking activity may be sent to an external provider if the example is used.

Why it was flagged

The citation-monitoring example sends configured search queries to Jina AI search. This is disclosed and relevant to citation monitoring.

Skill content
url = "https://s.jina.ai/{}".format(query.replace(" ", "+"))
Recommendation

Avoid confidential queries, review the provider’s privacy terms, and use only domains and prompts you are comfortable sharing.