setup
# /claude-alertr:setup
What this skill does
# /claude-alertr:setup
Walk the user through configuring claude-alertr. This skill replaces the interactive prompts from `install.sh`.
## Steps
### 1. Gather configuration
Ask the user for these three values (use AskUserQuestion or conversational prompts):
- **Worker URL** — The URL of their deployed claude-alertr Cloudflare Worker (e.g. `https://claude-alertr.you.workers.dev`). Required.
- **Auth Token** — The AUTH_TOKEN secret set on the Worker via `wrangler secret put AUTH_TOKEN`. Required.
- **Alert Delay** — Seconds to wait before sending an alert. Default: `60`. Optional.
### 2. Write the config file
Create `~/.claude-alertr/config` with these contents (replace values with user input):
```
# claude-alertr configuration
# URL of your deployed claude-alertr Cloudflare Worker
CLAUDE_ALERTR_URL="<worker_url>"
# Auth token (must match AUTH_TOKEN secret on the Worker)
CLAUDE_ALERTR_TOKEN="<auth_token>"
# Seconds to wait before sending an alert (default: 60)
CLAUDE_ALERTR_DELAY="<delay>"
```
Create the directory first (`mkdir -p ~/.claude-alertr`) and set permissions (`chmod 600 ~/.claude-alertr/config`).
### 3. Test the connection
Run a test request against the Worker:
```bash
curl -s -o /dev/null -w "%{http_code}" -X POST \
-H "Authorization: Bearer <auth_token>" \
<worker_url>/test
```
Interpret the result:
- **200** — Connected successfully. Tell the user to check their notification channels.
- **401** — Auth token doesn't match. Ask them to verify it matches what's set on the Worker.
- **503** — AUTH_TOKEN not configured on the Worker. Tell them to run `wrangler secret put AUTH_TOKEN`.
- **500** — Connected but no notification channels configured. Tell them to set `WEBHOOK_URL` or `RESEND_API_KEY` via `wrangler secret put`.
- **Connection error** — Worker URL may be wrong or Worker isn't deployed.
### 4. Confirm setup
Tell the user:
- claude-alertr is configured and will alert them if Claude has been waiting for their input for more than **{delay}** seconds
- Config is stored at `~/.claude-alertr/config`
- The plugin hooks are automatically registered — no manual `settings.json` editing needed
- To change settings later, edit `~/.claude-alertr/config` or run `/claude-alertr:setup` again
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.