Skill

diagnostics

Conducts structured technical SEO audits, incident response, and validation for crawl/index anomalies, traffic drops, and Core Web Vitals regressions using signal triangulation and root cause analysis.

performance

monitoring

From seo-workflow-orchestration

Install

Run in your terminal

npx claudepluginhub gtmagents/gtm-agents --plugin seo-workflow-orchestration

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

executing-plans

Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.

superpowers

134.2k

brainstorming

7 files

Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.

superpowers

134.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

134.2k

Stats

Parent Repo Stars138

Parent Repo Forks24

Last CommitNov 19, 2025

Actions

View Source View Plugin View on GitHub View README

Technical Diagnostics Toolkit Skill

When to Use

Investigating crawl/index anomalies, traffic drops, or Core Web Vitals regressions.
Running scheduled audits ahead of major launches or migrations.
Validating fixes before/after engineering deployments.

Framework

Signal Triangulation – combine Search Console, log files, crawler output, and analytics deltas.
Replication Scripts – document steps to reproduce issues (user agents, locales, device types).
Root Cause Hypotheses – map symptoms to likely causes (render blocking, redirects, robots, schema errors).
Fix Design – outline remediation options, risk level, dependencies, and testing approach.
Validation & Monitoring – specify metrics and alerts to confirm resolution.

Templates

Diagnostics worksheet (symptom, evidence, hypothesis, owner, next action).
Crawl + render checklist per environment.
Validation log capturing metrics pre/post change.

Tips

Keep historical baselines to quickly detect regressions.
Pair with engineering release notes to correlate incidents.
Automate recurring crawls and lighthouse runs to catch issues early.