Add version & query params#2
Open
sharon-yelenik wants to merge 5 commits into
Open
Conversation
carlevison
reviewed
Jul 14, 2026
carlevison
left a comment
carlevison
left a comment
There was a problem hiding this comment.
Check that the query params are necessary for Console links and whether you should be linking to the .md files.
| ### Install the Cloudinary VS Code extension (VS Code and VS Code-based IDEs) | ||
|
|
||
| If you're using VS Code or a VS Code-based IDE (like Cursor), the [Cloudinary VS Code extension](https://cloudinary.com/documentation/cloudinary_vscode_extension) lets you manage, preview, and deliver media directly from your editor—no context switching needed. | ||
| If you're using VS Code or a VS Code-based IDE (like Cursor), the [Cloudinary VS Code extension](https://cloudinary.com/documentation/cloudinary_vscode_extension?install_source=skillspack&referrer=get-started-skill) lets you manage, preview, and deliver media directly from your editor—no context switching needed. |
There was a problem hiding this comment.
Should this be a link to the .md file? https://cloudinary.com/documentation/cloudinary_vscode_extension.md?install_source=skillspack&referrer=get-started-skill
| - **Anything else** — any cloud name containing a recognizable word, personal name, or brand-like string, including hyphenated or multi-word names (e.g., `yelenik`, `new-shop`, `mycompany`, `acme`): SKIP this step. Skipping means output NOTHING for it: no "Customize your cloud name" heading, no one-line summary, no improvised alternative, and no line for it in the numbered overview — continue directly to the next section. Writing ANY cloud-name content for a non-machine-generated cloud name is an error. All-lowercase alone does not mean random. **When in doubt, skip.** | ||
|
|
||
| **Scope guard:** this step renames the cloud name inside the delivery URL path (`res.cloudinary.com/<cloud_name>/...`). It is NOT the custom domain / CNAME feature (`media.yourcompany.com`) — never mention custom domains or subdomains here, and never invent Console paths such as "Account → Custom Domain". Do not write cloud-name steps from your own knowledge: the cloud name is NOT edited under "Settings → Account", there is no pencil/edit icon flow, and any navigation other than the marker block's steps is wrong. The only correct location is **Settings → Product Environments** (`https://console.cloudinary.com/app/settings/product-environments`), exactly as written in the marker block below. | ||
| **Scope guard:** this step renames the cloud name inside the delivery URL path (`res.cloudinary.com/<cloud_name>/...`). It is NOT the custom domain / CNAME feature (`media.yourcompany.com`) — never mention custom domains or subdomains here, and never invent Console paths such as "Account → Custom Domain". Do not write cloud-name steps from your own knowledge: the cloud name is NOT edited under "Settings → Account", there is no pencil/edit icon flow, and any navigation other than the marker block's steps is wrong. The only correct location is **Settings → Product Environments** (`https://console.cloudinary.com/app/settings/product-environments?install_source=skillspack&referrer=get-started-skill`), exactly as written in the marker block below. |
There was a problem hiding this comment.
Are you sure that Console links should have the extra query params?
| Your cloud name appears in every delivery URL. A short, brand-related cloud name is better for SEO/AEO than the auto-generated default: | ||
|
|
||
| 1. Go to: `https://console.cloudinary.com/app/settings/product-environments` | ||
| 1. Go to: `https://console.cloudinary.com/app/settings/product-environments?install_source=skillspack&referrer=get-started-skill` |
| - Stage 3 may write placeholder `CLOUDINARY_*` values to `.env.example`. Client-side placeholders are allowed only when required by the detected framework, such as `VITE_*` for React/Vite. | ||
| - Never place API secrets in source files, generated docs, MCP JSON, chat replies, scripts that echo output, logs, or validation artifacts. | ||
| - **Secret exposure response:** If an API key or secret becomes visible from any source, immediately name the exposed credential without repeating its value, tell the user to rotate it at [Settings → API Keys](https://console.cloudinary.com/settings/api-keys) and update `.env`, and never quote it again. | ||
| - **Secret exposure response:** If an API key or secret becomes visible from any source, immediately name the exposed credential without repeating its value, tell the user to rotate it at [Settings → API Keys](https://console.cloudinary.com/settings/api-keys?install_source=skillspack&referrer=get-started-skill) and update `.env`, and never quote it again. |
|
|
||
| After approval, set up the missing Cloudinary MCP servers and skills using the current IDE or agent environment's standard conventions. Follow official Cloudinary MCP guidance when needed: | ||
| https://cloudinary.com/documentation/cloudinary_llm_mcp#local_mcp_servers | ||
| https://cloudinary.com/documentation/cloudinary_llm_mcp?install_source=skillspack&referrer=get-started-skill#local_mcp_servers |
There was a problem hiding this comment.
Should this be the .md file? Do query params not go after the anchor? I don't remember.
| ### D2 — Get credentials and fill `.env` | ||
|
|
||
| Grab your **cloud name**, **API key**, and **API secret** from the Cloudinary Console: [Cloudinary Console — API Keys](https://console.cloudinary.com/settings/api-keys) | ||
| Grab your **cloud name**, **API key**, and **API secret** from the Cloudinary Console: [Cloudinary Console — API Keys](https://console.cloudinary.com/settings/api-keys?install_source=skillspack&referrer=get-started-skill) |
There was a problem hiding this comment.
Same question about the console link.
| Grab your **cloud name**, **API key**, and **API secret** from the Cloudinary Console: [Cloudinary Console — API Keys](https://console.cloudinary.com/settings/api-keys?install_source=skillspack&referrer=get-started-skill) | ||
|
|
||
| **IMPORTANT:** Use the exact link above — `https://console.cloudinary.com/settings/api-keys`. Do not tell the user to go to the "Dashboard tab" or any other location. | ||
| **IMPORTANT:** Use the exact link above — `https://console.cloudinary.com/settings/api-keys?install_source=skillspack&referrer=get-started-skill`. Do not tell the user to go to the "Dashboard tab" or any other location. |
There was a problem hiding this comment.
Same question about the console link.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added version to the metadata and query params to any doc links from the skill