AgentStack
SKILL verified MIT Self-run

Refresh Vs New Content

skill-marketingskills-seo-refresh-vs-new-content · by marketingskills

Decide whether to update, consolidate, prune, or create new content for a given page or topic. Use when Codex needs to recommend the best content action based on performance data and competitive analysis.

No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-marketingskills-seo-refresh-vs-new-content

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Refresh Vs New Content? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Refresh vs New Content

Overview

Given a page and its performance data, decide the best content action: refresh (update existing), consolidate (merge pages), prune (remove or redirect), or create new. Uses traffic trends, SERP competitiveness, content quality, and business value.

Inputs

  • Page URL and current performance data (GSC/GA4)
  • Content quality assessment (depth, freshness, accuracy)
  • SERP competitive analysis for the page's primary query
  • Business value of the topic

Workflow

  1. Assess the page's current content quality:
  • Outdated information or examples
  • Thin content compared to top SERP results
  • Missing entities or sections
  • Poor user engagement signals (bounce rate, time on page)
  1. Assess traffic potential:
  • Total search demand for the primary query
  • Authority feasibility (can this site rank?)
  • Seasonality or trend direction
  1. Decision matrix:
  • Refresh: page has good bones, query is stable or growing, authority exists
  • Consolidate: page is thin, overlaps with another stronger page on the site
  • Prune: query demand declining, page has no unique value, better to redirect authority
  • Create new: new query opportunity, site has no existing coverage, authority is feasible
  1. For refresh: pass to content-refresh-brief for the detailed brief.
  2. For create new: pass to seo-content-brief.
  3. For consolidate/prune: recommend the target URL or redirect destination.

Output

Content action recommendation with rationale, expected impact, and handoff to the relevant skill.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.