skills.rest
amoai-tech
amoai-techCOMMUNITY
Explore all skills by this author →
GitHub

cloudinary

Implements Cloudinary uploads, transformations, signed delivery, and webhook handling for MDE media workflows.

1|Updated Sep 15, 2026
Search Tags:#supabase#nextjs#cloudinary#image transformation#webhook verification#media uploads#signed uploads
One-click install
npx skills add https://github.com/amoai-tech/mdeai --skill cloudinary-amoai-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloudinary
Source: https://github.com/amoai-tech/mdeai/tree/main/.claude/skills/cloudinary
Command: npx skills add https://github.com/amoai-tech/mdeai --skill cloudinary-amoai-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cloudinary media work in MDE risks scope creep, leaked secrets, and unverified webhooks when there is no clear integration boundary. This Skill defines when Cloudinary is actually in scope and enforces safe upload, transformation, deletion, and webhook behavior. ## Core Features & Use Cases - Scope Verification: Confirms Cloudinary is genuinely required before introducing it, since the current repo has no active Cloudinary dependency. - Security Invariants: Keeps API and signing secrets server-side, prefers signed uploads, and verifies webhook signatures before side effects. - Data Ownership Boundaries: Keeps durable business metadata in Supabase while treating Cloudinary as media infrastructure only. - Use Case: When adding a venue photo upload flow, use this Skill to implement signed uploads, validate asset ownership before deletion, and hand off metadata persistence to the supabase skill. ## Quick Start Use the cloudinary skill to implement a signed image upload flow with webhook signature verification for the venue photos feature.

Frequently Asked Questions about cloudinary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement signed Cloudinary uploads in a Next.js app?▼

Signed Cloudinary uploads generate the signature on the server using the API secret, then the client uploads directly with that signature. Keep all signing secrets server-side and expose only the minimal upload route through the framework layer.

When should I use Cloudinary for media in this project?▼

Use Cloudinary only when the task explicitly involves uploads, transformations, delivery URLs, signatures, or webhooks. The current repo has no active Cloudinary dependency, so verify scope before introducing it as architecture.

How do I verify Cloudinary webhook signatures?▼

Verify the webhook signature against your signing secret before applying any side effects such as updating asset records. Reject requests with invalid signatures and test retry and missing-asset behavior.

Should Cloudinary store my application's media metadata?▼

No, Cloudinary is media infrastructure, not the business source of truth. Keep durable metadata such as ownership and associations in the application database, and validate resource ownership before destructive asset changes.

Who owns debugging when a Cloudinary integration fails?▼

Route root-cause diagnosis to systematic-debugging rather than guessing, while the Cloudinary specialist supplies domain evidence. For production-critical changes, require targeted tests and independent task verification before marking done.

Related Skills

Explore More Software Engineering Skills→
ryu-satoryu-sato

kiro-discovery

Determine action paths for work items using metadata scans and structured dialogue.

Community
Intermediate
myapihqmyapihq
83

my-storage-api

Upload files or ingest public URLs into a CDN-backed storage system.

Official
Intermediate
erikstmartinerikstmartin
16

systematic-debugging

Enforce a four-phase root-cause debugging workflow before implementing fixes.

Community
Advanced
Parth5409Parth5409

cloudinary-media-workflow

Automate Cloudinary media uploads via a centralized upload_file utility in FastAPI backends.

Community
Intermediate