systemd
Manage Linux services with systemd. Use when a user asks to create a system service, run an app on boot, manage background processes, set up timers (cron replacement), or configure service dependencies and auto-restart.
What this skill does
# systemd ## Overview systemd manages Linux services — start, stop, restart, enable on boot, and monitor processes. It replaces init scripts with declarative unit files. Handles dependencies, auto-restart, logging (journald), resource limits, and timers (cron replacement). ## Instructions ### Step 1: Create a Service ```ini # /etc/systemd/system/myapp.service — Node.js app as a system service [Unit] Description=My Node.js Application After=network.target postgresql.service Wants=postgresql.service [Service] Type=simple User=deploy Group=deploy WorkingDirectory=/opt/myapp ExecStart=/usr/bin/node dist/server.js Restart=always RestartSec=5 Environment=NODE_ENV=production Environment=PORT=3000 EnvironmentFile=/opt/myapp/.env # Security hardening NoNewPrivileges=true ProtectSystem=strict ProtectHome=true ReadWritePaths=/opt/myapp/uploads # Resource limits MemoryMax=512M CPUQuota=80% [Install] WantedBy=multi-user.target ``` ### Step 2: Manage Service ```bash sudo systemctl daemon-reload # reload after editing unit files sudo systemctl enable myapp # start on boot sudo systemctl start myapp # start now sudo systemctl status myapp # check status sudo systemctl restart myapp # restart sudo systemctl stop myapp # stop journalctl -u myapp -f # view live logs journalctl -u myapp --since "1 hour ago" # recent logs ``` ### Step 3: Timer (Cron Replacement) ```ini # /etc/systemd/system/backup.timer — Run backup daily at 3 AM [Unit] Description=Daily Backup Timer [Timer] OnCalendar=*-*-* 03:00:00 Persistent=true [Install] WantedBy=timers.target ``` ```ini # /etc/systemd/system/backup.service — The actual backup job [Unit] Description=Database Backup [Service] Type=oneshot User=deploy ExecStart=/opt/scripts/backup.sh ``` ```bash sudo systemctl enable --now backup.timer systemctl list-timers # list active timers ``` ## Guidelines - Always run `daemon-reload` after changing unit files. - Use `Restart=always` for production services — systemd auto-restarts on crash. - `journalctl -u service -f` is the primary log viewer — replaces checking log files. - Timers are better than cron: persistent (catch up missed runs), dependency-aware, logged.
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.