agentleFS
Sign inStart free
ai-search-guruai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/skills/refresh/SKILL.md

refresh

Skill432 starsChanged 11 days agoMITView on GitHub

Updates dates, numbers and examples from Sources; flags what needs the user.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 7

    Distinctive

    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:

    When no page is named, list the drafts that changed longest ago and ask which one to refresh.

    line 17
  2. Distinctive:

    Update what a source supports: a figure or date from the page's own sources, the person's messages, or a page read in this chat.

    line 29
  3. Distinctive:

    Keep the passages AI quotes word for word, unless the person asks to change them and knows they are quoted.

    line 31
  4. Distinctive:

    Add an "Updated on [date]" line.

    line 32
  5. Distinctive:

    Don't invent new facts or figures to make the page look fresh.

    line 44
  6. Distinctive:

    Don't change a date on the page unless its content changed.

    line 45
  7. Distinctive:

    Never publish yourself: the app decides whether a page goes live, and asks the person unless an Admin allowed this agent to go live on its …

    line 46

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “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

Refresh for this year

Bring an older page up to date: its dates, numbers and examples, without losing what AI engines already quote from it.

When to use

  • "Refresh our pricing guide for this year", "Which pages are out of date?", "Update this draft's numbers."
  • When no page is named, list the drafts that changed longest ago and ask which one to refresh.

What to read

  1. get_draft for the page: its passages, the sources it cites, and which passages AI quotes now (locked).
  2. list_drafts when no page is named: the drafts, latest changed first, to find the oldest.
  3. get_site_audit_summary, then list_site_audit_issues for the page's latest audit: freshness, date markup and the other failed checks.
  4. list_ai_answers for one or two prompts the page serves: what AI cites now, and what this page no longer answers.

Steps

  1. Find what is dated: years, "last year", figures, prices, screenshots described in the text, examples, product names that changed.
  2. Update what a source supports: a figure or date from the page's own sources, the person's messages, or a page read in this chat. Each new number names its source.
  3. Flag what needs the person: a figure no source supports stays as a [placeholder], such as [current customer count], in a to-do list.
  4. Keep the passages AI quotes word for word, unless the person asks to change them and knows they are quoted.
  5. Add an "Updated on [date]" line.

Output

  1. A table: Passage, What changed, Source (or "needs you").
  2. The updated passages, ready to paste.
  3. The to-do list of what only the person can supply.

When the person wants it kept, save it as a new version with create_draft, method optimize, with the live page's address as its source; the app asks them first when it should. In an agent's run nobody is there to ask: always save it with its tool, and the app holds it for approval where the agent's mode needs it.

Don't

  • Don't invent new facts or figures to make the page look fresh.
  • Don't change a date on the page unless its content changed.
  • Never publish yourself: the app decides whether a page goes live, and asks the person unless an Admin allowed this agent to go live on its own.

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