add-ai-access-scrapers
Skill2 starsChanged 7 months agoMITView on GitHub
Query AI Access sources with many scrape items and create a PR adding dedicated scrapers for them in perform_scrape_for_source.
In this repository11 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Call the get_ai_access_sources MCP tool to get all AI Access sources with more than 10 scrape items.
- Very specific: line 9
Read backend/api/services/source/source_service.py to see the current perform_scrape_for_source function and its existing patterns (REDDIT, …
- Distinctive: line 17
Create a git branch, commit the changes, and open a PR.
- Distinctive: line 19
If no sources can be converted to dedicated scrapers, report which sources were found and why they could not be converted.
≈ “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.
Files
Call the get_ai_access_sources MCP tool to get all AI Access sources with more than 10 scrape items.
For each source returned, read its aiAccessInstructions and sourceClientKey to understand what data it accesses and how. Then:
- Read
backend/api/services/source/source_service.pyto see the currentperform_scrape_for_sourcefunction and its existing patterns (REDDIT, TWITTER, NYC_OPEN_DATA, AI_ACCESS). - For each source, determine if you can replace the generic AI Access scraping with a dedicated client that fetches the data directly (e.g., via an API, RSS feed, or structured web request). Skip sources whose instructions describe access patterns that cannot be replicated without Claude (e.g., "search the web for..." or "navigate through a complex UI").
- For each source you can write a dedicated scraper for:
a. Create a new client module in
backend/api/services/source/that fetches the data. b. Create a new SourceAccessType choice in the backend and a migration. b. Add anelifbranch inperform_scrape_for_sourcethat checkssource.source_access_type == SourceAccessTypeand calls your new client, creating ScrapeItem records from the response. c. Place the new branch before the genericelif source.source_access_type == SourceAccessType.AI_ACCESSbranch so it takes priority. - Create a git branch, commit the changes, and open a PR. In the PR description, list each source ID and what dedicated scraper was added for it.
If no sources can be converted to dedicated scrapers, report which sources were found and why they could not be converted.
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
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.

