Cloudinary Docs

cloudinary-devs/skills/skills/platform/cloudinary-docs

作者 cloudinary-devse9283bf633c17126ead05a4ec9cd03ab085daa04MIT13 個星標收錄於 2026年10月9日更新於 2026年10月9日儲存庫昨天更新

Looks up implementation details in the latest Cloudinary docs via the relevant llms.txt file. Use when building code or answering questions relating to image or video uploads, management, SDKs, APIs, webhooks, or integrations. For topics covered by a specialized Cloudinary skill, prefer that skill. Use this skill alongside it when the full use-case requires capabilities outside that skill's scope.

AI 產生的概覽

查詢 Cloudinary 文件與程式碼範例,涵蓋圖片和影片 API、DAM、MediaFlows 及整合。

功能
此技能引導代理程式取得 Cloudinary 針對代理程式最佳化的 markdown 文件檔案(llms.txt 子檔案),並據此回答問題或撰寫程式碼。它會將主題對應到某個產品領域,例如圖片與影片 API、Cloudinary Assets(DAM)、MediaFlows 或整合,然後檢索相關文件頁面。產出是根據所取得文件的正確回答、設定步驟或程式碼實作。
適用情境
適用於涉及 Cloudinary 圖片或影片上傳、管理、轉換、SDK、API、webhook、DAM 功能、MediaFlows 或第三方整合的問題或實作工作。當更專門的 Cloudinary 技能只涵蓋使用情境的一部分時,它也可作為補充使用。
執行需求
需要網路存取以取得 Cloudinary 文件網址。不包含指令碼或套件,僅為指示性內容。

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.

ProductTopicSub-file URL
Image & Video APIsImage/video uploads, transformations, optimization, SDKs, APIs, webhooks, add-ons, embedding widgets or players in apps, or any programmatic/automation/at-scale image and video requirementshttps://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 needshttps://cloudinary.com/documentation/llms-cloudinary-assets.txt?install_source=skillspack&referrer=docs-skill
MediaFlowsPowerFlows, EasyFlows, workflow automation, flow blockshttps://cloudinary.com/documentation/llms-mediaflows.txt?install_source=skillspack&referrer=docs-skill
IntegrationsCloudinary integrations with 3rd party apps (WordPress, Shopify, Contentful, Salesforce, Adobe, etc.) or questions about implementing new integrationshttps://cloudinary.com/documentation/llms-integrations.txt?install_source=skillspack&referrer=docs-skill
Cross-product or unsureMultiple products, general, or unclear topichttps://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

Example 2: DAM question

Example 3: MediaFlows question

Example 4: Integration question

Example 5: Ambiguous upload question

Example 6: Transformation question (fallback: use only if no specialized skill covers this topic)

來源與署名

來源:cloudinary-devs/skills位於skills/platform/cloudinary-docs提交e9283bf

授權條款: MIT

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架