Managing Installed Products
List, update, and uninstall MyClaude products in your Claude Code environment.
List, update, and uninstall MyClaude products in your Claude Code environment.
Once you have installed products via the CLI or the web, the myclaude CLI provides commands to inspect, update, and remove them. This page covers the full lifecycle after installation.
List installed products
$ myclaude listInstalled products (3)
@kairo/review-skill 1.2.0 skills .claude/skills/review-skill/
@dev/pr-checker 0.9.1 skills .claude/skills/pr-checker/
@anya/deploy-workflow 2.0.0 workflows .claude/workflows/deploy-workflow/Each row shows the product handle, installed version, category, and file path.
Filter by category:
$ myclaude list --category skillsCheck for available updates
Preview which products have newer versions without applying anything:
$ myclaude update --all --dry-runUpdates available (1 of 3)
@kairo/review-skill 1.2.0 → 1.3.0The --dry-run flag is safe to run at any time. It reads the registry but makes no changes.
Update products
Update a single product to the latest version:
$ myclaude update @kairo/review-skillUpdating @kairo/review-skill 1.2.0 → 1.3.0...
Downloaded. Replaced files in .claude/skills/review-skill/
Done.Update all installed products at once:
$ myclaude update --allThe CLI replaces the product files in place. Your local configuration files (if any) are preserved — only the product's core files are overwritten.
Pinning a version
If you need to stay on a specific version and skip future updates:
$ myclaude update @kairo/review-skill --pinPinned products are excluded from myclaude update --all. Remove the pin with:
$ myclaude update @kairo/review-skill --unpinUninstall products
$ myclaude uninstall @dev/pr-checkerRemoved @dev/pr-checker from .claude/skills/pr-checker/
Done.This deletes the product files from your .claude/ directory and removes the product from the local registry. Your purchase record remains — you can reinstall the product at any time without repurchasing.
To uninstall multiple products in one command:
$ myclaude uninstall @dev/pr-checker @anya/deploy-workflowFile locations by category
Products are stored in predictable directories:
| Category | Directory |
|---|---|
| Skills | .claude/skills/{product-name}/ |
| Squads | .claude/squads/{product-name}/ |
| Agents | .claude/agents/{product-name}/ |
| Workflows | .claude/workflows/{product-name}/ |
| Design Systems | .claude/design-systems/{product-name}/ |
| Prompts | .claude/prompts/{product-name}/ |
| CLAUDE.md | Project root or .claude/ |
| Applications | Standalone directory per product instructions |
If you installed via the web and placed files manually, myclaude repair can detect and register them:
$ myclaude repairScanned .claude/ directory
Found 1 unregistered product: @kairo/review-skill in .claude/skills/review-skill/
Registered.View purchase history
Your complete purchase history is available at myclaude.sh/dashboard under Purchases. The dashboard shows:
| Column | Description |
|---|---|
| Product | Name and creator handle |
| Date | Purchase date |
| Amount | Price paid |
| Status | Completed, Refunded |
| Action | Re-download, View product page |
You can re-download any purchased product from the dashboard at any time. There is no download limit.
Checking product health
Run a diagnostic on all installed products to verify file integrity and compatibility:
$ myclaude doctorChecking 3 installed products...
@kairo/review-skill 1.3.0 OK
@dev/pr-checker 0.9.1 OK
@anya/deploy-workflow 2.0.0 WARNING: requires myclaude-cli >= 0.2.0
All files intact. 1 warning.The doctor command checks that all expected files are present, manifest data is valid, and version requirements are satisfied. Run it after upgrading the CLI or Claude Code to catch compatibility issues early.
Backing up installed products
The .claude/ directory is a normal directory in your project. To back up your installed products, include .claude/ in your version control or backup system.
If you use git and want to track installed products:
$ git add .claude/skills/ .claude/workflows/
$ git commit -m "track installed MyClaude products"This ensures teammates working on the same repository get the same products without installing separately. If you prefer not to track product files in git, add .claude/skills/ and similar directories to .gitignore — each developer can install independently using myclaude install.
Troubleshooting
myclaude list shows no products but files exist in .claude/.
Run myclaude repair to scan the directory and re-register products that were installed manually or whose registry entries were lost.
myclaude update fails with a network error.
Check your internet connection and ensure you are logged in (myclaude login). If the error persists, try updating a single product to isolate the issue.
Uninstalled product still appears in Claude Code.
Restart your Claude Code session. Claude Code reads the .claude/ directory at startup — removing files mid-session may not take effect until the next launch.
Update overwrites my customizations.
Product updates replace the product's core files only. If you modified files inside the product directory, those changes will be lost on update. Keep customizations in a separate file outside the product directory and reference them from your project's CLAUDE.md.
Related pages
- Installing via CLI — first-time installation tutorial
- Installing via Web — download and install from the browser
- Purchasing Products — purchase history and re-downloads
- Troubleshooting — full FAQ for common issues