CtrlK
BlogDocsLog inGet started
Tessl Logo

page-play-builder

Use when the user asks to "build programmatic SEO pages", "generate pages at scale", "rank on a high-authority third-party site", "borrow domain authority", "build a vs / alternative page", "do local SEO", "optimize a Google Business Profile", or "fix NAP" — one page-build router with four modes: programmatic (template × dataset systems), parasite (barnacle publishing on Medium/Reddit/LinkedIn/GitHub), comparison (vs / alternative pages in four formats), and local (GBP + NAP + citations + location pages), each with its own thin/duplicate, honesty, or reputation-abuse guardrail. Not for finding what to target — use keyword-research or content-gap-analysis; not for drafting one standalone article — use content-writer; not for scoring a page for publish — use content-quality-auditor. 程序化SEO/批量页面/寄生SEO/借势权重/对比页/vs页/替代页/本地SEO/谷歌商家档案/NAP一致性

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured router skill body: clear mode selection, explicit validation gates and feedback loops appropriate to batch page generation, and clean one-level-deep reference disclosure. Its main weakness is redundancy — the scope-exclusion list and guardrail framing are restated across several sections.

Suggestions

Consolidate the 'not for X / use Y' exclusion list into one place (e.g. the Scope paragraph) and reference it from the Instructions scope guard and Next Best Skill instead of restating it verbatim.

Dedupe the per-mode guardrail framing: state each guardrail once in the Mode Selector table and let the Instructions step reference it, rather than re-describing thin/duplicate, reputation-abuse, honesty, and NAP rules across Mode Selector, Skill Contract, and Instructions.

Inline at least one concrete snippet per mode (e.g. a minimal template×dataset row example or a NAP canonical-record shape) so the body is executable without opening every reference pack.

DimensionReasoningScore

Conciseness

The body is information-dense with no basic-concept padding, but the 'not for X / use Y' scope list recurs verbatim in the scope paragraph, the Instructions scope guard, and Next Best Skill, and the guardrail framing is restated across Mode Selector, Skill Contract, and Instructions — noticeable redundancy that could be tightened.

3 / 5

Actionability

Concrete routing inputs (mode selector table with required inputs and NEEDS_INPUT fallback), a real executable command ('python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/indexpush.py" indexnow --file new-urls.txt --key $INDEXNOW_KEY'), and specific save filenames; the core play execution is offloaded to reference packs rather than spelled out inline, a minor gap.

4 / 5

Workflow Clarity

A clear 5-step sequence with explicit validation checkpoints and feedback loops for this batch/destructive skill: step 2 returns NEEDS_INPUT and stops on missing/inconsistent input, step 4 requires the guardrail verdict before handoff ('Flag any blocker; do not ship it silently'), and the index push is dry-run by default with '--live' gated behind the thin/duplicate guardrail passing.

5 / 5

Progressive Disclosure

Well-organized overview (Quick Start, Mode Selector, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with one-level-deep, clearly signaled links to the four real reference files, each annotated with its contents in the Reference Materials section.

5 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A model trigger-style description: it states the four-mode router concretely, leads with explicit 'Use when…' triggers including synonyms in two languages, and disambiguates against neighboring skills via a 'Not for…' clause. No vagueness, fluff, or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across all four modes — 'template × dataset systems', 'barnacle publishing on Medium/Reddit/LinkedIn/GitHub', 'vs / alternative pages in four formats', and 'GBP + NAP + citations + location pages' — giving comprehensive coverage of what each mode builds.

5 / 5

Completeness

Explicitly answers both 'what' (one page-build router with four named modes, each with its guardrail) and 'when' (a leading 'Use when the user asks to…' clause with concrete trigger phrases), and adds negative scope ('Not for…').

5 / 5

Trigger Term Quality

Comprehensive quoted natural triggers ('build programmatic SEO pages', 'generate pages at scale', 'borrow domain authority', 'fix NAP', 'optimize a Google Business Profile') plus Chinese synonyms (程序化SEO, 寄生SEO, 对比页, 本地SEO), matching the anchor's expectation of synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche (page-build router) with explicit negative scope naming the adjacent skills (keyword-research, content-gap-analysis, content-writer, content-quality-auditor), minimizing the chance of triggering for the wrong skill.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 22 suspicious

Warning

Total

13

/

16

Passed

Repository
aaron-he-zhu/aaron-marketing-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.