Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/libukai/awesome-agent-skills/tree/main/plugins/vscode-extensions-toolkit/skills/vscode-port-monitor-config
SKILL.md
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
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:
{
"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
- Copy template content to
.vscode/settings.json - Customize port numbers and labels for your project
- Save file - Port Monitor will auto-reload
Quick Start Examples
Example 1: Vite Project
{
"portMonitor.hosts": {
"Development": {
"5173": "dev",
"__CONFIG": {
"compact": true,
"bgcolor": "blue",
"show_title": true
}
}
},
"portMonitor.statusIcons": {
"inUse": "đ˘ ",
"free": "âŞď¸ "
}
}
Display: Development: [đ˘ dev:5173]
Example 2: Microservices
{
"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
- Check extension is installed:
code --list-extensions | grep port-monitor - Verify
.vscode/settings.jsonsyntax - Reload VS Code:
Cmd+Shift+Pâ "Reload Window"
Configuration Errors
Check port-label format is correct:
// â
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
- Choose template from examples/ directory based on your stack
- Copy to
.vscode/settings.json - Customize port numbers and labels
- Save and verify status bar display
- Troubleshoot if needed using references/troubleshooting.md
Port Monitor will automatically detect running services and update the status bar in real-time.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
obsidian-to-x
ĺĺ¸ĺ 厚ĺćçŤ ĺ° X (Twitter)ăćŻć常č§ć¨ć(ćĺ/ĺžç/č§é˘)ĺ X Articles(éżć Markdown)ă使ç¨çĺŽ Chrome ćľč§ĺ¨çťčżĺćşĺ¨äşşćŁćľăĺ˝ç¨ćˇčŻ´"ĺć¨"ă"ĺĺ° X"ă"ĺĺ° twitter"ă"ĺäşŤĺ° X"ă"ĺäşŤĺ° twitter"ă"ĺ tweet"ă"ĺćĽĺ° X"ă"ĺĺ¸ĺ° X"ăćĺ°"X Articles"ăćłäť Obsidian çŹčްĺĺ¸éżćĺ 厚ăćéčŚč˝Źć˘ Obsidian Markdown ĺ° X ć źĺźćśä˝żç¨ăéç¨äşćć X/Twitter ĺĺ¸äťťĺĄă
mcp-config
Configure MCP (Model Context Protocol) servers for Claude Code. Manage MCP servers at user or project scope with best practices to avoid context pollution.
skill-creator-pro
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".
skill-creator-pro
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".
skill-creator-pro
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".
vscode-httpyac-config
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.
Didn't find tool you were looking for?