About diagnostics
A technical diagnostics skill for marketing and web teams investigating crawl, indexing, traffic, or Core Web Vitals issues. It structures evidence gathering, root-cause hypotheses, remediation planning, and validation.
Key features
- 01Signal triangulation across data sources
- 02Issue reproduction scripts
- 03Root-cause hypothesis mapping
- 04Remediation and risk planning
- 05Pre/post-fix validation templates
Use cases
- 01Investigating crawl or indexing anomalies
- 02Tracing traffic drops to likely causes
- 03Checking Core Web Vitals regressions
- 04Validating fixes after deployments
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/diagnosticsin Claude Code to confirm it loaded.
Details
From the project READMETechnical 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.
Comments
Markdown supported