What does this skill do, and when should you use it?
Page Play Builder builds SEO pages and page systems that are not single hand-written articles. One router supports four modes: programmatic SEO, third-party-platform publishing, comparison pages, and local SEO. Each mode has separate required inputs and guardrails for thin or duplicate content, site-reputation abuse, claim honesty, or NAP consistency. It produces a handoff-ready page or page-system plan and writes the standard handoff summary to memory/content/.
Routes the request to programmatic, parasite, comparison, or local mode; reads datasets, product or ICP context, live URLs, competitor facts, platform rules, directory information, or NAP data; runs the selected play pack; produces a template-by-dataset system, platform and backlink plan, comparison page, or GBP/NAP/citation/location-page pack; labels numbers as Measured, User-provided, or Estimated; applies the relevant guardrail and flags blockers; and, where applicable, writes results to memory/content/, memory/hot-cache.md, and memory/open-loops.md.
- A marketing team has real row-level data and needs hundreds or thousands of location, integration, or comparison pages from one template.
- An SEO lead needs a third-party publishing plan for Medium, Reddit, LinkedIn, GitHub, or similar platforms that links back to an owned URL.
- A product marketer needs a “you vs competitor” or competitor-alternatives page.
- A local business needs Google Business Profile optimization, consistent name-address-phone data, citations, or location and service-area pages.
How do you install this skill?
- Parasite mode may still create platform-ToS or Google site-reputation-abuse exposure despite its stated ethics guardrails; verify each platform policy and retain human approval before publishing.
- Local and parasite workflows involve Google, Medium, Reddit, LinkedIn, and similar services; for mainland-China users, confirm reachability, account access, and compliant alternatives first.
- Mass generation and index pushing can have substantial external effects; review row-level data, sample pages, duplication, and index scope before any --live operation.
- This assessment is static only; the skill, connectors, scripts, and handoff writes were not executed.
- Shell / CLI
- Network access
- Local filesystem
Python 3
For Claude Code, run /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, then /plugin install aaron-marketing@aaron. On other Agent Skills-compatible hosts, run npx skills add aaron-he-zhu/aaron-marketing-skills. You can also run git clone https://github.com/aaron-he-zhu/aaron-marketing-skills.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/seo-geo/implement/page-play-builder" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- you vs [Competitor]
On a host with automatic skill routing, describe the goal and provide the required input, such as Build a template × dataset page system for integrations from [dataset], Build a "you vs [Competitor]" page, or Do local SEO for [business] in [city]. You may also explicitly name programmatic, parasite, comparison, or local. If required input is missing, the skill returns NEEDS_INPUT.
What are this skill's strengths and limitations?
- Four page-building modes are organized behind one explicit router.
- Each mode has its own guardrail for thin content, duplicate content, reputation abuse, competitor claims, or NAP consistency.
- Tier 1 works with user-provided data and does not require paid APIs.
- The contract defines handoff summaries, memory promotion, blockers, and next skills.
- It does not perform keyword research, content-gap analysis, single-article drafting, JSON-LD generation, or final publish scoring.
- Programmatic mode requires real per-row facts, not simple name-or-city swaps.
- Parasite mode still requires review of platform rules, terms of service, and reputation-abuse risk.
- The supplied source provides no independent test results or platform-coverage verification for this individual skill.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Page Play Builder: Scaled SEO Page Builder this page | 54 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Maps Intelligence for Local SEO | 54 · Use with care | ★ 19k | 22d ago | MIT |
| Local SEO Analyzer | 52 · Use with care | ★ 19k | 22d ago | MIT |
| Site Structure Optimizer | 59 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
| Competitor Comparison Page Builder | 47 · Use with care | ★ 19k | 22d ago | MIT |
How did FollowSkills review this skill?
The skill treats fetched or pasted material as untrusted and makes connectors opt-in; batch index submission is dry-run by default and requires explicit --live, while result saving is conditioned on user confirmation. These controls reduce prompt-injection and external-side-effect risk. However, it does not fully disclose data flows, confirmation boundaries for every write, rollback procedures, or permission isolation, so points are deducted.
Mode selection, required inputs, NEEDS_INPUT behavior, guardrails, and handoff paths are mostly consistent, with stop rules for abnormal input. Static materials contain no key-path test suite or execution evidence, and the referenced play packs, shared protocols, and runtimes are not fully reproduced here; the score therefore remains conservative under the static ceiling.
Triggers, four modes, required inputs, non-fit boundaries, and next skills are clearly stated, including Chinese trigger terms. However, parasite publishing, GBP, and local-directory workflows rely substantially on overseas platforms or Google services without mainland-China alternatives; the broad multi-mode scope also leaves some routing judgment to the user, so points are deducted.
Front matter provides name, version, license, compatibility, and homepage. The document includes Quick Start, a router table, contract, data sources, procedures, guardrails, save templates, and handoffs. It does not clearly identify maintenance ownership, update workflow, changelog, troubleshooting, or parameter-compatibility policy in the supplied skill evidence; publisher identity is also unverified, so points are deducted.
The skill can produce a page-system plan, platform plan, comparison page, or local SEO package with provenance labels, guardrails, handoff, and completion criteria, making the core planning output potentially usable. It does not perform keyword research, actual publishing, quality scoring, or large-scale validation, and no representative output or third-party execution evidence is supplied; the static cap therefore limits the score to 6.
The skill requires competitor claims to be sourced or marked [needs source] and distinguishes Measured, User-provided, and Estimated data, providing a modest audit trail. Claims such as “proven” playbooks, DA 90+, and AI-citation effects lack verifiable sources in the supplied skill material, and no key-path CI or test evidence is shown, so only limited credit is justified.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →