agentleFS
opencueopencue/cuecards/.agents/skills/content-refresher/SKILL.md

content-refresher

Skill6 starsChanged 3 months agoMITView on GitHub

Use when updating outdated content, fixing traffic/ranking decay, refreshing stats, adding new sections, or improving freshness signals. 内容更新/排名恢复

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Primary next skill: use the Next Best Skill below when the repair path is clear.

    line 94
  2. Distinctive:

    Use ~~analytics, ~~search console, and ~~SEO tool when connected.

    line 102
  3. Distinctive:

    When a user requests content refresh help:

    line 106
  4. Very specific:

    Ask to save results; if yes, write a dated summary to memory/audits/content-refresher/YYYY-MM-DD-<topic>.md.

    line 136
  5. Distinctive:

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

    line 138

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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: the current page or site state, symptoms, prior audits, and current priorities from AGENTS.md and the shared State Model when available.
  • Writes: a user-facing audit or optimization plan 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.
  • 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.

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.

Instructions

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 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 <20%; update schema, sitemap lastmod, cache, Search Console, and 4-6 week monitoring.
  9. Create Refresh Report -- Summarize completed changes, expected outcomes, owners, next review date, and open loops.

Reference: references/refresh-templates.md has compact templates for steps 2-9.

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

Reference data: references/content-decay-signals.md covers decay signals, lifecycle stages, refresh-vs-rewrite decisions, and content-type strategy.

Save Results

Ask to save results; if yes, write a dated summary to memory/audits/content-refresher/YYYY-MM-DD-<topic>.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

Next Best Skill

Primary: content-quality-auditor -- re-score refreshed content before shipping.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.