Browser UseBrowser Skills
← Back to skills

Domain skill

ods

Markdown synced from browser-harness domain skills.

Host
ods
Files
1

Agent prompt

Use this skill

Copy this prompt into your coding agent to make it enable browser-harness domain skills and read this exact domain folder before automating.

Set up https://github.com/browser-use/browser-harness for me if it is not already installed. If setup is needed, read `install.md` first to install and connect it to my real browser. Then read `SKILL.md` for normal usage and always read `helpers.py` because that is where the browser-harness functions are.

Enable domain skills if they are not already enabled by setting `BH_DOMAIN_SKILLS=1` for browser-harness. Use the `ods` domain skill from `agent-workspace/domain-skills/ods/`. Read every markdown file for this domain before inventing an approach:
- agent-workspace/domain-skills/ods/fact-sheets.md

Use those domain-skill notes to complete my task for `ods` in my real browser. When you open a setup, verification, or task tab, activate it so I can see the active browser tab.

Skill contents

What the agent will read

public fact-sheet capture

fact-sheets.md

Source
  • Observed on ods.od.nih.gov in September 2026.
  • Fact-sheet URLs use /factsheets/<Nutrient>-HealthProfessional/ and
  • /factsheets/<Nutrient>-Consumer/. Confirm the audience in the visible title.
  • Try ordinary HTTP first. A plain request returned 403 while the same public
Show full markdown

Observed on ods.od.nih.gov in September 2026.

  • Fact-sheet URLs use /factsheets/<Nutrient>-HealthProfessional/ and /factsheets/<Nutrient>-Consumer/. Confirm the audience in the visible title.
  • Try ordinary HTTP first. A plain request returned 403 while the same public page rendered normally in Chrome. Do not archive a denial body as the fact sheet; a normal browser visit may provide the public article without login.
  • The rendered article contains the sheet, references, disclaimer and displayed update date. #fact-sheet contains the substantive sections. If capturing DOM, label it rendered article HTML, not the original HTTP response.
  • Locate sections by visible heading text, then use that heading's observed ID. Numeric IDs such as h18 are specific to a sheet's organization, not universal identifiers for the same topic on every nutrient page.
  • Some headings have duplicate generated IDs (heading-0, etc.). Prefer the actual heading element within the article rather than a global ID match.
  • Inline references include tooltip citation text in the DOM. Naive textContent or static HTML-to-text extraction can repeat full citations inside paragraphs. Keep the original capture, and distinguish displayed prose from tooltip text before doing content-length checks or extracting sentences.
  • Record the article's Updated date separately from retrieval time. A fresh capture does not mean the scientific content was updated that day.

The site's linked source records and original publications still need their own identity and scope checks; the fact-sheet capture is not review of every cited paper. No account access or form submission is needed for this workflow.