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/secrets-store/README.md

Cloudflare Secrets Store

Account-level encrypted secret management for Workers and AI Gateway.

Overview

Secrets Store: Centralized, account-level secrets, reusable across Workers Worker Secrets: Per-Worker secrets (wrangler secret put)

Architecture

  • Store: Container (1/account in beta)
  • Secret: String ≤1024 bytes
  • Scopes: Permission boundaries controlling access
    • workers: For Workers runtime access
    • ai-gateway: For AI Gateway access
    • Secrets must have correct scope for binding to work
  • Bindings: Connect secrets via env object

Regional Availability: Global except China Network (unavailable)

Access Control

  • Super Admin: Full access
  • Admin: Create/edit/delete secrets, view metadata
  • Deployer: View metadata + bindings
  • Reporter: View metadata only

API Token permissions: Account Secrets Store Edit/Read

Limits (Beta)

  • 100 secrets/account
  • 1 store/account
  • 1024 bytes max/secret
  • Production secrets count toward limit

When to Use

Use Secrets Store when:

  • Multiple Workers share same credential
  • Centralized management needed
  • Compliance requires audit trail
  • Team collaboration on secrets

Use Worker Secrets when:

  • Secret unique to one Worker
  • Simple single-Worker project
  • No cross-Worker sharing needed

In This Reference

Reading Order by Task

| Task | Start Here | Then Read | |------|------------|-----------| | Quick overview | README.md | - | | First-time setup | README.md → configuration.md | api.md | | Add secret to Worker | configuration.md | api.md | | Implement access pattern | api.md | patterns.md | | Debug errors | gotchas.md | api.md | | Secret rotation | patterns.md | configuration.md | | Best practices | gotchas.md | patterns.md |

Files

See Also

  • workers - Worker bindings integration
  • wrangler - CLI secret management commands