菜单
Query systemd journal logs, check service status, diagnose failed units, and analyze boot performance. USE WHEN investigating system issues, service failures, checking logs, or when the user asks about systemd services or journal entries.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | systemd |
| description | Query systemd journal logs, check service status, diagnose failed units, and analyze boot performance. USE WHEN investigating system issues, service failures, checking logs, or when the user asks about systemd services or journal entries. |
| argument-hint | diagnose [unit] |
| model | sonnet |
You diagnose systemd issues by gathering service status, querying journal logs, and analyzing boot and timer state.
Gather Context: Verify the user is in the systemd-journal group by running groups. If not, inform the user that journal access may be limited.
Determine Intent: Analyze the user's request or the ARGUMENTS passed to the skill:
Select Workflow: Route to the appropriate workflow based on intent (see Workflow Routing table below). If no argument is given and intent is unclear, ask the user what they would like to investigate.
Execute Workflow: Report to the user which diagnostic path is running. You MUST read the selected workflow document completely before proceeding: ./workflows/<WorkflowName>.md
Report Results: Summarize findings, highlight failures or anomalies, and suggest next steps.
| Workflow | Trigger Words | When to Use |
|---|---|---|
| Diagnose | "diagnose", "status", "failed", "logs", "journal", "errors", "boot", "timers", "check" | User wants to investigate system health, service failures, journal logs, boot performance, or timer schedules. Accepts an optional unit name to scope the diagnostic. |
Test NixOS configuration changes using the feedback ladder — from instant syntax checks to full system builds. USE WHEN the user wants to verify, test, or check NixOS changes before deploying.
Review and fix documentation surprises discovered by the surprise hook. USE WHEN the user wants to fix documentation issues, review surprises, or address items in .claude/surprises/.
Browser automation for development testing, web scraping, and UI verification. USE WHEN you need to interact with web pages, verify UI changes, take screenshots, or extract data from websites.
Systematically explore and test a web application to find bugs, UX issues, and other problems. USE WHEN the user wants to quality-test a web app, find issues, dogfood a product, or produce a structured bug report with reproduction evidence.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) via Chrome DevTools Protocol. USE WHEN the user needs to interact with an Electron desktop app, automate a native app, connect to a running Electron app, or test an Electron application.
Interact with Slack workspaces using browser automation. USE WHEN the user needs to check unread channels, send messages, search conversations, navigate Slack, or extract data from Slack workspaces without using the Slack API.
