AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Content Refresher

skill-aaron-he-zhu-aaron-marketing-skills-content-refresher · by aaron-he-zhu

Use when the user asks to "update outdated content" or "fix traffic/ranking decay"; scores decay, prioritizes refresh work, and produces an update plan with GEO and republishing guidance. Not for net-new content — use seo-content-writer. 内容更新/排名恢复

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

Install

$ agentstack add skill-aaron-he-zhu-aaron-marketing-skills-content-refresher

✓ 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-aaron-he-zhu-aaron-marketing-skills-content-refresher)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Content Refresher? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Content Refresher

Identifies outdated content, scores decay/freshness, prioritizes refresh work, and produces update plans with GEO and republishing guidance.

Quick Start

Find content on [domain] that needs refreshing
Which of my blog posts have lost the most traffic?
Refresh this article for [current year]: [URL/content]
Update this content to outrank [competitor URL]: [your URL]
Create a content refresh strategy for [domain/topic]

Skill Contract

Expected output: a scored diagnosis, prioritized repair plan, and a short handoff summary ready for memory/audits/.

  • Reads: candidate URLs/content, traffic and ranking history, publish/update dates, and competitor examples.
  • Writes: a user-facing refresh plan (and optional refreshed content) plus a reusable summary that can be stored under memory/audits/.
  • Promotes: blocking defects, repeated weaknesses, fix priorities, and pending decisions to memory/open-loops.md.
  • Done when: decay drivers are identified with evidence; a refresh plan lists specific updates with a republish-date strategy; a Changes Made block and handoff summary are produced.
  • Primary next skill: use the Next Best Skill below when the repair path is clear.

Handoff Summary

> Emit the standard shape from [skill-contract.md §Handoff Summary Format](../../references/skill-contract.md).

Data Sources

Use ~~analytics, ~~search console, and ~~SEO tool when connected; otherwise ask for traffic data, ranking history, publish dates, candidate URLs, and competitor examples. See [CONNECTORS.md](../../CONNECTORS.md).

Instructions

Label every metric Measured (tool/export), User-provided, or Estimated (model inference); never present an estimate as measured; if a required metric is unavailable, mark it N/A — do not invent it.

When a user requests content refresh help:

  1. CORE-EEAT Quick Score — Estimate all 8 dimensions, prioritize red/yellow areas, and hand off to [content-quality-auditor](../../cross-cutting/content-quality-auditor/SKILL.md) for full scoring when needed.
  2. Identify Refresh Candidates — Use age, dated claims, declining traffic, lost rankings, broken links, SERP shifts, and missing topics.
  3. Analyze Page-Level Decay — Compare 6-month-old vs current performance, keyword deltas, SERP intent, competitor updates, and the why-refresh rationale.
  4. Define Updates Needed — Capture outdated elements, competitor/PAA gaps, SEO updates, GEO updates, links, images, sources, and dates.
  5. Create Refresh Plan — Specify title, structure, new sections, refreshed statistics, internal/external links, images, and validation requirements.
  6. Write Refresh Content — Draft updated intro, replacement sections, refreshed facts, FAQ answers, and Changes Made notes.
  7. Optimize for GEO — Add 40-60 word definitions, quotable statements, Q&A, dated citations, and standalone factual statements.
  8. Set Republishing Strategy — Use published-date update for 50%+ new content, last-updated date for 20-50%, original date for Reference: [references/refresh-templates.md](references/refresh-templates.md) has compact templates for steps 2-9.

Decision Gates

Stop and ask the user when:

  • A page is decayed enough that a rewrite may beat a refresh (e.g., outdated premise, intent shift, or >50% of content stale) — state the finding and ask: (1) refresh in place, or (2) rewrite as new content via [seo-content-writer](../../build/seo-content-writer/SKILL.md).

Continue silently (never stop for):

  • Missing analytics/ranking history — score decay from on-page signals (dated claims, broken links, stale stats), label findings Estimated, and proceed.
  • A request to "refresh" content that is actually net-new (no existing URL) — note the mismatch once and route to [seo-content-writer](../../build/seo-content-writer/SKILL.md) rather than fabricating a prior version.
  • Which republish-date treatment to apply — follow the Step 8 thresholds without asking.

Example

User: "Refresh my blog post about 'best cloud hosting providers'"

Output: CORE-EEAT quick score flags weak Referenceability, Experience, and Trust; recommends pricing refresh, broken-link fixes, author credential additions, affiliate disclosure, and a Changes Made block ready for republish.

> Reference: See [references/refresh-example.md](references/refresh-example.md) for the full worked example and checklist.

Tips for Success

Prioritize by ROI/search demand, make substantive improvements instead of date-only edits, add stronger evidence than competitors, track post-publish rankings/traffic, and treat every refresh as a GEO citation opportunity.

Save Results

Ask to save results; if yes, write a dated summary to memory/audits/content-refresher/YYYY-MM-DD-.md. Hand off veto-level risks to the auditor gate before any hot-cache marker.

Gate check recommended: Run content-quality-auditor on refreshed content before republishing.

Reference Materials

  • [Content Decay Signals](references/content-decay-signals.md) — Decay indicators, lifecycle stages, and refresh triggers by content type
  • [Refresh Templates](references/refresh-templates.md) — Compact templates for steps 2-9
  • [Refresh Example & Checklist](references/refresh-example.md) — Full worked example and pre/post-refresh checklist

Next Best Skill

Primary: [content-quality-auditor](../../cross-cutting/content-quality-auditor/SKILL.md) — re-score refreshed content before shipping.

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.