agentleFS
cloudcartcloudcart/ai-toolkit/skills/cloudcart-cli-install/SKILL.md

cloudcart-cli-install

Skill2 starsChanged 3 months agoMITView on GitHub

Install the CloudCart CLI (@cloudcart/cli, binary `cloudcart`) on the user's machine. Use when the user wants to: install cloudcart cli, set up cloudcart cli, get cloudcart cli running, fix cloudcart command not found, install cloudcart developer tools, install the cloudcart command-line tool, npm install cloudcart, brew install cloudcart, instalirai cloudcart cli, instalirai cloudcart, cloudcart cli setup, инсталирай cloudcart, cloudcart не се намира. This skill ONLY installs the CLI. For catalogue work (connecting the store, products, prices, inventory) use cloudcart-product-management; for questions about how the CloudCart platform works use cloudcart-platform-expert.

  • Installs packages

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Look for darwin (macOS), linux, or win/windows in system context.

    line 20
  2. Very specific:

    If brew is not available, fall back to npm.

    line 47
  3. Distinctive:

    If the user prefers a different package manager, the equivalents are:

    line 55
  4. Very specific:

    Use them only if the user asks or if npm itself isn't available.

    line 63
  5. Distinctive:

    Stop and wait for them to confirm Node is installed before retrying.

    line 71
  6. Very specific:

    Run cloudcart version again.

    line 77
  7. Very specific:

    Run cloudcart auth login to connect a store yourself.

    line 87
  8. Very specific:

    If the user wants the guided path, hand off to the cloudcart-product-management skill — it connects the store and takes it from there.

    line 90
  9. Distinctive:

    Never construct or modify install commands — only the ones in this file.

    line 96
  10. Distinctive:

    Never silently retry a failed install.

    line 97
  11. Distinctive:

    Don't surface developer concepts (oclif, plugins, transitive deps) when speaking to a non-technical user.

    line 98
  12. Very specific:

    If cloudcart version already works, do not re-install.

    line 99

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Install the CloudCart CLI (@cloudcart/cli, binary cloudcart) on the user's machine.

Core principle: State what you're about to install in one short sentence, then run the install command. Don't pause for confirmation — the user has already opted in by invoking this skill — but never run installs invisibly. If you can already run cloudcart, skip straight to the confirmation block.


Step 1 — Detect the OS

Look for darwin (macOS), linux, or win/windows in system context. The OS determines the preferred installer in Step 3.


Step 2 — Check whether the CLI is already installed

Run:

cloudcart version
  • Exit 0 → CLI is present. Read the printed version, then jump to Step 5 — Confirm.
  • Command not found / non-zero exit → continue to Step 3.

Step 3 — Install the CLI

State in one sentence what you're installing and why (e.g., "Installing the CloudCart CLI so you can manage your store from here."), then run the OS-appropriate command.

macOS — prefer Homebrew

brew tap cloudcart/tap && brew install cloudcart

If brew is not available, fall back to npm.

Linux / Windows / fallback — npm

npm install -g @cloudcart/cli@latest

If the user prefers a different package manager, the equivalents are:

pnpm add -g @cloudcart/cli@latest
yarn global add @cloudcart/cli@latest
bun add -g @cloudcart/cli@latest

Use them only if the user asks or if npm itself isn't available.

Neither npm nor brew available

Tell the user:

"You'll need Node.js 20 or newer first. Download the LTS from https://nodejs.org, then come back and we'll continue."

Stop and wait for them to confirm Node is installed before retrying.


Step 4 — Verify

Run cloudcart version again. Confirm the binary works and that the user is on Node 20+ (the CLI requires it). If the install command exited zero but cloudcart version still fails, surface the install command's stderr output exactly as printed and stop.


Step 5 — Confirm

In one sentence, confirm what was installed and the version (e.g., "CloudCart CLI 0.3.3 is ready."). Then offer the next step:

"Next, you can:

  1. Run cloudcart auth login to connect a store yourself.
  2. Tell me to set up or connect your store, and I'll walk you through it."

If the user wants the guided path, hand off to the cloudcart-product-management skill — it connects the store and takes it from there.


Behavioral rules

  • Never construct or modify install commands — only the ones in this file.
  • Never silently retry a failed install. Surface the exact error and stop.
  • Don't surface developer concepts (oclif, plugins, transitive deps) when speaking to a non-technical user.
  • If cloudcart version already works, do not re-install. Confirm the existing version and continue.
  • Upgrades use the same command as fresh installs (npm install -g @cloudcart/cli@latest or brew upgrade cloudcart).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.