agentleFS
Sign inStart free
blisspixelblisspixel/primr/skills/scrape-strategy/SKILL.md

scrape-strategy

Skill3 starsChanged 24 days agoApache-2.0View on GitHub

Guide mode selection when site scraping is weak, blocked, or low quality. Use when the user asks why scraping failed or how Primr should proceed on a protected site.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. pueo-labs/primr★ 3100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the bottleneck is site access rather than report writing.

    line 18
  2. Very specific:

    Read primr://research/modes to compare scrape, deep, full, and premium behavior.

    line 22
  3. Very specific:

    Use references/tiers.md only when you need tier-level scraping context.

    line 24
  4. Very specific:

    Prefer deep when the target site is heavily protected or first-party signal is sparse.

    line 29
  5. Distinctive:

    Do not promise exact success percentages unless the run data already shows them.

    line 31

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

Scrape Strategy

Purpose

Use this skill when the bottleneck is site access rather than report writing. Focus on deciding whether to stay in scrape-capable modes or pivot to external research.

Workflow

  1. Read primr://research/modes to compare scrape, deep, full, and premium behavior.
  2. Review current run state through primr://research/status or check_jobs.
  3. Use references/tiers.md only when you need tier-level scraping context.
  4. Recommend the smallest viable change: retry, change mode, or accept partial coverage.

Decision Rules

  • Prefer deep when the target site is heavily protected or first-party signal is sparse.
  • Stay with scrape or full when first-party pages are the core evidence source.
  • Do not promise exact success percentages unless the run data already shows them.
  • Escalate from site troubleshooting to mode selection quickly; avoid over-explaining scrape internals unless the user asks.

Example

User: The site seems blocked

1. Read primr://research/status
2. Read primr://research/modes
3. Explain whether deep mode is the better fit
4. If needed, estimate_run(company_url="https://example.com", mode="deep")

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