add
Add a new terminal tidbit to your personal reference
What this skill does
Add a new tidbit to the user's terminal reference collection.
## Arguments
$ARGUMENTS
The user provides:
- **tid**: A short identifier for the command/concept (e.g., `2>&1`, `grep -r`, `chmod 755`)
- **bit**: A detailed explanation in markdown format
Arguments may be provided as:
- Two separate arguments: `/terminal-tidbits:add "2>&1" "explanation here..."`
- A JSON object: `/terminal-tidbits:add {"tid": "2>&1", "bit": "explanation..."}`
- Natural language: "add a tidbit for the `xargs` command..."
## 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`.
Tidbits are stored in `TIDBITS_FILE` with this structure:
```json
{
"tidbits": [
{"tid": "command", "bit": "explanation..."}
]
}
```
## Instructions
### Step 1: Parse the Input
Extract the `tid` and `bit` from $ARGUMENTS. If the user provided natural language, help them formulate both parts:
- Ask clarifying questions if the tid or bit is unclear
- Offer to write the bit if the user just names a command they want to learn about
### Step 2: Read Existing Tidbits
First, try to read the working tidbits file:
```
TIDBITS_FILE
```
If that file doesn't exist, read the defaults and use them as the starting point:
```
DEFAULT_TIDBITS_FILE
```
If neither file exists, start with an empty structure:
```json
{"tidbits": []}
```
### Step 3: Check for Duplicates
Check if a tidbit with the same `tid` already exists (case-sensitive match).
If duplicate found:
- Show the existing bit
- Ask if they want to replace it or keep both (with a modified tid)
### Step 4: Add the Tidbit
Append the new tidbit to the array and write the updated JSON to the working file:
```
TIDBITS_FILE
```
Create the parent directory first if it does not exist.
### Step 5: Confirm
Output a confirmation:
```
Added tidbit: `{tid}`
{bit preview - first 100 chars}...
You now have {N} tidbits. Use `/terminal-tidbits:show` to see all.
```
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.