Cloudinary Docs
Pull current Cloudinary upload, management, SDK, API, and webhook answers from official llms.txt docs while implementing media features.
Overview
cloudinary-docs is an agent skill for the Build phase that fetches up-to-date Cloudinary implementation guidance from official llms.txt documentation.
Install
npx skills add https://github.com/cloudinary-devs/skills --skill cloudinary-docsWhat is this skill?
- Agent-optimized lookups against Cloudinary llms.txt documentation slices
- Covers image and video upload, management, SDKs, APIs, webhooks, and account-level topics
- Explicit rule to prefer specialized Cloudinary skills first, then this skill for gaps
- Sub-file index overview for targeting the right doc section
- MIT-licensed maintainer skill at metadata version 1.1.0
- Skill metadata version 1.1.0
- Documentation sourced from agent-optimized Cloudinary llms.txt files
Adoption & trust: 1 installs on skills.sh; 7 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are implementing Cloudinary uploads or media pipelines but agent answers about SDKs, APIs, and webhooks may be outdated or incomplete.
Who is it for?
Indie developers integrating Cloudinary who need doc-accurate snippets for uploads, management, webhooks, or cross-SDK questions outside a narrow Cloudinary skill.
Skip if: Replacing a dedicated Cloudinary transformation or framework SDK skill when that skill already owns the whole task end to end.
When should I use this skill?
When building or answering questions about image or video upload, management, SDKs, APIs, webhooks, or Cloudinary integrations, or when filling gaps outside a specialized Cloudinary skill.
What do I get? / Deliverables
Your agent grounds code and explanations in current Cloudinary docs, complementing specialized Cloudinary skills for any capabilities they do not cover.
- Doc-grounded code examples and API references for the requested Cloudinary capability
Recommended Skills
Journey fit
Build is where solo builders wire uploads, delivery URLs, and webhooks; doc lookup belongs on the integration shelf even when UI displays the assets. Integrations subphase matches SDK and API wiring that sits beside your app backend or frontend media components.
How it compares
Use as live doc retrieval alongside specialized Cloudinary skills—not as a substitute for vendor SDK skills or generic web search.
Common Questions / FAQ
Who is cloudinary-docs for?
Solo and indie builders using coding agents to integrate Cloudinary image and video upload, delivery, and management into their products.
When should I use cloudinary-docs?
During Build integrations when you need SDK methods, API endpoints, webhooks, or account settings from current docs—especially when a specialized Cloudinary skill only covers part of the feature.
Is cloudinary-docs safe to install?
It is a read-only documentation lookup skill; review the Security Audits panel on this Prism page and follow Cloudinary credential hygiene for any code it helps you write.
SKILL.md
READMESKILL.md - Cloudinary Docs
# Cloudinary Documentation Helps developers integrate Cloudinary into their applications by providing documentation and code examples retrieved directly from the agent-optimized markdown files in the Cloudinary documentation. ## When to Use - When a user asks questions or requests code implementation relating to image or video upload, management, SDKs, APIs, webhooks, or integrations - For topics covered by a more specialized Cloudinary skill (e.g. transformations, React SDK): prefer that skill. Use this skill alongside it when the full use-case also requires capabilities outside that skill's scope. - General Cloudinary documentation lookup (account settings, webhooks, DAM features) - Looking up specific Cloudinary API endpoints or SDK methods - When a specialized Cloudinary skill handles part of a use-case, use this skill to cover the remaining capabilities it doesn't address, not as a substitute for it. ## Sub-file Index Overview The main documentation llms.txt file is split into product-specific sub-files. **Go directly to the relevant sub-file** according to the descriptions below. Do not fetch the main llms.txt first unless the topic spans multiple products or you are unsure. | Product | Topic | Sub-file URL | |---|---|---| | Image & Video APIs | Image/video uploads, transformations, optimization, SDKs, APIs, webhooks, add-ons, embedding widgets or players in apps, or any programmatic/automation/at-scale image and video requirements | https://cloudinary.com/documentation/llms-image-and-video-apis.txt?install_source=skillspack&referrer=docs-skill | | Cloudinary Assets (DAM) | Digital Asset Management (DAM), Media Library, folders, metadata, collections, creative workflows, portals, digital rights, or any Cloudinary Console or UI-based asset management needs | https://cloudinary.com/documentation/llms-cloudinary-assets.txt?install_source=skillspack&referrer=docs-skill | | MediaFlows | PowerFlows, EasyFlows, workflow automation, flow blocks | https://cloudinary.com/documentation/llms-mediaflows.txt?install_source=skillspack&referrer=docs-skill | | Integrations | Cloudinary integrations with 3rd party apps (WordPress, Shopify, Contentful, Salesforce, Adobe, etc.) or questions about implementing new integrations | https://cloudinary.com/documentation/llms-integrations.txt?install_source=skillspack&referrer=docs-skill | | Cross-product or unsure | Multiple products, general, or unclear topic | https://cloudinary.com/documentation/llms.txt?install_source=skillspack&referrer=docs-skill | ## Instructions **Note:** If a more specialized Cloudinary-specific skill covers the user's topic, defer to that skill first. Invoke this docs skill in addition, not as a substitute, and only if the full use-case also requires capabilities outside that skill's scope. When using this skill to answer image and video upload, management, optimization, or transformation questions or when implementing Cloudinary code: 1. **Identify the product area**: Refer to the [Sub-file Index table](#sub-file-index-overview) above and identify the matching row. 2. **Fetch the relevant sub-file directly per the table above** (skip the main llms.txt unless the topic is cross-product or unclear) 3. **Analyze the sub-file** to identify which specific documentation URLs are most relevant 4. **Retrieve** those specific markdown documentation URLs (you can make multiple calls if needed) 5. **Use the fetched documentation** to provide a comprehensive, accurate answ