vscode-port-monitor-config

This skill should be used when configuring VS Code Port Monitor extension for development server monitoring. Use when the user asks to "set up port monitoring for Vite", "monitor my dev server ports", "configure port monitor for Next.js", "track which ports are running", "set up multi-port monitoring", "monitor frontend and backend ports", or "check port status in VS Code". Provides ready-to-use configuration templates for Vite (5173), Next.js (3000), and microservices architectures with troubleshooting guidance.

3,893 stars

Best use case

vscode-port-monitor-config is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

This skill should be used when configuring VS Code Port Monitor extension for development server monitoring. Use when the user asks to "set up port monitoring for Vite", "monitor my dev server ports", "configure port monitor for Next.js", "track which ports are running", "set up multi-port monitoring", "monitor frontend and backend ports", or "check port status in VS Code". Provides ready-to-use configuration templates for Vite (5173), Next.js (3000), and microservices architectures with troubleshooting guidance.

Teams using vscode-port-monitor-config should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/vscode-port-monitor-config/SKILL.md --create-dirs "https://raw.githubusercontent.com/libukai/awesome-agent-skills/main/plugins/vscode-extensions-toolkit/skills/vscode-port-monitor-config/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/vscode-port-monitor-config/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How vscode-port-monitor-config Compares

Feature / Agentvscode-port-monitor-configStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

This skill should be used when configuring VS Code Port Monitor extension for development server monitoring. Use when the user asks to "set up port monitoring for Vite", "monitor my dev server ports", "configure port monitor for Next.js", "track which ports are running", "set up multi-port monitoring", "monitor frontend and backend ports", or "check port status in VS Code". Provides ready-to-use configuration templates for Vite (5173), Next.js (3000), and microservices architectures with troubleshooting guidance.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# VS Code Port Monitor Configuration

Configure the VS Code Port Monitor extension to monitor development server ports in real-time with visual status indicators in your status bar.

