Inspect system logs
Skill neptune-software/claude-code-plugin/skills/inspect-system-logs
Read Neptune DXP system log files via the MCP tools `list_system_logs` and `get_system_log`. Use when the user wants to debug a server error, inspect script output, trace requests, or investigate exceptions/vault activity from the platform's daily log files. Trigger phrases include "check the logs", "show server errors", "what did the script log", "any exceptions today", "tail the request log", "look at the system log", "debug this error in the logs".From its SKILL.md
npx -y skills add neptune-software/claude-code-plugin --skill inspect-system-logsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.8 KB, as published. Nobody here has run it
Inspecting Neptune DXP system logs via MCP
Planet 9 writes its operational logs to daily files — one file per day per category. These two read-only tools let you find those files and read entries from them. This is the go-to for debugging runtime errors, seeing what a server script logged, or tracing requests.
The five log categories
type | What it holds |
|---|---|
server | General server/runtime log. |
exceptions | Uncaught exceptions and stack traces. |
scripts | Server-script output (log.<silly, verbose, info, debug, warn, error, crit>, e.g log.debug("User not framed")), console.log does not go to this log |
requests | Incoming HTTP request log. |
vault | Secret/vault access activity. |
Tools
| Tool | Purpose |
|---|---|
list_system_logs({ type?, dateFrom?, dateTo? }) | List available log files. Omit type to get files grouped across all categories; pass one to narrow. |
get_system_log({ type, name, ... }) | Read entries from a specific file (paginated, filterable). |
list_system_logs returns files grouped as serverFiles/exceptionFiles/scriptFiles/requestFiles/vaultFiles (or pass type to narrow); names look like 2026-05-11-planet9.log. get_system_log needs type + that name, and filters by: level (silly→crit), message (case-insensitive substring), scriptName/scriptGroup (scripts category only), start/end (default 0–100, end exclusive), dateFrom/dateTo.
Gotchas
namemust come fromlist_system_logs— don't guess; the naming convention varies by deployment. So the flow is always list → get.- Always pass a
leveland/ormessagefilter when hunting a problem. Files are huge; an unfiltered 0–100 window from a busyrequestslog tells you little. Filter tolevel: ["error","crit"]or a distinctivemessagesubstring. - Read-only. No deletion or rotation control over MCP. Both tools require the
syslogrole (List/Get).
Related skills
run-server-script/manage-server-scripts— when thescriptslog points at a failing script, inspect and re-run it.manage-apis— request/proxy failures in therequestslog often trace back to an API artifact.search-docs— look up an unfamiliar error message in the public DXP docs.