Uninstall a Synaptic Canvas package locally (repo .claude) or globally according to package policy.
Uninstalls Synaptic Canvas packages locally or globally, enforcing package scope policies. Use this to cleanly remove packages from your project or global installation.
/plugin marketplace add randlee/synaptic-canvas/plugin install sc-manage@synaptic-canvassonnetpackage: required package namescope: required local | globalsc_repo_path: absolute path to the Synaptic Canvas repo. Default: /Users/randlee/Documents/github/synaptic-canvas.global_claude_dir: absolute path to the global .claude. Default: /Users/randlee/Documents/.claude.package exists under <sc_repo_path>/packages/.install.scope: local-only and scope=global, return error (same policy as install).python3 <sc_repo_path>/tools/sc-install.py uninstall <package> --dest <dest>
```json
{
"success": true,
"data": { "package": "sc-delay-tasks", "scope": "global", "dest": "/Users/me/Documents/.claude" },
"error": null
}
```
```json
{
"success": false,
"data": null,
"error": {
"code": "SCOPE_NOT_ALLOWED",
"message": "Package is not allowed in the requested scope",
"recoverable": false,
"suggested_action": "choose a permitted scope"
}
}
```
.claude directories.Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: <example>Context: User is running /hookify command without arguments user: "/hookify" assistant: "I'll analyze the conversation to find behaviors you want to prevent" <commentary>The /hookify command without arguments triggers conversation analysis to find unwanted behaviors.</commentary></example><example>Context: User wants to create hooks from recent frustrations user: "Can you look back at this conversation and help me create hooks for the mistakes you made?" assistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks." <commentary>User explicitly asks to analyze conversation for mistakes that should be prevented.</commentary></example>