**Extension**: [dkurokawa.vscode-port-monitor](https://github.com/dkurokawa/vscode-port-monitor)

## Core Concepts

### Port Monitor Features

- 🔍 **Real-time monitoring** - Live status bar display
- 🏷️ **Intelligent configuration** - Supports arrays, ranges, well-known ports
- 🛑 **Process management** - Kill processes using ports
- 🎨 **Customizable display** - Icons, colors, positioning
- 📊 **Multiple groups** - Organize ports by service/project

### Status Icons

- 🟢 = Port is in use (service running)
- ⚪️ = Port is free (service stopped)

---

## Configuration Workflow

### Step 1: Create Configuration File

Add configuration to `.vscode/settings.json`:

```json
{
  "portMonitor.hosts": {
    "GroupName": {
      "port": "label",
      "__CONFIG": { ... }
    }
  }
}
```

### Step 2: Choose a Template

Select from common scenarios (see examples/ directory):

| Scenario | Template File | Ports |
|----------|--------------|-------|
| Vite basic | `vite-basic.json` | 5173 (dev) |
| Vite with preview | `vite-with-preview.json` | 5173 (dev), 4173 (preview) |
| Full stack | `fullstack.json` | 5173, 4173, 3200 |
| Next.js | `nextjs.json` | 3000 (app), 3001 (api) |
| Microservices | `microservices.json` | Multiple groups |

### Step 3: Apply Configuration

1. Copy template content to `.vscode/settings.json`
2. Customize port numbers and labels for your project
3. Save file - Port Monitor will auto-reload

---

## Quick Start Examples

### Example 1: Vite Project

```json
{
  "portMonitor.hosts": {
    "Development": {
      "5173": "dev",
      "__CONFIG": {
        "compact": true,
        "bgcolor": "blue",
        "show_title": true
      }
    }
  },
  "portMonitor.statusIcons": {
    "inUse": "🟢 ",
    "free": "⚪️ "
  }
}
```

**Display**: `Development: [🟢 dev:5173]`

### Example 2: Microservices

```json
{
  "portMonitor.hosts": {
    "Frontend": {
      "3000": "react",
      "__CONFIG": { "compact": true, "bgcolor": "blue", "show_title": true }
    },
    "Backend": {
      "3001": "api",
      "5432": "postgres",
      "__CONFIG": { "compact": true, "bgcolor": "yellow", "show_title": true }
    }
  }
}
```

**Display**: `Frontend: [🟢 react:3000] Backend: [🟢 api:3001 | 🟢 postgres:5432]`

---

## Best Practices

### ✅ Do

- Use descriptive labels: `"5173": "dev"` not `"5173": "5173"`
- Add space after emojis: `"🟢 "` for better readability
- Group related ports: Frontend, Backend, Database
- Use compact mode for cleaner status bar
- Set reasonable refresh interval (3000-5000ms)

### ❌ Don't

- Reverse port-label format: `"dev": 5173` ❌
- Use empty group names
- Set refresh interval too low (<1000ms)
- Monitor too many ports (>10 per group)

---

## Common Issues

### Port Monitor Not Showing

1. Check extension is installed: `code --list-extensions | grep port-monitor`
2. Verify `.vscode/settings.json` syntax
3. Reload VS Code: `Cmd+Shift+P` → "Reload Window"

### Configuration Errors

Check port-label format is correct:
```json
// ✅ Correct
{"5173": "dev"}

// ❌ Wrong
{"dev": 5173}
```

For more troubleshooting, see `references/troubleshooting.md`

---

## Reference Materials

- **Configuration Options**: `references/configuration-options.md` - Detailed option reference
- **Troubleshooting**: `references/troubleshooting.md` - Common issues and solutions
- **Integrations**: `references/integrations.md` - Tool-specific configurations
- **Advanced Config**: `references/advanced-config.md` - Pattern matching, custom emojis
- **Examples**: `examples/` - Ready-to-use JSON configurations

---

## Workflow Summary

1. **Choose template** from examples/ directory based on your stack
2. **Copy to** `.vscode/settings.json`
3. **Customize** port numbers and labels
4. **Save** and verify status bar display
5. **Troubleshoot** if needed using references/troubleshooting.md

Port Monitor will automatically detect running services and update the status bar in real-time.

Related Skills

vscode-sftp-config

3893
from libukai/awesome-agent-skills

This skill should be used when setting up SFTP deployment for static websites to production servers, including converting projects from Docker/Express to static hosting, deploying Vue/React/Angular builds, setting up Slidev presentations, or configuring Hugo/Jekyll/Gatsby sites. Use this when the user asks to "setup SFTP deployment", "deploy static site to server", "configure Nginx for static files", "convert from Docker to static hosting", "deploy Vue build to production", "setup subdomain hosting", or "configure SFTP in VS Code". Provides SFTP configuration templates and production-ready Nginx configurations with security headers and caching.

vscode-httpyac-config

3893
from libukai/awesome-agent-skills

Configure VSCode with httpYac for API testing and automation. This skill should be used specifically when converting API documentation to executable .http files (10+ endpoints), setting up authentication flows with pre-request scripts, implementing request chaining with response data, organizing multi-file collections with environment management, or establishing Git-based API testing workflows with CI/CD integration.

mcp-config

3893
from libukai/awesome-agent-skills

Configure MCP (Model Context Protocol) servers for Claude Code. Manage MCP servers at user or project scope with best practices to avoid context pollution.

obsidian-to-x

3893
from libukai/awesome-agent-skills

发布内容和文章到 X (Twitter)。支持常规推文(文字/图片/视频)和 X Articles(长文 Markdown)。使用真实 Chrome 浏览器绕过反机器人检测。当用户说"发推"、"发到 X"、"发到 twitter"、"分享到 X"、"分享到 twitter"、"发 tweet"、"同步到 X"、"发布到 X"、提到"X Articles"、想从 Obsidian 笔记发布长文内容、或需要转换 Obsidian Markdown 到 X 格式时使用。适用于所有 X/Twitter 发布任务。

skill-creator-pro

3893
from libukai/awesome-agent-skills

Create new skills, modify and improve existing skills, and measure skill performance. Enhanced version with quick commands. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. Triggers on phrases like "make a skill", "create a new skill", "build a skill for", "improve this skill", "optimize my skill", "test my skill", "turn this into a skill", "skill description optimization", or "help me create a skill".

plugin-integration-checker

3893
from libukai/awesome-agent-skills

Check if a skill is part of a plugin and verify its integration with commands and agents. Use after creating or modifying a skill to ensure proper plugin architecture. Triggers on "check plugin integration", "verify skill integration", "is this skill in a plugin", "check command-skill-agent integration", or after skill creation/modification when the skill path contains ".claude-plugins" or "plugins/".

interactive-portfolio

31392
from sickn33/antigravity-awesome-skills

Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios, and portfolios that convert visitors into opportunities.

azure-monitor-query-java

31392
from sickn33/antigravity-awesome-skills

Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.

azure-monitor-opentelemetry-ts

31392
from sickn33/antigravity-awesome-skills

Auto-instrument Node.js applications with distributed tracing, metrics, and logs.

azure-monitor-opentelemetry-exporter-java

31392
from sickn33/antigravity-awesome-skills

Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.

azure-appconfiguration-ts

31392
from sickn33/antigravity-awesome-skills

Centralized configuration management with feature flags and dynamic refresh.

azure-appconfiguration-java

31392
from sickn33/antigravity-awesome-skills

Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots.