Andrew Yim
e519a49cc4
Run the additive migration pass from SKILL-MIGRATION-GUIDE: generate a root SKILL.md for every skill that lacked one, copied from its desktop/SKILL.md (or code/SKILL.md), with name set to the directory name and description + body preserved verbatim. - scripts/migrate_skill_root.py: the reusable, non-destructive migrator (dry-run default). - 61 new root SKILL.md (desktop source for most; code/SKILL.md for 61/62/92). - Untouched: 16/17/95 (already had root); desktop/ and code/ packaging left intact. - All 64 root SKILL.md validate: frontmatter <=1024, kebab name, description present. Still MANUAL (no SKILL.md source — commands/README only), need hand-authored root SKILL.md: 81-mac-optimizer, 90-reference-curator, 91-multi-agent-guide, 94-dintel-bootstrap. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
110 lines
2.9 KiB
Markdown
110 lines
2.9 KiB
Markdown
---
|
|
name: 11-seo-comprehensive-audit
|
|
description: |
|
|
Comprehensive SEO audit orchestrator. Runs 6-stage audit pipeline (Technical, On-Page, CWV, Schema, Local, GSC) and produces a unified report with weighted health score.
|
|
Triggers: comprehensive SEO, full SEO audit, 종합 SEO 감사, site audit, SEO health check.
|
|
---
|
|
|
|
# Comprehensive SEO Audit
|
|
|
|
## Purpose
|
|
|
|
Orchestrate a full-spectrum SEO audit by running 6 specialized analyses and synthesizing results into a unified health score and actionable report.
|
|
|
|
## Pipeline Stages
|
|
|
|
| # | Stage | Source Skill | Default |
|
|
|---|-------|-------------|---------|
|
|
| 1 | Technical SEO | 12-seo-technical-audit | Always |
|
|
| 2 | On-Page SEO | 13-seo-on-page-audit | Always |
|
|
| 3 | Core Web Vitals | 14-seo-core-web-vitals | Always |
|
|
| 4 | Schema Validation | 16-seo-schema-validator | Always |
|
|
| 5 | Local SEO | 18-seo-local-audit | Skippable |
|
|
| 6 | Search Console | 15-seo-search-console | Skippable |
|
|
|
|
## Workflow
|
|
|
|
### 1. Initialization
|
|
1. Receive target URL from user
|
|
2. Confirm which stages to run (all 6 by default)
|
|
3. Set up audit tracking ID: `COMP-YYYYMMDD-NNN`
|
|
|
|
### 2. Execute Stages (Sequential)
|
|
For each active stage:
|
|
1. Run the sub-skill analysis
|
|
2. Collect JSON results
|
|
3. Extract score and issues
|
|
|
|
### 3. Synthesis
|
|
1. Compute weighted health score (0-100)
|
|
2. Assign grade (A/B+/B/C/D/F)
|
|
3. Prioritize critical and high-severity findings
|
|
4. Generate recommendations
|
|
|
|
### 4. Notion Report
|
|
1. Create summary page: `종합 SEO 감사 보고서 - [domain] - YYYY-MM-DD`
|
|
2. Create individual pages for Critical/High findings
|
|
3. Database: `2c8581e5-8a1e-8035-880b-e38cefc2f3ef`
|
|
|
|
## Health Score Weights
|
|
|
|
| Category | Weight |
|
|
|----------|--------|
|
|
| Technical SEO | 20% |
|
|
| On-Page SEO | 20% |
|
|
| Core Web Vitals | 25% |
|
|
| Schema | 15% |
|
|
| Local SEO | 10% |
|
|
| Search Console | 10% |
|
|
|
|
Skipped stages redistribute weight proportionally.
|
|
|
|
## Output Format
|
|
|
|
```markdown
|
|
## 종합 SEO 감사 보고서: [domain]
|
|
|
|
**Health Score**: [score]/100 ([grade])
|
|
**Date**: YYYY-MM-DD
|
|
**Audit ID**: COMP-YYYYMMDD-NNN
|
|
|
|
### Stage Results
|
|
| Stage | Score | Issues |
|
|
|-------|-------|--------|
|
|
| Technical SEO | XX/100 | N issues |
|
|
| On-Page SEO | XX/100 | N issues |
|
|
| Core Web Vitals | XX/100 | N issues |
|
|
| Schema | XX/100 | N issues |
|
|
| Local SEO | XX/100 | N issues |
|
|
| Search Console | XX/100 | N issues |
|
|
|
|
### Critical Findings
|
|
1. [Finding with recommendation]
|
|
|
|
### Recommendations (Priority Order)
|
|
1. [Action item]
|
|
```
|
|
|
|
## MCP Tool Usage
|
|
|
|
### Firecrawl
|
|
```
|
|
mcp__firecrawl__scrape: Fetch page content for on-page and schema analysis
|
|
```
|
|
|
|
### Notion
|
|
```
|
|
mcp__notion__*: Create audit report pages in SEO database
|
|
```
|
|
|
|
### Perplexity
|
|
```
|
|
mcp__perplexity__search: Research best practices for recommendations
|
|
```
|
|
|
|
## Limitations
|
|
|
|
- Local SEO stage requires manual input for NAP/GBP data
|
|
- Search Console stage requires GSC API credentials
|
|
- Health score accuracy improves when all 6 stages are active
|