portcheck

Identify port usage and owning process on Linux and macOS.

32|9|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/DotNetAge/mindx --skill portcheck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portcheck
Source: https://github.com/DotNetAge/mindx/tree/main/skills/portcheck
Command: npx skills add https://github.com/DotNetAge/mindx --skill portcheck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, lsof, ss, and includes scripts (resource) components.

What problem does it solve?

This skill helps diagnose port usage by querying a specific port to determine whether it is in use and which process is using it.

Core Features & Use Cases

  • Port status check for a given port and associated process information.
  • Cross-platform (macOS and Linux) port analysis to facilitate debugging network services.
  • Use Case: Imagine you are debugging a server that fails to bind to port 8080; portcheck will help you quickly identify the conflicting process.

Quick Start

Check port 8080 to see if it is free or occupied and identify the occupying process.

Frequently Asked Questions about portcheck

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a network port is in use and identify the owning process?

To check port usage and identify the owning process, query the specific port to retrieve its in-use status and associated process metadata. This directly resolves service binding conflicts on Linux and macOS environments.

How can I find out which process is using port 8080 on macOS and Linux?

Finding which process is using port 8080 involves running a network port analysis to return structured JSON output with process metadata. This cross-platform diagnostic facilitates debugging server binding issues.

Does portcheck work on both macOS and Linux for diagnosing service conflicts?

Yes, portcheck works on both macOS and Linux for diagnosing service conflicts. It analyzes port usage across these environments to help you quickly identify conflicting processes when a server fails to bind.

What is the best way to diagnose port binding issues using command line tools?

The best way to diagnose port binding issues is to query the specific port for its in-use status and owning process. It leverages standard tools like lsof and ss to provide structured JSON output for debugging.

Do I need to install lsof and ss to analyze port status?

Yes, you need lsof and ss installed to analyze port status, as they are required dependencies for querying port usage. jq is also required to parse and produce the structured JSON output with process metadata.