/seo-page
Use when analyzing a single URL or local file via /seo page — meta, schema, headers, GEO readiness.
$ npx -y skills add fusengine/agents --skill seo-page --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/seo-page
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when analyzing a single URL or local file via /seo page — meta, schema, headers, GEO readiness.
SKILL.md
seo-page.SKILL.mdname: seo-page
description: Use when analyzing a single URL or local file via /seo page — meta, schema, headers, GEO readiness.
user-invocable: false
related-skills: seo, seo-schema, seo-content, seo-geo
<objective> Runs a single-page SEO analysis: fetches the page (URL or local file), extracts meta/OG/Twitter/canonical (`scripts/parse-meta.ts`), validates JSON-LD (`scripts/validate-schema.ts`), analyzes H1-H6 hierarchy, and scores LLM-readiness (`scripts/geo-score.ts`). Checklist covers title length/keyword, meta description length, single-H1 rule, heading hierarchy, canonical correctness, Open Graph/Twitter Card completeness, schema presence, and image alt/lazy/format compliance. For a full-site audit spanning multiple pages, use seo-audit instead. </objective>
Single-Page SEO Analysis
Workflow
1. Fetch page (URL via WebFetch, or read local file) 2. Run `scripts/parse-meta.ts <input>` → extract title, description, OG, Twitter, canonical 3. Run `scripts/validate-schema.ts <input>` → JSON-LD validation 4. Analyze H1-H6 hierarchy 5. Run `scripts/geo-score.ts <input>` → LLM-readiness score 6. Output structured report
Checks
| Element | Rule | |---------|------| | `<title>` | 50-60 chars, primary keyword, brand | | `<meta description>` | 120-155 chars, hook + benefit + CTA | | `<h1>` | Exactly one, contains primary keyword | | `<h2>-<h6>` | Hierarchical, no skip | | Canonical | Self-referencing or pointing to authoritative URL | | Open Graph | og:title, og:description, og:image (1200x630), og:url | | Twitter Cards | summary_large_image with og:image | | Schema | At least one JSON-LD block, validates against schema.org | | Images | All have alt, lazy-loaded, WebP/AVIF |
References
- `skills/seo/02-onpage-seo/` (meta-tags, open-graph, twitter-cards, headers, alt-text)
- `skills/seo/09-checklists/pre-publication.md`
Read more
name: seo-page description: Use when analyzing a single URL or local file via /seo page — meta, schema, headers, GEO readiness. user-invocable: false related-skills: seo, seo-schema, seo-content, seo-geo
<objective> Runs a single-page SEO analysis: fetches the page (URL or local file), extracts meta/OG/Twitter/canonical (`scripts/parse-meta.ts`), validates JSON-LD (`scripts/validate-schema.ts`), analyzes H1-H6 hierarchy, and scores LLM-readiness (`scripts/geo-score.ts`). Checklist covers title length/keyword, meta description length, single-H1 rule, heading hierarchy, canonical correctness, Open Graph/Twitter Card completeness, schema presence, and image alt/lazy/format compliance. For a full-site audit spanning multiple pages, use seo-audit instead. </objective>
Single-Page SEO Analysis
Workflow
1. Fetch page (URL via WebFetch, or read local file) 2. Run `scripts/parse-meta.ts <input>` → extract title, description, OG, Twitter, canonical 3. Run `scripts/validate-schema.ts <input>` → JSON-LD validation 4. Analyze H1-H6 hierarchy 5. Run `scripts/geo-score.ts <input>` → LLM-readiness score 6. Output structured report
Checks
| Element | Rule | |---------|------| | `<title>` | 50-60 chars, primary keyword, brand | | `<meta description>` | 120-155 chars, hook + benefit + CTA | | `<h1>` | Exactly one, contains primary keyword | | `<h2>-<h6>` | Hierarchical, no skip | | Canonical | Self-referencing or pointing to authoritative URL | | Open Graph | og:title, og:description, og:image (1200x630), og:url | | Twitter Cards | summary_large_image with og:image | | Schema | At least one JSON-LD block, validates against schema.org | | Images | All have alt, lazy-loaded, WebP/AVIF |
References
- `skills/seo/02-onpage-seo/` (meta-tags, open-graph, twitter-cards, headers, alt-text)
- `skills/seo/09-checklists/pre-publication.md`
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

