Performance Reporter
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only SEO reporting skill is purpose-aligned, with notable but expected use of connected analytics data and optional persistent report memory.
This skill appears safe for its stated purpose. Before installing or using it, make sure you are comfortable letting it summarize connected analytics/Search Console/SEO data, and review any saved memory files so sensitive business metrics or outdated decisions are not carried into future work.
Findings (2)
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.
If connected tools are available, the agent may read and summarize business-sensitive website traffic, search, ranking, backlink, and AI visibility data.
The skill may use connected third-party analytics and SEO accounts or exported business data. This is aligned with the reporting purpose, but users should notice the account/data access involved.
With tools connected, aggregates traffic from ~~analytics, search data from ~~search console, rankings/backlinks from ~~SEO tool, and AI visibility from ~~AI monitor. Without tools, ask user for analytics exports, Search Console data, ranking data, and KPIs.
Confirm the intended domain, date range, and connected accounts before using it; provide only the exports or tool access needed for the requested report.
Report findings, KPIs, action items, and decisions could be reused later by the agent if saved to memory.
The skill intentionally creates persistent summaries and may update shared memory files with business findings and decisions. This is disclosed and useful for recurring reporting, but it can preserve sensitive or incorrect context for future tasks.
**Writes**: a user-facing monitoring deliverable plus a reusable summary that can be stored under `memory/monitoring/`. ... **Promotes**: significant changes, confirmed anomalies, and follow-up actions to `memory/open-loops.md` and `memory/decisions.md`.
Review saved memory entries, avoid storing confidential raw metrics unnecessarily, and correct or remove stale findings before future reports rely on them.