本文へ移動
cccskills
無料GitHub で公開

seo

Run a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO. Use as the umbrella skill when the user asks for a full SEO analysis or strategy.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md4.7 KB
  • references/cwv-thresholds.md5.0 KB
  • references/eeat-framework.md7.3 KB
  • references/quality-gates.md5.1 KB
  • references/schema-types.md6.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

SEO: Universal SEO Analysis Skill

Comprehensive SEO analysis across all industries (SaaS, local services, e-commerce, publishers, agencies). Orchestrates 2 specialized sub-skills.

When to Use

  • Use when the user asks for a full SEO audit or broad SEO strategy.
  • Use as the umbrella entry point when multiple SEO dimensions are in scope.
  • Use when the task spans technical SEO, content, schema, sitemaps, and AI search readiness together.

Quick Reference

CommandWhat it does
/seo audit <url>Full website audit with parallel subagent delegation
/seo technical <url>Technical SEO audit (9 categories)

Orchestration Logic

When the user invokes /seo audit, delegate to subagents:

  1. Detect business type (SaaS, local, ecommerce, publisher, agency, other)
  2. Spawn subagent: seo-technical for technical SEO analysis
  3. Collect results and generate unified report with SEO Health Score (0-100)
  4. Create prioritized action plan (Critical -> High -> Medium -> Low)

Industry Detection

Detect business type from homepage signals:

  • SaaS: pricing page, /features, /integrations, /docs, "free trial", "sign up"
  • Local Service: phone number, address, service area, "serving [city]", Google Maps embed
  • E-commerce: /products, /collections, /cart, "add to cart", product schema
  • Publisher: /blog, /articles, /topics, article schema, author pages, publication dates
  • Agency: /case-studies, /portfolio, /industries, "our work", client logos

Quality Gates

Read references/quality-gates.md for thin content thresholds per page type. Hard rules:

  • WARNING at 30+ location pages (enforce 60%+ unique content)
  • HARD STOP at 50+ location pages (require user justification)
  • Never recommend HowTo schema (deprecated Sept 2023)
  • FAQ schema for Google rich results: only government and healthcare sites (Aug 2023 restriction); existing FAQPage on commercial sites -> flag Info priority (not Critical), noting AI/LLM citation benefit; adding new FAQPage -> not recommended for Google benefit
  • All Core Web Vitals references use INP, never FID

Reference Files

Load these on-demand as needed (do NOT load all at startup):

  • references/cwv-thresholds.md: Current Core Web Vitals thresholds and measurement details
  • references/schema-types.md: All supported schema types with deprecation status
  • references/eeat-framework.md: E-E-A-T evaluation criteria (Sept 2025 QRG update)
  • references/quality-gates.md: Content length minimums, uniqueness thresholds

Scoring Methodology

SEO Health Score (0-100)

Weighted aggregate of all categories:

CategoryWeight
Technical SEO22%
Content Quality23%
On-Page SEO20%
Schema / Structured Data10%
Performance (CWV)10%
AI Search Readiness10%
Images5%

Priority Levels

  • Critical: Blocks indexing or causes penalties (immediate fix required)
  • High: Significantly impacts rankings (fix within 1 week)
  • Medium: Optimization opportunity (fix within 1 month)
  • Low: Nice to have (backlog)

Sub-Skills

This skill orchestrates 2 specialized sub-skills:

  1. seo-audit -- Full website audit with parallel delegation
  2. seo-technical -- Technical SEO (9 categories)

Subagents

For analysis during audits:

  • seo-technical -- Crawlability, indexability, security, CWV

Error Handling

ScenarioAction
Unrecognized commandList available commands from the Quick Reference table. Suggest the closest matching command.
URL unreachableReport the error and suggest the user verify the URL. Do not attempt to guess site content.
Sub-skill fails during auditReport partial results from successful sub-skills. Clearly note which sub-skill failed and why. Suggest re-running the failed sub-skill individually.
Ambiguous business type detectionPresent the top two detected types with supporting signals. Ask the user to confirm before proceeding with industry-specific recommendations.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.

日本語の概要は準備中です。原文の説明を表示しています。

hybridlabor-api/aos62026年10月12日 更新

hybridlabor-api のスキルをすべて見る

このスキルの問題を報告する