agentleFS
Sign inStart free
marketingskillsmarketingskills/seo/skills/content-refresh-brief/SKILL.md

content-refresh-brief

Skill7 starsChanged 5 months agoMITView on GitHub

Produce a focused refresh brief for a declining page. Use when Codex needs to research SERP intent, competitor content, entity coverage, and internal link opportunities to create an actionable page refresh plan.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search the page's primary query in a current SERP.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Refresh Brief

Overview

Given a URL and optionally its GSC/GA4 performance data, produce a structured refresh brief that covers SERP intent analysis, entity gaps, content outline, internal link plan, and technical recommendations.

Inputs

  • URL of the page to refresh
  • Current GSC performance (clicks, impressions, CTR, avg position, top queries)
  • Prior period GSC performance for comparison
  • Optional: page content (if the user pastes it)
  • Optional: GA4 engagement or conversion data

Workflow

  1. Search the page's primary query in a current SERP.
  2. Analyze top 5 organic results for:
    • Content format (guide, list, tool, video, etc.)
    • Content depth (word count, section count, entities covered)
    • Date freshness (when each page was last updated)
    • SERP features present (featured snippets, People Also Ask, video, etc.)
  3. Compare current page content against SERP expectations:
    • Does it match the dominant content format?
    • Are key entities missing?
    • Is the content depth competitive?
    • Is the page fresh enough?
  4. Review GSC query data to identify:
    • Queries with declining CTR despite stable impressions
    • Queries where the page ranks but doesn't satisfy intent
    • Queries from the prior period that stopped driving traffic
  5. Recommend:
    • Content changes (restructure, expand, add sections, update data)
    • Technical changes (title, meta description, schema, canonical)
    • Internal link additions (from high-traffic pages)
    • Entities to add or strengthen
  6. Estimate effort and expected recovery.

Output Format

## Refresh Brief: /page-url

### Current Performance
| Metric | Current | Prior | Change |
|---|---|---|---|

### SERP Intent Analysis
[Format, depth, freshness expectations from top results]

### Gap Analysis
| Gap | Competitor Example | Our Action |
|---|---|---|

### Recommended Content Changes
1. [Action with details]

### Recommended Technical Changes
1. [Action with details]

### Internal Link Plan
| Source Page | Anchor Text | Rationale |
|---|---|---|

### Effort Estimate
[Low / Medium / High] — [estimated hours]

### Expected Recovery
[Estimated click/impression recovery range]

Related Skills

  • traffic-decay-detector — identifies which pages need briefs.
  • serp-authority-mark — checks authority feasibility for the target query.
  • title-meta-rewriter — produces title/meta alternatives for the refresh.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free