investigate-service-issues
Skill2 starsChanged 20 days agoApache-2.0View on GitHub
Debug systemd service failures - status, journal logs, boot issues, failed units. Optional auto-restart. Use when user says "service down", "check systemd", "investigate service", or "aa-workflow not running".
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- manage-local-servicesSkill
- The first 60 shown.
The file
Files
Investigate Service Issues
Debug systemd service failures and investigate issues. Checks status, journal logs, boot-level issues, failed units. Optional auto-restart.
Inputs
| Input | Type | Default | Purpose |
service_name | string | - | Service to check (e.g., aa-workflow-mcp). Empty = all failed |
since | string | 1h | Log time window (1h, 30m, 1d) |
auto_restart | bool | false | Restart failed services |
check_all_failed | bool | true | List all failed systemd units |
Persona
Load devops persona (systemd tools: systemctl, journalctl).
Workflow
1. Bootstrap
persona_load("devops")
2. System Info
hostnamectl_status()— hostname, OStimedatectl_status()— time sync (NTP)
3. Failed Units
systemctl_list_units(pattern="--failed")— all failed unitssystemctl_list_unit_files(pattern="aa-workflow-*")— workflow units
4. Service-Specific (if service_name)
systemctl_is_active(unit="{service}.service")systemctl_is_enabled(unit="{service}.service")systemctl_status(unit="{service}.service")journalctl_unit(unit="{service}.service", lines=50)
5. Broad Log Analysis
journalctl_logs(priority="err", since=since, lines=30)journalctl_boot(boot="0", priority="warning", lines=20)
6. Ollama Check
ollama_status()— inference server
7. Auto-Restart (if auto_restart and service_name)
systemctl_daemon_reload()systemctl_restart(unit="{service}.service")systemctl_status(unit="{service}.service")— verify
8. Analyze
Parse for: inactive service, not enabled, failed units count, OOM, permission denied, connection refused, time not synced, restart success.
9. Log
memory_session_log("Investigated service issues", ...)
10. Failure Patterns
- segfault/core dump → binary compatibility
- "too many open files" → ulimit, LimitNOFILE
learn_tool_fix(...)for recurring patterns
Output
Report: issues, recommendations, service status, recent logs, failed units, restart result, system info.
Quick Actions
systemctl_restart(unit="{service}.service")journalctl_unit(unit="{service}.service", lines=100)skill_run("manage_local_services", '{"action": "status"}')
Chains To
manage_local_services
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

