agentleFS
Sign inStart free
whyashthakkerwhyashthakker/estack/skills/catch-up/SKILL.md

catch-up

Skill0 starsChanged 11 days agoMITView on GitHub

Brief the user on the AI news that matters to their project, not all AI news. Reads the project (stack, models, tools, dependencies), pulls current news and trends from the explainx.ai MCP server, and keeps only items that change something for this project, each with a "so what" and an action. Use when the user says "catch up", "what's new in AI", "what did I miss", "anything new for my stack", or asks if a recent model, tool, or release affects them.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use in-your-own-words, bro and 3 more.

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

    in-your-own-words

    Restate the user's goals and the problem they are trying to solve to check understanding. Manual invocation only; use when the user explicitly invokes in-your-own-words or requests this understanding check. Do not solve the task or rewrite the assistant's last answer.

    Also in 3 projects that use this

  • MicrosoftSkill

    bro

    Re-explain the previous assistant message in a much simpler way, for when the reply made you go 'bro what'. Use /bro to get a simpler version of the last answer in Plain Language + Chicago Manual of Style, with diagrams where they help.

    Also in 3 projects that use this

  • MicrosoftSkill

    blast-radius

    Assesses network dependency and shared-infrastructure exposure. Use when the user asks which services, customers, SLA policies, routes, or redundant links are affected by a network fault.

    Also in 3 projects that use this

  • termdockSkill

    recall

    Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.

    Also in 3 projects that use this

  • photon-groveSkill

    unslop

    Detects and rewrites generic, overly polished, or AI-sounding prose while preserving meaning. Use when the user asks to "unslop", humanize, de-AI, tighten, or review whether writing sounds generated.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only what you need:

    line 12
  2. Very specific:

    Write a one-line profile: "Next.js app, Claude Sonnet via the Anthropic SDK, Postgres, three MCP servers."

    line 17
  3. Distinctive:

    Keep an item only if it does at least one of these for this project:

    line 30
  4. Distinctive:

    Every item has a date and a link.

    line 51
  5. Distinctive:

    Do not edit code from this skill.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 20 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

Catch up

Goal: five minutes of reading that changes a decision, not a news feed.

1. Learn the project

Read only what you need:

  • Dependency files (package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml).
  • Model names and providers in code and config (search for claude-, gpt-, gemini, model:, provider SDK imports).
  • Agent setup (CLAUDE.md, AGENTS.md, .mcp.json, skills folders).

Write a one-line profile: "Next.js app, Claude Sonnet via the Anthropic SDK, Postgres, three MCP servers."

2. Get the news

With the explainx.ai MCP server connected (tool names may have a prefix):

  • get_ai_news for the last 7 days (or the window the user gives).
  • get_trending for what people read now.
  • search for each main item in the profile (each model, SDK, and key tool).

Without it: use web search, prefer primary sources (vendor changelogs, release notes, official blogs), and tell the user that live explainx.ai data was not used.

3. Filter hard

Keep an item only if it does at least one of these for this project:

  • Changes price, limits, or a deprecation date for something it uses.
  • Ships a new model or feature that does a current task better or cheaper.
  • Is a security issue in something it depends on.
  • Replaces a tool or pattern the project uses.

Everything else is noise. Zero items is a valid result: say "Nothing this week changes your project" and stop.

4. Report

For each item (most urgent first, five at most):

Title (date, source link)

  • What changed: one sentence with the real numbers.
  • So what: one sentence about this project.
  • Action: one concrete step, or "no action, watch".

Then one line: "Ask me to pick-model to compare prices" when a model item is on the list.

Rules

  • Every item has a date and a link. No link, no item.
  • Say "claimed" for vendor claims that no one has checked yet.
  • Do not edit code from this skill. Suggest the change; the user decides.

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