← RefreshAgentCONTENT HISTORY

Update to RefreshAgent

Snapshot Oct 24, 2026 · 13:46 UTC · version 1.0.3

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save RefreshAgent and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use RefreshAgent as a data and deterministic-compute substrate to create novel, defensible SEO/AEO knowledge instead of generic LLM summaries. Use for programmatic SEO, research, information-gain analysis, data-led content and refresh decisions.",
  "included_files": [],
  "name": "computed-knowledge-seo",
  "skill_md_contents": "---\nname: computed-knowledge-seo\ndescription: Use RefreshAgent as a data and deterministic-compute substrate to create novel, defensible SEO/AEO knowledge instead of generic LLM summaries. Use for programmatic SEO, research, information-gain analysis, data-led content and refresh decisions.\n---\n\n# Computed Knowledge SEO\n\nRefreshAgent should provide evidence and deterministic computation. ChatGPT should do semantic reasoning with its own tokens.\n\nCore rule:\n\n> Compute, don't summarize. Create facts the model could not know without the connected data.\n\n## When to use this skill\n\nUse it when the user asks what to add to a page, how to refresh declining content, how to differentiate from ranking competitors, how to build programmatic SEO pages, or how to turn datasets into SEO/AEO content.\n\nDo not invoke it for a simple performance lookup when the user only needs clicks, impressions, CTR, rankings, or a traffic explanation.\n\n## Workflow\n\n1. Start from a valuable user/search question.\n2. Inventory independent datasets and identify the common entity/time/geography model.\n3. Separate observed facts, deterministic derived facts, and bounded inferred claims.\n4. Prefer joins, calculations, comparisons, trends, history, and first-party observations over generic prose.\n5. Maintain provenance for factual claims.\n6. Before proposing a scaled page family, state the new fact, comparison, trend, or decision each page exposes. If the answer is only “another row exists”, do not scale it.\n7. When evaluating an existing or proposed page against competing coverage, use the `information-gain` skill and `assess_information_gain` operator.\n8. Separate table-stakes competitor coverage from genuine differentiation.\n9. Prefer novel derived facts, independent source joins, historical evidence, and first-party data.\n\n## RefreshAgent execution rule\n\nDo not ask RefreshAgent to run another LLM for an external-agent workflow. Use RefreshAgent tools for data and deterministic operators, then reason in ChatGPT.\n\nFor a content refresh discovered from Search Console, a strong default chain is:\n\n`find_content_decay` or `find_biggest_losers` → page/query evidence → `collect_information_gain_evidence` → normalize atomic claims → `assess_information_gain` → recommend genuinely new computed knowledge.\n\nNever recommend “add more content” merely because a page is thin. Identify the new fact, comparison, calculation, historical observation, first-party evidence, or cross-dataset insight the update will add.\n"
}

SHA-256 of public snapshot: 904c03dd73351bdb81d626441eac0a7bfdeb0b504ecfb5ad93200b626c549fef