agentleFS
Sign inStart free
memi-designmemi-design/design-skills/skills/browser-research-agent/SKILL.md

browser-research-agent

Skill7 starsChanged 4 months agoMITView on GitHub

Compatibility workflow for browser-backed evidence capture. Deprecated: use web-research for primary-source research, citations, freshness, and gap analysis.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Run browser-backed research agents that capture evidence, citations, and source freshness.

    line 10
  2. Distinctive:

    Use this Note when a Memoire or Studio run needs browser research, web evidence, citation capture, source comparison.

    line 14
  3. Distinctive:

    Start with primary sources, then use secondary sources only to find more primary evidence.

    line 18
  4. Distinctive:

    Use screenshots for visual UI claims and direct API responses for machine-readable facts.

    line 20

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

Browser Research Agent

Deprecated compatibility slug. Use web-research for new work. This payload remains self-contained for clients that installed the historical name.

Run browser-backed research agents that capture evidence, citations, and source freshness.

When to Use

Use this Note when a Memoire or Studio run needs browser research, web evidence, citation capture, source comparison.

Workflow

  1. Start with primary sources, then use secondary sources only to find more primary evidence.
  2. Record source URL, access date, claim, confidence, and whether the fact is time-sensitive.
  3. Use screenshots for visual UI claims and direct API responses for machine-readable facts.
  4. Separate quotes from paraphrases and keep quoted excerpts short.
  5. Finish with an evidence table and a list of claims that still need verification.

Sources

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