Diagnose a Linux service issue from logs in read-only mode

When To Use

• When logs are available
• When remote access is not authorized
• When the user needs a safe diagnostic checklist

When Not To Use

• When the agent must SSH or restart services
• When logs contain secrets that cannot be redacted
• When production action is requested

Inputs Required

• Logs or status output
• Service name
• Recent changes

Expected Outputs

• Likely cause
• Safe checks
• Escalation boundary

Skill Bundle

MCP Discovery Workflow

Use this as read-only discovery and planning. The live endpoint does not execute the workflow or install packages.

1. search_solutions - Find scenario solutions by workflow problem.
2. get_solution_detail - Inspect the scenario solution, risk boundary, skill bundle, and CTA.
3. search_skills - Search the current public GetSkillary skill catalog.
4. get_skill_detail - Inspect the primary or supporting skill detail.
5. get_download_url - Get a manual download URL for the selected skill.
6. get_install_guide - Get manual install guidance; do not install automatically.

search_solutions("Diagnose a Linux service issue from logs in read-only mode")
search_skills("Diagnoses Common Linux Service Issues Using Logs, Systemd/pm2, File Permissions, Nginx Reverse")
search_skills("Create Precise Incident Timelines From Logs and Notes")
search_skills("Markdown Authoring Helper")

Safety Boundary

Execution mode

local_agent_guided_no_hosted_execution

Human review required

Yes

Modifies local files

No

Requires API key

No

Requires external account

No

Local scenario-solution architecture only. This does not publish Batch 3, deploy production pages, add hosted execution, or claim AI citation, recommendation, ranking, click, lead, or conversion improvement.

Success Criteria

• Diagnosis stays evidence-based
• Commands are operator-run
• No remote action is implied

Failure Modes

• Inventing root cause
• Requesting credentials
• Treating suggested commands as already run

Example Prompt

How can an AI agent diagnose a Linux service issue from logs without touching the server?

Example Input

systemd or PM2 log excerpts and service context.

Example Output Summary

A read-only diagnosis with likely causes and commands the operator can run manually.

Next Action

Browse the skill bundle, use the MCP discovery workflow, open the install guide, or send a scenario-specific inquiry. Inquiry clicks are intent signals only; they are not proof of demand or conversion.