Skip to content
Skills Library
Programming · Analysis

nomoreide-debug

/nomoreide-debug

Debug and troubleshoot local development services through the shared NoMoreIDE MCP daemon. Use this skill whenever the user asks to debug, diagnose, troubleshoot, run or start an app or service, inspect a crash, investigate logs, fix an unhealthy server, resolve a port conflict, restart a service, or determine why a frontend or backend is not loading—even when they do not mention NoMoreIDE.

Repository
nomoreide ↗
Licence
AGPL-3.0
Last repository change
11.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.10.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Debug and troubleshoot local development services through the shared NoMoreIDE MCP daemon. Use this skill whenever the user asks to debug, diagnose, troubleshoot, run or start an app or service, inspect a crash, investigate logs, fix an unhealthy server, resolve a port conflict, restart a service, or determine why a frontend or backend is not loading—even when they do not mention NoMoreIDE.

Original author description

Debug and troubleshoot local development services through the shared NoMoreIDE MCP daemon. Use this skill whenever the user asks to debug, diagnose, troubleshoot, run or start an app or service, inspect a crash, investigate logs, fix an unhealthy server, resolve a port conflict, restart a service, or determine why a frontend or backend is not loading—even when they do not mention NoMoreIDE.

How it works

  1. Workflow
Original SKILL.md headings · 34 lines, 235 words
SKILL.md preview
---
name: nomoreide-debug
description: Debug and troubleshoot local development services through the shared NoMoreIDE MCP daemon. Use this skill whenever the user asks to debug, diagnose, troubleshoot, run or start an app or service, inspect a crash, investigate logs, fix an unhealthy server, resolve a port conflict, restart a service, or determine why a frontend or backend is not loading—even when they do not mention NoMoreIDE.
compatibility: Requires the nomoreide MCP server and a registered NoMoreIDE service, bundle, or repository.
---

# Debug with NoMoreIDE

Use NoMoreIDE as the shared runtime control plane so the human, agent, dashboard,
CLI, and other sessions observe the same processes and logs.

## Workflow

1. Call `nomoreide_list_services` and `nomoreide_status`.
2. Match the current repository and the user's wording to a registered service
   or bundle. Ask for the intended target only when multiple matches remain.
3. Before changing runtime state, inspect `nomoreide_service_health`,
   `nomoreide_service_context`, `nomoreide_read_logs`, and
   `nomoreide_timeline` as relevant.
4. When the user wants the application running, start the registered target
   with `nomoreide_start_service` or `nomoreide_start_bundle`. Do not launch
   its command in a separate shell because that creates a duplicate process
   outside the shared runtime.
5. Diagnose the evidence, inspect the affected code, and make only the changes
   the user authorized.
6. Restart through NoMoreIDE when the fix requires it, then re-check health,
   logs, and timeline to verify the result.

If the project is not registered, explain that clearly and use the NoMoreIDE
onboarding or registration flow before managing it. If the MCP is unavailable,
report that setup is missing instead of silently falling back to an unmanaged
development process.

Starting, stopping, or restarting changes shared machine state. A request to
debug or diagnose authorizes inspection, not a runtime mutation. Start only
when the user explicitly asks to run or start the target. Before stopping or
restarting, explain why it is needed and get permission unless the user
explicitly requested that exact action.
Files in this package (3)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB
  • evals/evals.json 1 KB

Versions

The database has no other skills named nomoreide-debug.

Database snapshot: 13.11.2026 · package version 62379996647e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90nomoreide-ui-polish
    Apply NoMoreIDE's compact, flat visual language to React dashboard surfaces. Use when polishing, simplifying, restyling, or making Git, Docker, Activity, Services, or another NoMoreIDE page visually consistent; when the user asks for the "same style"; or when reviewing UI…
  • 90manage-local-services
    Manage workflow daemon services - MCP, SLOP, Slack, Ollama, Scheduler. Start, stop, restart, status. Use when user says "start MCP", "restart slack daemon", "service status".
  • 95docker-debug
    Debug Kurtosis running on local Docker. Inspect engine, API container, and service logs. Diagnose container crashes, port conflicts, and networking issues. Use when kurtosis commands fail or services aren't reachable on Docker.
  • 100dev-debug-logs
    Use when debugging an app through `fusebase dev start`, or when you need to inspect browser logs, proxied API traffic, frontend dev server output, or backend output captured by the local CLI. Explains where logs are written and which file to inspect for each symptom. This is for…
  • 100debug-fe-be-integration
    Diagnose and fix frontend↔backend contract failures by tracing requests, server logs, validation, auth, and responses on both sides. Use for API 4xx/5xx, mismatched payloads, or "frontend and backend disagree". One layer → debug-error.
  • 100ao-desktop-dev
    Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.