Performance Reporter
v8.0.2Generate SEO/GEO dashboards: rankings, traffic, backlinks, AI visibility for stakeholders. SEO报告/绩效仪表盘
⭐ 2· 2.3k·7 current·7 all-time
byAaron Zhu@aaron-he-zhu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and large template/reference docs all match an SEO/GEO reporting/monitoring skill. The declared requirements are minimal (no env vars, no binaries) which is consistent with an instruction-only reporting skill that works with manual data or optional connectors.
Instruction Scope
SKILL.md instructs the agent to read shared repo reference files (CLAUDE.md, state model) and to write monitoring outputs into agent memory paths (memory/monitoring/, memory/open-loops.md, memory/decisions.md). This is expected for a monitoring/reporting skill but is worth noting because stored reports or summaries may contain sensitive data if the user supplies it.
Install Mechanism
No install spec and no code files — instruction-only is lowest-risk. There are no downloads, external install URLs, or package installs to review.
Credentials
The skill declares no required environment variables or credentials, which is appropriate. It does mention optional integrations (analytics, search console, SEO tools, AI monitor) — those integrations would require API keys when enabled, but the SKILL.md does not request them by default. Users should only supply connector credentials when needed and with least privilege.
Persistence & Privilege
always:false (normal). The skill is allowed to be invoked autonomously (platform default). It writes to its own agent memory locations as part of the Skill Contract — that is normal for monitoring skills but increases persistence of any data the user provides.
Assessment
This skill appears coherent and safe as an instruction-only SEO/GEO report generator. Before installing or using it: (1) review the GitHub homepage/source to confirm origin and review any referenced contract files; (2) be cautious about what you paste into reports — do not include secrets or PII you don't want stored in agent memory; (3) if you enable optional connectors (Analytics, Search Console, Ahrefs/Moz, AI monitor), provide only the minimum-scoped API keys and verify where data is sent; (4) periodically review what's stored under memory/monitoring, memory/open-loops.md, and memory/decisions.md and purge sensitive entries as needed. If you want additional assurance, ask the maintainer for a brief summary of exactly which external APIs the connectors call and what minimum scopes they require.Like a lobster shell, security has layers — review code before you run it.
analyticsvk973wdr0j2jp2fdx78vy101x8n84bn8jgeovk973wdr0j2jp2fdx78vy101x8n84bn8jlatestvk973pz4rfzpg0n1021v4br8aq185099tperformance-reportvk973wdr0j2jp2fdx78vy101x8n84bn8jseovk973wdr0j2jp2fdx78vy101x8n84bn8jseo-reportingvk973wdr0j2jp2fdx78vy101x8n84bn8j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.