mcpField
M
marketing-site-skill

marketing-site-skill

github.com/sergekostenchukDesign & UI3253 installsUpdated 18w ago
Repository

About marketing-site-skill

A specialist skill for building, auditing, and verifying public-facing marketing pages. It combines first-viewport and conversion guidance with metadata and responsive checks, and structures results by what was run, skipped, planned, or reviewed manually.

Key features

  1. 01Build or refactor marketing pages
  2. 02Audit conversion and visual clarity
  3. 03Inspect page metadata
  4. 04Run metadata and responsive checks
  5. 05Separate executed and manual findings

Use cases

  1. 01Create a public product landing page
  2. 02Review a page’s calls to action and layout
  3. 03Check HTML metadata and social previews
  4. 04Test a page’s responsive behavior

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill marketing-site-skill

After installing, type/marketing-site-skillin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
assets/
animation-presets.md
landing-brief.template.md
metadata.template.json
evals/
evals.json
references/
conversion-framework.md
hero-first-viewport.md
metadata-checklist.md
performance-budget.md
responsive-storytelling.md
scripts/
lint_metadata.py
responsive_smoke_test.mjs

Details

From the project README

Marketing Site Skill

Use this specialist for public-facing pages where the first viewport, product/place/person signal, conversion path, media quality, metadata, and responsive behavior matter.

Operating Modes

  • build: create or refactor a marketing/public page.
  • audit: review a page for conversion, metadata, responsive behavior, and visual clarity.
  • metadata: inspect title, description, canonical, Open Graph, Twitter, headings, and social preview basics.
  • verify: run local checks and distinguish evidence from manual review.

Required Workflow

  1. Read references/hero-first-viewport.md before designing the top of the page.
  2. Read references/conversion-framework.md for CTA and proof decisions.
  3. Read references/metadata-checklist.md when source files or HTML are available.
  4. Use assets/landing-brief.template.md and assets/metadata.template.json when producing durable page briefs or metadata specs.
  5. Apply ../../shared/privacy-policy.md before using external images, AI page builders, or cloud tools.
  6. If source files are available, run scripts/lint_metadata.py or report why it was skipped.
  7. If a URL is available, run scripts/responsive_smoke_test.mjs or report why it was skipped.
  8. Return Ran, Skipped, Planned, and Manual sections.

Design Doctrine

  • The first viewport must show the product, place, offer, brand, object, or person clearly.
  • Do not hide the real subject inside a decorative card or generic gradient.
  • Use real or generated bitmap media when a visual signal is needed.
  • Keep CTA hierarchy obvious and avoid many visually equal primary actions.
  • Keep mobile text readable and avoid overlap, horizontal overflow, and viewport-scaled font tricks.

Tool Contracts

  • Metadata lint: python3 scripts/lint_metadata.py --root "$PROJECT_ROOT" --out reports/metadata.json.
  • Responsive smoke: node scripts/responsive_smoke_test.mjs --url "$URL" --out reports/visual-smoke.
  • Optional cloud tools require explicit approval and cannot be validation evidence by themselves.

Validation

python3 $CODEX_SKILLS_DIR/.system/skill-creator/scripts/quick_validate.py $CODEX_SKILLS_DIR/marketing-site-skill
python3 $CODEX_SKILLS_DIR/senior-skill-architect/scripts/lint_production_skill.py $CODEX_SKILLS_DIR/marketing-site-skill

Output Shape

Page type:
Primary offer or object:
First viewport:
CTA path:
Metadata:
Ran:
Skipped:
Manual findings:
Risks:

Comments

Markdown supported