delete-all
Delete tidbits (defaults, custom, or all)
What this skill does
Delete tidbits from the user's collection with options for what to delete.
## Storage
Resolve paths before reading or writing:
- `PLUGIN_ROOT`: `${CLAUDE_PLUGIN_ROOT}` in Claude Code. If unavailable, use the directory two levels above this `SKILL.md`.
- `TIDBITS_FILE`: `${TERMINAL_TIDBITS_FILE}` if set; otherwise `~/.terminal-tidbits/terminal-tidbits.json`.
- `DEFAULT_TIDBITS_FILE`: `${PLUGIN_ROOT}/data/default-terminal-tidbits.json`.
## Instructions
### Step 1: Read Current State
Read both files to understand what exists:
1. Read the defaults file:
```
DEFAULT_TIDBITS_FILE
```
2. Read the working file (if it exists):
```
TIDBITS_FILE
```
Determine:
- How many default tidbits exist (from default-terminal-tidbits.json)
- How many total tidbits the user currently has
- Which tidbits are "user-added" (in working file but not in defaults, matched by `tid`)
### Step 2: Show Current State
Before asking, display a summary so the user understands what they have:
```
You currently have {TOTAL} tidbits:
- {D} from the default set
- {C} that you added
```
If the user has modified or deleted some defaults, note that too.
### Step 3: Ask What to Delete
Use the **AskUserQuestion** tool to present deletion options. Use clear action verbs that explicitly state what will be REMOVED:
```json
{
"questions": [{
"question": "Which tidbits do you want to remove?",
"header": "Remove",
"options": [
{
"label": "My additions only",
"description": "Removes the {C} tidbits you added; keeps the {D} defaults"
},
{
"label": "Defaults only",
"description": "Removes the {D} default tidbits; keeps your {C} additions"
},
{
"label": "Everything",
"description": "Removes all {TOTAL} tidbits; collection will be empty"
},
{
"label": "Reset to original",
"description": "Discards all changes; restores the {ORIG} original default tidbits"
}
],
"multiSelect": false
}]
}
```
Replace placeholders with actual counts:
- `{TOTAL}` = total tidbits user currently has
- `{D}` = count of default tidbits still present
- `{C}` = count of user-added tidbits
- `{ORIG}` = count of tidbits in default-terminal-tidbits.json (always the same)
### Step 4: Execute Based on Choice
Before writing `TIDBITS_FILE`, create its parent directory if it does not exist.
**If "My additions only":**
- Filter the working file to keep only tidbits whose `tid` matches a default tidbit
- Write the filtered list to the working file
- Or simply delete the working file if all custom tidbits were removed
**If "Defaults only":**
- Filter the working file to keep only tidbits whose `tid` does NOT match any default tidbit
- Write the filtered list to the working file
**If "Everything":**
- Write an empty tidbits structure to the working file:
```json
{"tidbits": []}
```
**If "Reset to original":**
- Delete the working file entirely (so commands will read from defaults)
- Use Bash to remove: `rm "$TIDBITS_FILE"`
- Or write the defaults content to the working file
### Step 5: Confirm
Report what was done:
```
Deleted {X} tidbits.
You now have {Y} tidbits. Use `/terminal-tidbits:show` to see them.
```
Or if everything was deleted:
```
All tidbits deleted. Your collection is now empty.
Use `/terminal-tidbits:add` to start fresh, or run `/terminal-tidbits:delete-all` and choose "Reset to original" to restore the defaults.
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.