Results for “systemd”

Bringing up a complete ROS2 system on a robot's onboard computer: systemd services, launch file composition, ordered startup, and production monitoring. Use this skill when configuring a robot to start ROS2 nodes on boot, writing systemd unit files for ROS2 launch, composing layered launch files for full robot stacks, setting up watchdog monitoring, configuring udev rules for deterministic device naming, or debugging boot-time race conditions. Trigger whenever the user mentions robot bringup, robot startup, systemd for ROS2, ROS2 on boot, launch file composition, robot boot sequence, udev rules for cameras or serial ports, automatic restart for ROS2 nodes, network configuration for multi-machine ROS2, log rotation for robots, graceful shutdown of robot stacks, or SSH-based remote debugging. Also trigger for sourcing workspaces in systemd, ordered startup with health checks, or running ROS2 systems as long-running production services. Covers systemd on Ubuntu 22.04/24.04 with ROS2 Humble, Iron, and Jazzy.

The English summary is being prepared. Showing the original description.

Inspect Linux scheduled tasks, services, shell profiles, shared library settings, and SSH keys for mechanisms that maintain attacker access. Correlate findings with audit logs to produce a timeline, risk scores, and remediation commands.

• Investigating how attackers maintained access to a Linux host
• Hunting for suspicious scheduled tasks and services
• Building a timeline from persistence-related audit events

Examine Linux authentication logs, shell history, SSH keys, scheduled tasks, and system settings to investigate a compromise. Help reconstruct activity, identify ways attackers maintain access, and document suspicious accounts, files, and configuration changes.

• Investigating a potentially compromised Linux server
• Finding mechanisms that maintain unauthorized access
• Tracing user activity through logs and command history

Helps configure an iii engine for Compose management or direct supervision by tools such as systemd. Covers configuration file structure, ports, storage, and role-based access control through rbac-proxy, including requirements for public connections.

• Configuring an engine managed by Compose
• Configuring an engine supervised by systemd or Kubernetes
• Setting authentication and access rules for public connections

Manage continuously running or cloud-hosted agents with lifecycle controls, logs, metrics, restricted permissions, and emergency stops. It guides incident response, staged deployments, rollbacks, and tracking success rates and cost per successful task.

• Define operating controls for continuously running agents
• Plan incident response when failures increase
• Set deployment and rollback procedures

Hunts for Linux persistence by inspecting cron, systemd units, shell rc files, SSH authorized_keys, and common autostart locations for attacker-added entries. Activates for requests to hunt Linux persistence, audit cron/systemd for backdoors, or find unauthorized autostart and authorized_keys entries.

The English summary is being prepared. Showing the original description.

Update a live OpenClaw checkout on macOS, then verify its Gateway and local app. Investigate automated check failures, repair them through focused pull requests, and run release validation without publishing a release.

• Updating a live OpenClaw installation on macOS
• Verifying Gateway and app behavior after updates
• Repairing automated checks for the current main commit

Diagnose Fedora Linux problems with a structured troubleshooting plan. Get commands for checking services, logs, and packages, followed by remediation, validation, and rollback steps that account for SELinux and firewalld where relevant.

• Investigating a service that will not start
• Troubleshooting package-related problems
• Checking SELinux or firewall involvement

Investigate Debian Linux issues through service checks, logs, and package tools. Receive repair commands, verification steps, and rollback guidance, with attention to AppArmor security restrictions or firewall settings when relevant.

• Investigating Debian service or package problems
• Checking whether security restrictions affect an issue
• Preparing repair, verification, and rollback steps

Diagnose Arch Linux problems by reviewing recent updates, service logs, and packages. Get a step-by-step investigation plan, ready-to-copy repair commands, verification steps, and guidance for rollback or cleanup.

• Investigating problems after an Arch Linux update
• Diagnosing services that fail to start
• Planning repairs with verification and rollback steps

Set up KubeEye in KubeSphere to inspect Kubernetes clusters. Define checks for configurations, nodes, and services, schedule recurring or one-time inspections, and retrieve findings as HTML or spreadsheet reports.

• Install KubeEye for cluster inspections
• Create checks for node health and configuration
• Schedule recurring cluster inspections

Plan persistence testing for authorized Windows and Linux security exercises, examining how access can survive logons or restarts. The skill compares mechanisms by privilege level and environment, with validation steps, detection indicators, and cleanup considerations.

• Planning persistence tests for authorized exercises
• Comparing methods by operating system and privilege
• Reviewing detection indicators for persistence

