AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

cloudflare-deploy

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.

Original source
openai
License
Apache-2.0
Pinned revision
49f948faa9258a0c61caceaf225e179651397431

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read openai--cloudflare-deploy at revision 49f948faa9258a0c61caceaf225e179651397431, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 309

references/browser-rendering/README.md

Cloudflare Browser Rendering Skill Reference

Description: Expert knowledge for Cloudflare Browser Rendering - control headless Chrome on Cloudflare's global network for browser automation, screenshots, PDFs, web scraping, testing, and content generation.

When to use: Any task involving Cloudflare Browser Rendering including: taking screenshots, generating PDFs, web scraping, browser automation, testing web applications, extracting structured data, capturing page metrics, or automating browser interactions.

Decision Tree

REST API vs Workers Bindings

Use REST API when:

  • One-off, stateless tasks (screenshot, PDF, content fetch)
  • No Workers infrastructure yet
  • Simple integrations from external services
  • Need quick prototyping without deployment

Use Workers Bindings when:

  • Complex browser automation workflows
  • Need session reuse for performance
  • Multiple page interactions per request
  • Custom scripting and logic required
  • Building production applications

Puppeteer vs Playwright

| Feature | Puppeteer | Playwright | |---------|-----------|------------| | API Style | Chrome DevTools Protocol | High-level abstractions | | Selectors | CSS, XPath | CSS, text, role, test-id | | Best for | Advanced control, CDP access | Quick automation, testing | | Learning curve | Steeper | Gentler |

Use Puppeteer: Need CDP protocol access, Chrome-specific features, migration from existing Puppeteer code Use Playwright: Modern selector APIs, cross-browser patterns, faster development

Tier Limits Summary

| Limit | Free Tier | Paid Tier | |-------|-----------|-----------| | Daily browser time | 10 minutes | Unlimited* | | Concurrent sessions | 3 | 30 | | Requests per minute | 6 | 180 |

*Subject to fair-use policy. See gotchas.md for details.

Reading Order

New to Browser Rendering:

  1. configuration.md - Setup and deployment
  2. patterns.md - Common use cases with examples
  3. api.md - API reference
  4. gotchas.md - Avoid common pitfalls

Specific task:

REST API users:

Workers users:

In This Reference

  • configuration.md - Setup, deployment, wrangler config, compatibility
  • api.md - REST API endpoints + Workers Bindings (Puppeteer/Playwright)
  • patterns.md - Common patterns, use cases, real examples
  • gotchas.md - Troubleshooting, best practices, tier limits, common errors

See Also