automate-cleanup

Included with Lifetime

$97 forever

Remove all automations created by /automate (pre-uninstall)

General

What this skill does


# Cleanup Automations

Read `${CLAUDE_SKILL_DIR}/../../docs/shared-context.md` for registry format, merge algorithm, file markers, and deletion procedures.

## Step 1: Find All Automations

1. Read `~/.claude/automations-registry.json`
2. If empty/missing, scan for `created-by: automate` markers (same logic as Registry Bootstrap in shared-context.md)
3. If no automations found at all:
   > "No automations found. Nothing to clean up. You can safely uninstall the plugin."

   Stop here.

## Step 2: Display

Show all found automations:
```
Automations that will be removed:

| # | Name            | Type   | Scope   | Path                                    |
|---|-----------------|--------|---------|-----------------------------------------|
| 1 | semver-hook     | hook   | global  | ~/.claude/settings.json (hook entry)    |
| 2 | semver          | skill  | global  | ~/.claude/skills/semver/SKILL.md        |
| 3 | code-reviewer   | agent  | project | .claude/agents/code-reviewer.md         |
```

## Step 3: Choose Action

Use AskUserQuestion:
```
What would you like to do?
- Remove ALL automations listed above
- Select which automations to keep
- Cancel (keep everything)
```

## Step 4: Execute Removal

**If "Remove ALL":**
For each automation, in reverse order of creation, follow the deletion procedure for its type (see shared-context.md "Deletion Procedures by Type").

**If "Select which to keep":**
Show a numbered list, ask which to KEEP (all others will be removed).
Remove only the ones NOT selected.

**If "Cancel":** Stop.

**IMPORTANT**: Every JSON file modification during cleanup MUST be validated with `jq` after writing. Use the merge algorithm — never write partial JSON.

## Step 5: Final Cleanup

After removal, delete `~/.claude/automations-registry.json`.

## Step 6: Summary

```
Cleanup complete:
- Removed: 3 automations (semver-hook, semver, code-reviewer)
- Kept: 0
- Registry: deleted

You can now safely uninstall the plugin with:
/plugin uninstall automate
```

Files: 1

Size: 2.5 KB

Complexity: 9/100

Category: General

Source: https://github.com/elmisi/claude-code-automation/tree/main/plugin/skills/automate-cleanup

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts