
Cloudinary Docs
- 623 installs
- 11 repo stars
- Updated July 8, 2026
- cloudinary-devs/skills
cloudinary-docs is an agent skill that fetches up-to-date Cloudinary implementation guidance from official llms.txt documentation.
About
cloudinary-docs is Cloudinary’s documentation retrieval skill for coding agents. Solo builders adding photos, video, or transformations hit fast-moving SDK and API surfaces where stale training data causes broken uploads, wrong transformation parameters, or missed webhook events. The skill routes questions to the latest agent-oriented markdown in Cloudinary’s llms.txt index so answers mirror what the docs site publishes now. When a narrower Cloudinary skill already owns part of the job—React SDK flows or transformation recipes—you should start there and use cloudinary-docs only for the rest of the use case, such as general account settings, DAM features, or endpoints the specialized skill does not cover. That division keeps implementations aligned with vendor guidance without pretending one skill replaces the whole platform. Invoke it during Build whenever you are writing integration code or explaining Cloudinary behavior to teammates through the agent.
- 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
Cloudinary Docs by the numbers
- 623 all-time installs (skills.sh)
- Ranked #363 of 1,335 Generative Media skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cloudinary-devs/skills --skill cloudinary-docsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 623 |
|---|---|
| repo stars | ★ 11 |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 8, 2026 |
| Repository | cloudinary-devs/skills ↗ |
What it does
Pull current Cloudinary upload, management, SDK, API, and webhook answers from official llms.txt docs while implementing media features.
Who is it for?
Best when you're integrating Cloudinary and 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 you get
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
By the numbers
- Skill metadata version 1.1.0
- Documentation sourced from agent-optimized Cloudinary llms.txt files
Files
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 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 answer or code implementation.
Example Workflows
Example 1: SDK question
- User asks: "How do I install and use the Node.js SDK for Cloudinary?"
- Topic maps to Image & Video APIs → fetch https://cloudinary.com/documentation/llms-image-and-video-apis.txt?install_source=skillspack&referrer=docs-skill
- Identify SDK-related pages and provide installation instructions and usage examples or help implement the request in the user's code.
Example 2: DAM question
- User asks: "How do I set up approval workflows for assets in the Media Library?"
- Topic maps to Cloudinary Assets (DAM) → fetch https://cloudinary.com/documentation/llms-cloudinary-assets.txt?install_source=skillspack&referrer=docs-skill
- Identify relevant pages like "dam_admin_creative_approval_flows.md"
- Fetch the specific documentation and provide setup steps
Example 3: MediaFlows question
- User asks: "How do I build a PowerFlow that auto-moderates uploaded images?"
- Topic maps to MediaFlows → fetch https://cloudinary.com/documentation/llms-mediaflows.txt?install_source=skillspack&referrer=docs-skill
- Identify relevant pages like "mediaflows_build_flow.md" or "mediaflows_moderation_powerflow.md"
- Fetch the specific documentation and provide a flow-building walkthrough
Example 4: Integration question
- User asks: "How do I connect Cloudinary to my WordPress site?"
- Topic maps to Integrations → fetch https://cloudinary.com/documentation/llms-integrations.txt?install_source=skillspack&referrer=docs-skill
- Identify relevant pages like "wordpress_integration.md"
- Fetch the specific documentation and provide setup instructions
Example 5: Ambiguous upload question
- User asks: "How do I upload images to Cloudinary?"
- First, determine whether the user wants to upload programmatically (via SDK/API) or via the Console UI (DAM)
- If programmatic → fetch https://cloudinary.com/documentation/llms-image-and-video-apis.txt?install_source=skillspack&referrer=docs-skill
- Identify relevant pages like "image_upload.md" or "upload_api.md"
- Retrieve those specific pages and provide an answer with code examples
- If via the Console UI (DAM) → fetch https://cloudinary.com/documentation/llms-cloudinary-assets.txt?install_source=skillspack&referrer=docs-skill
- Identify relevant pages like "dam_upload_store_assets.md" or "dam_admin_upload_presets.md"
- Retrieve those specific pages and provide step-by-step instructions for uploading via the Media Library.
- If unable to determine → fetch https://cloudinary.com/documentation/llms.txt?install_source=skillspack&referrer=docs-skill
- Look at documentation for both Image & Video APIs and Cloudinary Assets products
- Provide an answer covering both programmatic and UI-based upload options
Example 6: Transformation question (fallback: use only if no specialized skill covers this topic)
- User asks: "How do I resize and crop images?"
- Topic maps to Image & Video APIs → fetch https://cloudinary.com/documentation/llms-image-and-video-apis.txt?install_source=skillspack&referrer=docs-skill
- Identify relevant pages like "image_transformations.md" or "transformation_reference.md"
- Fetch the specific documentation and provide transformation syntax and examples or help implement the request in the user's code.
Related skills
How it compares
Use as live doc retrieval alongside specialized Cloudinary skills—not as a substitute for vendor SDK skills or generic web search.
FAQ
Who is cloudinary-docs for?
Developers 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.