AGENTIC MEMORY

Skills

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

← Back to Skills

cloudflare

Discover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation.

Original source
cloudflare
License
Apache-2.0
Pinned revision
e44f580f9c4fa3bf268e284ae7706c7954ba31fd

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

Ask your assistant

Use Agentic Memory skills to read cloudflare--cloudflare at revision e44f580f9c4fa3bf268e284ae7706c7954ba31fd, 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 · 135

references/secrets-store/gotchas.md

Secrets Store troubleshooting

Start with the failing operation and fetch its documentation before changing credentials or bindings.

| Symptom or decision | What to check | Documentation | |---------------------|---------------|---------------| | Deployment cannot attach a secret | Selected account, caller's binding permission, and the secret's consuming-service scope; metadata read permission alone is insufficient | Access control | | Secret is missing or the wrong value is used | Store, secret name, binding name, and selected deployment environment | Workers integration, Wrangler environments | | Secret works in production but fails locally | Local secret provisioning and the management command's local/remote target | Workers integration, Wrangler commands | | CLI update, retrieval, or deletion fails | The operation's required identifier and flags; a secret name is not interchangeable with its ID | Wrangler commands | | Binding is treated as a string or has incorrect types | Asynchronous account-secret access and generated configuration types | Runtime access, TypeScript | | Quota or value-size validation fails | Current account quota and the requested operation's schema | Secrets Store REST API | | Regional or integration support is unclear | Current product availability and supported consumers | Product overview |

Do not diagnose failures by printing secret values or returning raw errors to clients. Check metadata and sanitized operation context. Validate JSON or other structured values before consuming them, and handle retrieval or parsing failures at the application's error boundary.

Before deleting a secret to fix a binding conflict or quota problem, identify all consumers. Follow secret management and the rotation decisions in patterns.md; removing a shared credential can affect multiple services.

See configuration.md for setup and api.md for API selection.