smithery/patricio0312rev

workspace-services

Start and stop development services for workspace projects. Use when user says "start services", "stop services", "start all", or "stop all".

Installation

$ npx skills add smithery/patricio0312rev --skill workspace-services

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/patricio0312rev · top by installs.

npx skills add smithery/patricio0312rev

Browse all from smithery/patricio0312rev

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,686 B
  • docs SUMMARY.md 167 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Skill: Workspace Services

Description

Start and stop services for workspace projects. Manages development servers and related services.

Arguments

  • start [project|all] - Start services
  • stop [project|all] - Stop services

Instructions

Starting Services

When the user wants to start services:

Step 1: Check for Shared Command

Look for start-all in the ## Commands section of WORKSPACE.md:

## Commands
start-all: cd ~/work/acme && docker-compose up -d

If a shared command exists, offer to use it.

Step 2: Start Individual Projects

If no shared command or user prefers individual starts:

  1. Find the project's start command (check package.json for dev or start scripts)
  2. Start the service
  3. Verify the port becomes active

Output Format for Start

🚀 Starting workspace services...

Starting api...
  cd ~/work/acme/api && npm run dev
  ✓ api started on port 3000

Starting admin...
  cd ~/work/acme/admin && npm run dev
  ✓ admin started on port 3001

Port status:
  • api: :3000 ✓ running
  • admin: :3001 ✓ running

Stopping Services

Step 1: Check for Shared Command

Look for stop-all in ## Commands.

Step 2: Stop Individual Projects

If no shared command, stop services by terminating processes on configured ports.

Output Format for Stop

🛑 Stopping workspace services...

Stopping api (port 3000)...
  ✓ Stopped

Stopping admin (port 3001)...
  ✓ Stopped