agentleFS
Sign inStart free
press-passpress-pass/journalism-skills/skills/trusted-source-discovery/SKILL.md

trusted-source-discovery

Skill2 starsChanged 7 months agoMITView on GitHub

Scrapes RSS feeds supplied as an argument to discover sources for news articles.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    If the source is a social media site (i.e.

    line 10
  2. Distinctive:

    After creating all sources, summarize what was created including the returned source IDs.

    line 24

≈ “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

You will be given a comma-delimited list of RSS feed URLs. For each RSS feed:

  1. Fetch the feed and extract all links contained within it that do not share a domain with the feed itself.
  2. Identify the best sources. Good sources appear in many articles or are the only source in an article. Try to find sources that could spawn an article all on their own.
  3. If the source is a social media site (i.e. Reddit, Instagram etc.) follow the link to the social media site to find more reliable sources on that page.
  4. For each source, attempt to find an official API that contains the same information as the referenced link. Do not use 3rd-party copies of the data.

For each of the 20 best sources, call the add_source_from_source_discovery MCP tool with:

  • name: descriptive name of the source
  • aiAccessInstructions: how to access the source programmatically (API endpoint, scraping instructions, etc.)
  • whenItsImportant: when this source is newsworthy
  • sourceClientKey: object with api_key if needed and any other access metadata
  • isReferenceSource: is this source just a huge database that we can't get story leads from? Examples include 311 complaints, tax records, etc.

After creating all sources, summarize what was created including the returned source IDs.

RSS feeds to process: $ARGUMENTS

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