setup-scripts
Generate or regenerate all helper scripts used by org automation skills
What this skill does
# Setup Helper Scripts Generate all shell scripts in `~/.claude/scripts/` used by the org automation skills. Run this after a fresh install, or to regenerate scripts if they go missing. ## Script inventory All scripts live in `~/.claude/scripts/` and must be executable. They share a common library `_lib.sh` with functions for parsing CLAUDE.md files. | Script | Used by | Purpose | |---|---|---| | `_lib.sh` | All scripts | Shared: `get_gh_org`, `parse_repo_names`, `parse_repo_names_with_type` | | `org-ci-health.sh` | `/org-ci-health` | CI run status + action versions per repo | | `org-deps.sh` | `/org-deps` | DESCRIPTION/Project.toml deps + release tags | | `org-releases.sh` | `/org-releases` | Release tags, commit counts, NEWS status | | `org-maintenance.sh` | `/org-maintenance` | Non-main worktrees + open PRs with status | | `daily-summary.sh` | `/daily-summary` | Bot PRs, issues, commits, blockers for a date | | `weekly-plan.sh` | `/weekly-plan` | Daily logs, open PRs, assigned issues, commit counts | | `org-standards.sh` | `/org-standards` | Config files, CI workflows, badges per repo | | `org-issues-scan.sh` | `/org-issues-tidy`, `/org-issues-do` | Open issues with metadata and bot comment status | | `bot-tasks.sh` | `/bot-tasks` | Unprocessed bot notifications with comment context | | `cron-bot-tasks.sh` | cron | Poll for new bot requests, trigger if needed | ## Procedure 1. Create `~/.claude/scripts/` if it does not exist 2. For each script in the inventory above, check if it exists and is executable 3. If missing, read the current version from this skill's embedded templates below and write it 4. If it exists, check its version comment against the template — offer to update if outdated 5. Run `chmod +x` on all scripts 6. Smoke test each script (run with `--help` or a quick org name) and report pass/fail ## Templates The templates for each script are maintained in the script files themselves. This skill should read the existing scripts at `~/.claude/scripts/*.sh` to verify they exist. If any are missing, regenerate them by: 1. Reading `~/.claude/scripts/_lib.sh` for the shared library pattern 2. Following the same pattern (source `_lib.sh`, use `get_gh_org`, `parse_repo_names`) 3. Outputting JSON to stdout 4. Using `set -euo pipefail` and bash 3.2 compatibility (no `mapfile`, no associative arrays) ### Bash 3.2 compatibility rules macOS ships bash 3.2. All scripts MUST: - Not use `mapfile` — use `while IFS= read -r` loops instead - Not use associative arrays (`declare -A`) — use parallel indexed arrays - Not use `|&` — use `2>&1 |` - Not use `[[ =~ ]]` with literal `)` in patterns — use `sed` for extraction - Use `$(( ))` for arithmetic, not `let` - Process substitution `< <()` works on macOS bash 3.2 but test if unsure ## Validation After generating, run each script and verify: - Exit code 0 - Output is valid JSON (pipe through `jq .`) - No bash syntax errors Report results as a table: | Script | Exists | Executable | Valid JSON | Status | |---|---|---|---|---| ## Auto-Exit When Standalone **IMPORTANT**: If this command is being run as a standalone request, automatically exit after completing all phases successfully.
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.