fetch-homepage-content▌
example.com/fetch-homepage-content-3h5vgl · updated May 21, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Fetch the example.com homepage and return its h1 heading, first paragraph text, and the trailing 'Learn more' link as structured JSON. Read-only, no auth, no anti-bot.
| name | fetch-homepage-content |
| title | Fetch example.com Homepage Content |
| description | >- Fetch the example.com homepage and return its h1 heading, first paragraph text, and the trailing 'Learn more' link as structured JSON. Read-only, no auth, no anti-bot. |
| website | example.com |
| category | reference |
| tags | - reference - fetch - html-parse - smoke-test - iana |
| source | 'browserbase: agent-runtime 2026-05-19' |
| updated | '2026-05-19' |
| recommended_method | api |
| alternative_methods | - method: browser rationale: >- Works identically (browse open + browse get markdown body returns the same content cleanly), but spinning up a cloud session is ~2 orders of magnitude more expensive than a single HTTP fetch for a fully server-rendered static page. Only worth using if your harness has no HTTP fetch primitive or you specifically need a visual screenshot. |
| verified | false |
| proxies | false |
Fetch example.com Homepage Content
Purpose
Read-only extraction of the example.com homepage and return its h1 heading text and the first paragraph text (and, optionally, the trailing "Learn more" link). example.com is the IANA-reserved illustrative domain whose homepage is a single static HTML document served by Cloudflare — no JavaScript rendering, no anti-bot, no authentication. The optimal path is a raw HTTP fetch and a minimal HTML parse; a browser session is not required.
When to Use
- An agent needs a known-stable, zero-friction target to smoke-test its fetch + parse pipeline end to end.
- A documentation, tutorial, or eval harness needs the canonical "hello world" web payload returned in a normalized shape.
- A connectivity / DNS / TLS check needs to confirm not just that
example.comis reachable but that the expected document body is being served (e.g. detecting a captive portal or middlebox interception). - A demo wants to show a JSON-shaped extraction of
h1+ lead paragraph from any URL, using example.com as the safe reference input.
Workflow
The recommended path is a single HTTP fetch. example.com serves a complete, server-rendered HTML document — there is nothing for a browser to do that curl-equivalent tooling cannot.
-
Fetch the page with
browse cloud fetch. No--proxies, no--verified, no session needed:browse cloud fetch https://example.comThe response is a JSON envelope; the
contentfield holds the raw HTML andstatusCodeshould be200. -
Parse the HTML for the two required fields. The document structure is stable: a single
<h1>inside a<div>, followed by two<p>elements (the descriptive paragraph and a paragraph containing only the "Learn more"<a>). Any minimal parser works — examples:- Node:
cheerio→$('h1').text()and$('p').first().text(). - Python:
BeautifulSoup→soup.h1.get_text(strip=True)andsoup.find('p').get_text(strip=True). - Regex (acceptable because the document is hand-authored and stable):
/<h1>([^<]+)<\/h1>/and/<p>([^<]+)<\/p>/.
- Node:
-
Normalize whitespace on the extracted strings (collapse runs of whitespace, strip leading/trailing) before returning. The served HTML is minified onto a single line, so naive substring extraction will not have stray newlines, but downstream consumers should still be defensive.
-
Return the structured shape shown in Expected Output.
Browser fallback
Only worth using if your harness has no HTTP-fetch primitive at all, or if you want a visual screenshot for a marketplace card. Cost is ~2 orders of magnitude higher than browse cloud fetch (cloud session spin-up dominates).
sid=$(browse cloud sessions create --keep-alive | jq -r .id)
export BROWSE_SESSION="$sid"
browse open https://example.com --remote
browse get markdown body --remote
# {"markdown":"# Example Domain\n\nThis domain is for use in documentation examples without needing permission. Avoid use in operations.\n\n[Learn more](https://iana.org/domains/example)"}
browse cloud sessions update "$sid" --status REQUEST_RELEASE
The browse get markdown body output is already cleanly normalized; split on \n\n to separate the heading line from the first paragraph.
Site-Specific Gotchas
- The page text is not historical-museum content — it changed. The widely-quoted older version that began "This domain is for use in illustrative examples in documents…" is no longer what's served. As of
Last-Modified: Thu, 14 May 2026 05:31:28 GMT, the lead paragraph reads: "This domain is for use in documentation examples without needing permission. Avoid use in operations." Do not hardcode the paragraph text in tests — extract it at runtime, or your skill will silently rot the next time IANA updates the copy. - Cloudflare edge caching is aggressive (
Cf-Cache-Status: HIT,Ageheader in the tens of thousands of seconds is normal). TheLast-Modifiedheader is therefore the authoritative freshness signal, notDate. If you need to detect a content change, compareLast-Modifiedrather than re-fetching on a timer. - Allowed methods are
GET, HEADonly (Allow: GET, HEAD). Do not waste retries onPOST/OPTIONS; the origin will refuse them. - No
robots.txtenforcement and no rate limiting observed at single-digit requests per minute. This is the IANA reference domain, intentionally permissive for documentation use. Do not abuse it (do not use it as a load-test target — there are dedicated services for that). example.com,example.org,example.net, andexample.eduall serve the same payload from the same infrastructure. If your skill is generalized for "IANA example domains", treat them interchangeably; only the host header in the request differs.- The page does NOT include the host string
example.comin its visible body — only the title (<title>Example Domain</title>) and theh1(Example Domain) name the page. Do not assume the body contains the domain literal. - There is no API in the conventional sense. The HTML document itself is the API. Do not waste iterations probing for
/api/,/v1/, GraphQL, or sitemaps — none exist. Content-Encoding: br(Brotli) is returned by default.browse cloud fetchand modern HTTP clients decode this transparently; rawsocket-level clients will need to advertiseAccept-Encoding: identityif they cannot decode Brotli.
Expected Output
{
"url": "https://example.com",
"status": 200,
"fetched_at": "2026-05-19T00:00:43Z",
"last_modified": "2026-05-14T05:31:28Z",
"title": "Example Domain",
"h1": "Example Domain",
"first_paragraph": "This domain is for use in documentation examples without needing permission. Avoid use in operations.",
"learn_more_url": "https://iana.org/domains/example"
}
If you cannot reach the origin (DNS failure, TLS failure, captive portal returning a non-Example Domain body), return an error shape rather than fabricated content:
{
"url": "https://example.com",
"status": 0,
"error": "fetch_failed",
"error_detail": "ENOTFOUND example.com"
}
If you reach the origin but the document shape has drifted (no h1, or zero p elements found), return a partial-success shape with the raw HTML attached for debugging — never silently substitute defaults:
{
"url": "https://example.com",
"status": 200,
"h1": null,
"first_paragraph": null,
"error": "unexpected_document_shape",
"raw_html": "<!doctype html>..."
}
How to use fetch-homepage-content on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add fetch-homepage-content
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches fetch-homepage-content from GitHub repository example.com/fetch-homepage-content-3h5vgl and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate fetch-homepage-content. Access the skill through slash commands (e.g., /fetch-homepage-content) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★35 reviews- ★★★★★Mateo Tandon· Dec 20, 2024
fetch-homepage-content fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ganesh Mohane· Dec 4, 2024
Solid pick for teams standardizing on skills: fetch-homepage-content is focused, and the summary matches what you get after install.
- ★★★★★Mateo Gupta· Nov 11, 2024
fetch-homepage-content is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Charlotte Abbas· Oct 2, 2024
Keeps context tight: fetch-homepage-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Min Okafor· Sep 21, 2024
Solid pick for teams standardizing on skills: fetch-homepage-content is focused, and the summary matches what you get after install.
- ★★★★★Diego Robinson· Sep 13, 2024
fetch-homepage-content reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Charlotte Bansal· Sep 13, 2024
fetch-homepage-content has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Piyush G· Sep 9, 2024
Registry listing for fetch-homepage-content matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Diya Taylor· Sep 1, 2024
Keeps context tight: fetch-homepage-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Shikha Mishra· Aug 28, 2024
fetch-homepage-content reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 35