SkillAgentSearch skills...

seo-ops

AI-powered SEO operations: keyword intelligence, competitor gap analysis, GSC optimization, and trend detection.

Install / Use

npx skills add ericosiu/ai-marketing-skills --skill seo-ops

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Supported Platforms

Universal

Our assessment of seo-ops

seo-ops scores 88/100 on our quality scale, 366th of 604 Data & Analytics skills we index.

Its SKILL.md is 5.7 KB long, well organised into 20 sections with 7 code examples: a solid amount of guidance for an agent.

With 3,573 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so seo-ops is actively maintained.
  • Our last check on 2026-11-01 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

seo-ops compared with similar skills

All 4 of these similar skills score higher than seo-ops; compare them before choosing.

SkillScoreStarsUpdatedFormat
seo-ops (this skill)by ericosiu883.6k55d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server
crawl4aiby unclecode10087.4k3d agoMCP Server

Frequently asked questions

How do I install seo-ops?
Run npx skills add ericosiu/ai-marketing-skills --skill seo-ops. The install tabs above show the steps for each supported agent.
Which AI agents does seo-ops work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is seo-ops safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is seo-ops still maintained?
The repository was last updated about 2 months ago, so seo-ops is actively maintained.

AI SEO Ops

Preamble (runs on skill start)

# Version check (silent if up to date)
python3 telemetry/version_check.py 2>/dev/null || true

# Telemetry opt-in (first run only, then remembers your choice)
python3 telemetry/telemetry_init.py 2>/dev/null || true

Privacy: This skill logs usage locally to ~/.ai-marketing-skills/analytics/. Remote telemetry is opt-in only. No code, file paths, or repo content is ever collected. See telemetry/README.md.


AI-powered SEO operations: keyword intelligence, competitor gap analysis, GSC optimization, and trend detection.

When to Use

  • User asks for keyword research, content brief, or SEO analysis
  • User wants to find quick-win keywords from Google Search Console
  • User needs a competitor gap analysis
  • User wants to identify trending topics for content creation
  • User asks about decaying content or traffic drops
  • User wants a prioritized list of keywords to target

Tools

Content Attack Brief (content_attack_brief.py)

Full keyword intelligence pipeline. Requires AHREFS_TOKEN and GSC auth.

# Run the full brief
python content_attack_brief.py

What it produces:

  • Topic fingerprint from your content library
  • BOFU money keywords ranked by Impact × Confidence
  • Trending keywords with sparkline visualizations
  • Competitor gap analysis (keywords they rank for, you don't)
  • Decaying page alerts (traffic drops >30%)
  • Execution pipeline (auto-create → semi-auto → team)

Output: Prints formatted report to stdout + saves JSON to OUTPUT_DIR/content-attack-brief-latest.json

GSC Client (gsc_client.py)

Google Search Console API client. Works as CLI or importable library.

# CLI usage
python gsc_client.py --queries 50 --days 28
python gsc_client.py --striking                    # Striking distance keywords (pos 4-20)
python gsc_client.py --pages 100 --days 7
python gsc_client.py --trend                       # Daily click/impression trend
python gsc_client.py --devices                     # Mobile vs desktop split
python gsc_client.py --sites                       # List verified properties
python gsc_client.py --json --queries 25           # JSON output
# Library usage
from gsc_client import GSCClient

gsc = GSCClient()
rows = gsc.striking_distance(days=28, min_position=4, max_position=20)
for row in rows:
    print(f"{row['keys'][0]}: pos {row['position']:.1f}, {row['impressions']} impressions")

GSC Auth (gsc_auth.py)

One-time OAuth setup for Google Search Console access.

python gsc_auth.py
# Opens browser → Google Sign-In → saves token locally

Trend Scout (trend_scout.py)

Multi-source trend detection. No API keys required for basic functionality.

python trend_scout.py

Sources: Google Trends RSS, Hacker News, Reddit, X/Twitter (needs BRAVE_API_KEY), YouTube outlier detection

Output: Prints summary + saves JSON to OUTPUT_DIR/flash-trends-latest.json and markdown report.

Configuration

All scripts read from environment variables. Copy .env.example to .env and fill in your values.

Required:

  • GSC_SITE_URL — your Google Search Console property URL
  • GOOGLE_CLIENT_ID / GOOGLE_CLIENT_SECRET — for GSC OAuth
  • YOUR_DOMAIN — your root domain

Optional:

  • AHREFS_TOKEN — enables Ahrefs keyword data and competitor analysis
  • COMPETITORS — comma-separated competitor domains
  • BRAVE_API_KEY — enables X/Twitter trend scanning
  • CONTENT_VERTICALS — comma-separated topics for trend relevance scoring
  • TREND_SUBREDDITS — comma-separated subreddits to monitor

Scoring Model

Keywords are scored on two axes:

Impact (0-10): Volume + CPC + Funnel Stage + Trend direction Confidence (0-10): Keyword Difficulty + Current ranking position + Topic authority

Priority = Impact × Confidence (max 100)

Funnel Classification

  • BOFU: Commercial/transactional intent, or keywords containing "agency", "services", "pricing", "best", "vs", "hire"
  • MOFU: Informational with buying signals — "how to", "guide", "roi", "case study"
  • TOFU: Pure informational

Recommended Workflow

  1. Weekly: Run content_attack_brief.py for the full intelligence report
  2. Daily: Run gsc_client.py --striking to monitor striking distance keywords
  3. 2x/week: Run trend_scout.py to catch trending topics early
  4. Monthly: Review competitor gaps and adjust COMPETITORS list

SEO/AEO/GEO Closed Loop

Use analytics readbacks before promoting any SEO, AEO, GEO, or content-refresh playbook change.

Inputs:

  • GSC clicks, impressions, CTR, average position, queries, pages
  • GA4 sessions, engaged sessions, conversions, assisted leads
  • Ahrefs rankings, backlinks, traffic estimates, keyword movement
  • ClickFlow opportunities where available
  • AI-search / answer-engine / GEO visibility where available
  • CMS/page change log

Judgment:

  • Compare baseline vs candidate windows.
  • Segment by page, query, topic, intent, and source.
  • Track confounders: seasonality, indexing lag, brand spikes, campaigns, tracking changes, and unrelated site edits.

Promotion rule:

  • Promote the playbook patch only if the candidate beats baseline or exposes a repeatable signal.
  • Otherwise mark it unproven, keep testing, or rollback.

Common readback windows:

  • Content refresh: 7, 14, 28, and 56 days
  • New content: 14, 28, 56, and 90 days
  • Technical SEO fix: daily for 7 days, then 28-day readback
  • AEO/GEO visibility: weekly, because answer engines are noisy gremlins with citations

Required readback fields:

  • change made
  • owner
  • page/query/topic affected
  • baseline window
  • candidate window
  • source systems pulled
  • primary and secondary metrics
  • caveats
  • decision: promote / keep testing / rollback / unproven
  • next playbook patch

Dependencies

pip install -r requirements.txt

Related Skills

View on GitHub
GitHub Stars3.6k
CategoryData
Updated1mo ago
Forks684

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions