Run any Skill in Manus with one click

review-seo

Stars18

Forks2

UpdatedJuly 3, 2026 at 23:22

Internal SEO review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks changed web pages/routes for indexability, metadata, and structured data — applies only to public web surfaces. Findings only; never edits code.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

gtrabanco

gtrabanco/agentic-workflow

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web DevelopersComputer and Mathematical Occupations·SOC 15-1254

SKILL.md

readonly

name	review-seo
user-invocable	false
version	1.0.1
author	Gabriel Trabanco <gtrabanco@users.noreply.github.com>
license	MIT
description	Internal SEO review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks changed web pages/routes for indexability, metadata, and structured data — applies only to public web surfaces. Findings only; never edits code.

Review SEO (internal)

Composed by review-change / product-audit within their conversation — on any agent, follow this file inline as the routed step. Findings only; never edits, never refactors.

Scope

The diff or path/glob the caller passes; default the current change vs the default branch. State the scope at the top of the returned table.

Checklist (evaluate EVERY item — none is optional; n/a must be stated)

✓ Read the project's SEO doc first (e.g. docs/frontend/SEO.md) — n/a all items with the reason if the product has no public web surface
✓ Every new/changed public page has a unique title and meta description within the project's declared lengths
✓ Canonical URL correct on new/changed routes (no accidental duplicates)
✓ Indexability intended = indexability actual (robots/noindex/sitemap state matches the page's purpose)
✓ One h1 per page; heading levels don't skip
✓ Structured data valid for the content type the project declares (cite the validator output when run)
✓ Links crawlable (real hrefs, not click handlers) on changed navigation
✓ Images on changed pages have descriptive filenames/alt where the SEO doc requires
✓ No render-blocking regression for primary content (content present without JS where the project declares SSR/SSG)

Return exactly

REVIEW SEO — scope: <scope>

| # | Finding | Sev | Evidence | Suggested fix |
|---|---------|-----|----------|---------------|
| 1 | <what>  | critical|major|minor | <file:line> | <smallest action> |

Checklist: <n> evaluated, <n> pass, <n> findings, <n> n/a (<which + why>)
Summary: <1-2 sentences>
Decision: PASS | FAIL

FAIL if any critical or major finding is open; PASS otherwise. Minor findings never block — they route to the caller's triage step.

Done when

Every checklist item was evaluated with evidence (file:line or command output) or explicitly marked n/a with the reason.
The fixed-format block above is returned — nothing more, nothing less — and no code was changed.

More from this repository

same repository

product-audit

gtrabanco/agentic-workflow

Periodic, product-wide health check — the CTO's "where do we actually stand?" Sweeps the WHOLE codebase (not a diff, not a PR) across every applicable axis — correctness, architecture, security/cybersecurity, performance, tests, UX/UI, accessibility, SEO, brand, tech debt — PLUS process & docs (incomplete phases, aging issues, solvable known-issues, doc/workflow completeness) and roadmap coherence. Mines accumulated suggestions from feature docs. Output: a severity-ranked report and concrete PROPOSALS — issues to open, roadmap features to add or remove. Every run is persisted to docs/audits/<n>-<YYYY-MM-DD>.md with an incremental audit id and findings numbered F1, F2, … so any finding is addressable later as "triage-issue <audit-id> F<k>". NEVER auto-fixes; the user decides what to act on. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the `#claude` branch instead (`npx skills add gtrabanco/agentic-workflow#claude`) — see the README. This branch is model-agnostic: the skill inherits

2026-07-1918

triage-issue

gtrabanco/agentic-workflow

Classify an issue and take a defensible decision: fix-now, postpone (deferred/trigger-based), wontfix, or promote-to-feature. Reads the issue's own "when to fix"/trigger and severity, verifies the trigger against the CURRENT codebase (counts consumers, checks thresholds, measures), then routes or reports with a dated, auditable comment. Also triages product-audit findings ("triage-issue <audit-id> F<k>"): reads docs/audits/<audit-id>-*.md, verifies the finding, and opens the GitHub issue only if the verdict warrants it. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the `#claude` branch instead (`npx skills add gtrabanco/agentic-workflow#claude`) — see the README. This branch is model-agnostic: the skill inherits whatever model and effort your agent session is already using. Triggers: "triage issue N", "should we fix #N now", "classify this issue", "is #N's trigger met", "what do we do with #N".

2026-07-1918

design-feature

gtrabanco/agentic-workflow

Turn an idea or a feature request into an exhaustive, checkable product definition — the stage before engineering planning. The core mechanism is **capability closure**: a checklist that forces every entity, capability, and role a feature introduces to be walked to its full surface (CRUD + state transitions + UI entry point + API + test, or an explicit design-time `n/a`), so non-frontier executor models stop silently omitting the implicit work ("auth with dashboard management and ACLs" must not collapse to a users table + a list view). Closure has three fixed checklists: **entity closure** (each entity to full surface), **integration closure** (the feature reconciled against every subsystem in the project's capability inventory, `docs/CAPABILITIES.md` — auth, ACL, navigation, notifications, …), and the **role matrix** (every inventory role explicitly allowed/denied per capability) — plus an **expectation sweep** that forces what a competent human would implicitly assume ("a blog has drafts") into in-scope/out

2026-07-1918

execute-phase

gtrabanco/agentic-workflow

Implement one phase of a feature (default), or a small feature / a fix (--fix) by its SPEC's ## Phases ledger — one phase per invocation, the final phase is always Hardening & PR (the close-out); legacy SPECs without ## Phases run end-to-end in a single pass. Enforces branch safety, issue policy, the project's verification gate, and per-phase doc discipline. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the `#claude` branch instead (`npx skills add gtrabanco/agentic-workflow#claude`) — see the README. This branch is model-agnostic: the skill inherits whatever model and effort your agent session is already using. Triggers: "execute phase P1 of NN", "implement the NN feature", "build NN from its spec", "execute-phase NN P2", "execute-phase --fix".

2026-07-1918

init-workspace

gtrabanco/agentic-workflow

Bootstrap a project's way of working: fetch the agentic-workflow documentation scaffold (template/) and adapt it to THIS project by interview — fill the CLAUDE.md documentation map, gate commands and architecture, prune doc folders that don't apply, keep the SPEC/feature/fix and GitHub templates — then offer to install the skills. The adaptive counterpart to a raw `npx degit` copy. On a repo that already has the scaffold, detects it and switches to **upgrade mode**: diffs the project's substrate against the current template, reads `docs/workflow/MIGRATION.md`, and proposes only the blocks the project is missing — never clobbering a tailored one. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the `#claude` branch instead (`npx skills add gtrabanco/agentic-workflow#claude`) — see the README. This branch is model-agnostic: the skill inherits whatever model and effort your agent session is already using. Triggers: "set up the agentic workflow here", "init-workspace", "scaffold this proje

2026-07-1918

plan-feature-from-issue

gtrabanco/agentic-workflow

Internal step of plan-feature: turn a feature-request issue into a scoped, sized, roadmap-mapped SPEC **product half** (capability closure satisfied) with Closes #N traceability.

2026-07-1918

name	review-seo
user-invocable	false
version	1.0.1
author	Gabriel Trabanco <gtrabanco@users.noreply.github.com>
license	MIT
description	Internal SEO review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks changed web pages/routes for indexability, metadata, and structured data — applies only to public web surfaces. Findings only; never edits code.

Review SEO (internal)

Composed by review-change / product-audit within their conversation — on any agent, follow this file inline as the routed step. Findings only; never edits, never refactors.

Scope

The diff or path/glob the caller passes; default the current change vs the default branch. State the scope at the top of the returned table.

Checklist (evaluate EVERY item — none is optional; n/a must be stated)

✓ Read the project's SEO doc first (e.g. docs/frontend/SEO.md) — n/a all items with the reason if the product has no public web surface
✓ Every new/changed public page has a unique title and meta description within the project's declared lengths
✓ Canonical URL correct on new/changed routes (no accidental duplicates)
✓ Indexability intended = indexability actual (robots/noindex/sitemap state matches the page's purpose)
✓ One h1 per page; heading levels don't skip
✓ Structured data valid for the content type the project declares (cite the validator output when run)
✓ Links crawlable (real hrefs, not click handlers) on changed navigation
✓ Images on changed pages have descriptive filenames/alt where the SEO doc requires
✓ No render-blocking regression for primary content (content present without JS where the project declares SSR/SSG)

Return exactly

REVIEW SEO — scope: <scope>

| # | Finding | Sev | Evidence | Suggested fix |
|---|---------|-----|----------|---------------|
| 1 | <what>  | critical|major|minor | <file:line> | <smallest action> |

Checklist: <n> evaluated, <n> pass, <n> findings, <n> n/a (<which + why>)
Summary: <1-2 sentences>
Decision: PASS | FAIL

FAIL if any critical or major finding is open; PASS otherwise. Minor findings never block — they route to the caller's triage step.

Done when

Every checklist item was evaluated with evidence (file:line or command output) or explicitly marked n/a with the reason.
The fixed-format block above is returned — nothing more, nothing less — and no code was changed.