mcpField
P
publishing-process

publishing-process

github.com/gtmagentsMarketing & growth42867 installsUpdated 30w ago
Repository

About publishing-process

An SEO publishing workflow skill for content and marketing teams coordinating writers, designers, web, and legal. It organizes pre-launch checks, technical and analytics QA, launch controls, and post-launch validation, with runbook and checklist templates.

Key features

  1. 01Pre-flight asset and approval checks
  2. 02CMS and code quality review
  3. 03Analytics and tracking configuration checks
  4. 04Staging review, smoke tests, and rollback planning
  5. 05Post-launch indexation and performance validation

Use cases

  1. 01Coordinate publishing across multiple teams
  2. 02Check SEO, accessibility, and analytics requirements before launch
  3. 03Track owners and approval evidence in a runbook
  4. 04Review missed deadlines or publishing defects

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill publishing-process

After installing, type/publishing-processin Claude Code to confirm it loaded.

Details

From the project README

SEO Publishing Process Skill

When to Use

  • Coordinating multi-team releases (writers, designers, web, legal).
  • Ensuring SEO assets meet quality, accessibility, and analytics requirements before launch.
  • Running retros after missed deadlines or publishing defects.

Framework

  1. Pre-flight Checklist – briefs approved, assets uploaded, localization complete, legal sign-off captured.
  2. CMS/Code QA – metadata, schema markup, internal links, CWV budgets, responsive design.
  3. Analytics & Tracking – UTMs, event triggers, conversion modules, A/B test configs.
  4. Launch Controls – staging reviews, smoke tests, rollback plan, comms schedule.
  5. Post-launch Validation – indexation check, monitoring alerts, performance baseline snapshot.

Templates

  • Publishing runbook (steps, owner, evidence link, status).
  • QA checklist (content, technical, analytics, accessibility).
  • Launch log capturing timestamps, environments, and approvals.

Tips

  • Timebox approvals with clear SLAs to keep calendars on track.
  • Automate checklist reminders via project tools or Git hooks.
  • Pair with deploy-optimizations to keep evidence attached to each task.

Comments

Markdown supported