creo-gsc — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited creo-gsc (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
| Command | Description |
|---|---|
/creo gsc list-sites | List all Search Console properties |
/creo gsc inspect <url> | Inspect a URL's indexation status |
/creo gsc analytics | Get search analytics (clicks, impressions, CTR) |
/creo gsc security <url> | Analyze HTTP security headers |
/creo gsc onpage <url> | On-page SEO analysis (title, meta, headings, images) |
/creo gsc schema <url> | Validate structured data (JSON-LD) |
/creo gsc hreflang <url> | Validate hreflang implementation |
/creo gsc full-seo <url> | Run all 9 page analyzers on a URL |
/creo gsc site-audit <url> | Crawl and audit entire website |
The toolkit is a Python package. All commands are executed via:
# Find the installed toolkit
GSC_DIR="${HOME}/.claude/skills/creo-gsc"
# Activate the virtual environment (if installed with venv)
source "${GSC_DIR}/.venv/bin/activate" 2>/dev/null || true
# Run commands
python -m gsc_toolkit <command> [options]If the venv is not available, ensure gsc_toolkit's parent directory is on PYTHONPATH:
PYTHONPATH="${GSC_DIR}:${PYTHONPATH}" python -m gsc_toolkit <command>python -m gsc_toolkit list-sites
python -m gsc_toolkit inspect <url>
python -m gsc_toolkit analytics [--days 28] [--dimension query|page|device|country]
python -m gsc_toolkit sitemaps
python -m gsc_toolkit batch-inspect <urls_file>
python -m gsc_toolkit coverage [--path <directory>]
python -m gsc_toolkit links [--path <directory>]
python -m gsc_toolkit cwv <url> [--strategy mobile|desktop]
python -m gsc_toolkit cwv-batch <urls_file>
python -m gsc_toolkit index-request <url>
python -m gsc_toolkit index-batch <sitemap_url> [--limit 200]
python -m gsc_toolkit full-report [--days 28]
python -m gsc_toolkit seo-audit [--days 28] [--urls-file <file>]python -m gsc_toolkit security <url>
python -m gsc_toolkit onpage <url>
python -m gsc_toolkit schema <url>
python -m gsc_toolkit hreflang <url> [--no-return-check]
python -m gsc_toolkit robots <base_url>
python -m gsc_toolkit sitemap-check <sitemap_url>
python -m gsc_toolkit full-seo <url>python -m gsc_toolkit content <url>
python -m gsc_toolkit mobile <url>
python -m gsc_toolkit performance <url>
python -m gsc_toolkit url-analysis <url>python -m gsc_toolkit site-audit <url> [--max-pages 500] [--max-depth 10] [--delay 0.2] [--output file.json]For GSC API access, set environment variables or create .env in the working directory:
GSC_KEY_FILE=./service-account-key.json
GSC_SITE_URL=sc-domain:your-domain.com
GSC_DEFAULT_DAYS=28
PAGESPEED_API_KEY=your_api_key
GSC_OUTPUT_DIR=./outputPage analysis commands (security, onpage, schema, hreflang, robots, content, mobile, performance, url-analysis, full-seo, site-audit) do not require any API credentials.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.