Forge seo

Skill is-bo/fullstack-forge-skill/.gemini/skills/forge-seo

A production full-stack engineering skill suite for AI coding agents—covering UI, UX, security, databases, auth, caching, testing, performance, and deployment.

Install

npx -y skills add is-bo/fullstack-forge-skill --skill forge-seo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Conditionally inspect public web content for crawlability, canonicalization, metadata, structured data, and rendering. Activate automatically for public indexable web routes when that concern is relevant to a software-engineering request.

SKILL.md

1.8 KB, 354 tokens by cl100k_base, as published. Nobody here has run it

Fullstack Forge adapter: forge-seo

This file is a pointer maintained by Fullstack Forge. It exists so this agent host can discover and trigger the skill. The full playbook is not duplicated here: one canonical copy is shared by every installed host.

Read the canonical playbook now and follow it exactly:

../../../.fullstack-forge/skills/forge-seo/SKILL.md

That path is relative to this file. From the installation root it is .fullstack-forge/skills/forge-seo/SKILL.md. Every resource the playbook references (fullstack-forge/references/..., fullstack-forge/schemas/..., fullstack-forge/templates/..., fullstack-forge/profiles/...) resolves relative to .fullstack-forge/skills/.

Resolve the runtime composition before loading specialist guidance:

node ../../../.fullstack-forge/runtime/cli/src/composition-entry.js seo compose --root <repository-root> --json

Pass repeatable --request, --condition, or --risk-surface values only for explicit requests and directly proven task facts.

Then load only the ordered selected paths in .forge/composition.json. Stop and report the installation as damaged if missing is non-empty; suppressed sources are not fallback instructions.

Do not edit this adapter; edit the canonical playbook instead. If the canonical file is missing or unreadable the installation is damaged: run forge doctor, then forge update all.

Gives 0 of the 12 instructions most seo skills give in 354 tokens

Counted across 454 of the 460 authors here whose files we hold, read 2026-08-06

implement structured data using JSON-LDin 30 of 454, across 26 files
write unique meta descriptions under 160 charactersin 27 of 454, across 20 files
verify one H1 exists per pagein 24 of 454, across 15 files
maintain a single h1 per pagein 24 of 454, across 15 files
use JSON-LD format for all schema markupin 23 of 454, across 15 files
use descriptive anchor text for internal linksin 21 of 454, across 16 files
add descriptive alt text to imagesin 19 of 454, across 15 files
read product marketing context before auditingin 19 of 454, across 10 files
write unique title tags under 60 charactersin 19 of 454, across 14 files
add unique title and meta description per pagein 19 of 454, across 17 files
Reference the sitemap in robots.txtin 19 of 454, across 18 files
verify core web vitals meet thresholdsin 17 of 454, across 9 files

Said here and by no other author read

read the canonical playbook
resolve the runtime composition before loading guidance
load only ordered selected paths
pass request flags for explicit requests only
report installation as damaged if missing sources exist
treat suppressed sources as non-fallback instructions