Running a DOCA-linked binary directly on the hardware, with no container or kubelet: on host x86 with a BlueField NIC over PCIe, or bare-metal on BlueField Arm. Use for launching and supervising it (direct, tmux, systemd), and when it "exits 1 right after launch", "systemd keeps restarting it", reports "no matching device on the BF", or the BlueField itself is unhealthy: "bfb-install exited 0 but DPU is dead", "ping 192.168.100.2 works but ssh fails", "host PFs aren't showing netdevs". Service containers under kubelet belong to doca-container-deployment. Covers PCI/NUMA/CPU/IRQ binding, co-tenant isolation (cgroup-v2/netns/numactl), a seven-layer error taxonomy, platform lifecycle (BFB install, RShim/TMFIFO, host PF rebind, post-BFB recovery) and a six-state BlueField lifecycle classifier. Destructive firmware burn / mlxconfig set requires explicit confirmation via doca-hardware-safety; library APIs, env prep, and build use other skills.

The English summary is being prepared. Showing the original description.

Create and manage systemd services and timers. Configure service dependencies and resource limits. Use when managing system services.

The English summary is being prepared. Showing the original description.

Build daemon/background processes that start on boot, run continuously, and manage their own lifecycle. Covers macOS launchd (plist files, agents vs daemons), Linux systemd (unit files), Windows services, process supervision, logging, health checks, graceful shutdown, auto-restart, and AI-powered daemons that manage LLM API connections and rate limits. Activate on: "daemon", "background process", "launchd", "systemd", "service file", "plist", "launch agent", "launch daemon", "auto-start", "always running", "process supervisor", "pm2", "background service", "boot service", "AI daemon", "long-running process". NOT for: container orchestration (use devops-automator), cron jobs that run and exit (use task-scheduler), web server deployment (use backend-architect).

The English summary is being prepared. Showing the original description.

Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LD_PRELOAD hijacking, bashrc modifications, and authorized_keys backdoors using auditd and file integrity monitoring

The English summary is being prepared. Showing the original description.

Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LD_PRELOAD hijacking, bashrc modifications, and authorized_keys backdoors using auditd and file integrity monitoring

The English summary is being prepared. Showing the original description.

Administração de Ubuntu, Debian e AlmaLinux — systemd, cron, SSH, Fail2Ban, supervisor, disco, memória, rede e processos. Use quando o usuário disser "servidor", "linux", "systemd", "serviço não sobe", "disco cheio", "load alto", "SSH", "cron não roda", "processo travado".

The English summary is being prepared. Showing the original description.

Build daemon/background processes that start on boot, run continuously, and manage their own lifecycle. Covers macOS launchd (plist files, agents vs daemons), Linux systemd (unit files), Windows services, process supervision, logging, health checks, graceful shutdown, auto-restart, and AI-powered daemons that manage LLM API connections and rate limits. Activate on: "daemon", "background process", "launchd", "systemd", "service file", "plist", "launch agent", "launch daemon", "auto-start", "always running", "process supervisor", "pm2", "background service", "boot service", "AI daemon", "long-running process". NOT for: container orchestration (use devops-automator), cron jobs that run and exit (use task-scheduler), web server deployment (use backend-architect).

The English summary is being prepared. Showing the original description.

Detect and analyze Linux persistence mechanisms including crontab entries, systemd service units, LD_PRELOAD hijacking, bashrc modifications, and authorized_keys backdoors using auditd and file integrity monitoring

The English summary is being prepared. Showing the original description.

Design a persistent multi-agent workflow in Claude Code, with specialist roles, reusable commands, file-based memory, and scheduled tasks. Keep project context and decisions across sessions using JSON and Markdown files without an external database.

• Coordinate specialist agents for development and writing
• Preserve project context across sessions
• Schedule recurring morning briefings

Connect NanoClaw to a real phone number for SMS and AI voice calls through Dial. The skill installs the channel adapter, guides account sign-in and phone pairing, and configures who can contact the agent.

• Contact a NanoClaw agent by SMS
• Set up an AI phone receptionist
• Restrict the line to a paired owner phone

Helps manage and troubleshoot Linux, macOS, and Windows systems. Guides checks of CPU, memory, disks, networks, and logs, then supports service configuration and security hardening with explanations suited to the operating system.

• Investigating slow systems and resource usage
• Finding causes of low disk space
• Checking failed services and their logs

Investigate how a limited Linux account could gain root, the system administrator's privileges. The skill guides checks of permissions, scheduled tasks, services, and known vulnerabilities, while outlining evidence defenders can monitor during authorized security assessments.

• Assessing Linux privilege escalation paths
• Practicing privilege escalation in CTF challenges
• Reviewing sudo and scheduled task configurations