workspace-services
Skill9 starsChanged 10 months agoMITView on GitHub
Start and stop development services for workspace projects. Use when user says "start services", "stop services", "start all", or "stop all".
In this repository8 other files it gives its agents.
- using-workspacesSkill
- workspace-affectedSkill
- workspace-cloneSkill
- workspace-doctorSkill
- workspace-initSkill
- workspace-searchSkill
- workspace-setupSkill
- workspace-statusSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Start and stop services for workspace projects.
- Distinctive: line 21
When the user wants to start services:
- Very specific: line 25
Look for start-all in the ## Commands section of WORKSPACE.md:
- Distinctive: line 32
If a shared command exists, offer to use it.
- Distinctive: line 36
If no shared command or user prefers individual starts:
- Distinctive: line 40
Verify the port becomes active
- Very specific: line 64
Look for stop-all in ## Commands.
- Distinctive: line 68
If no shared command, stop services by terminating processes on configured ports.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Workspace Services
Description
Start and stop services for workspace projects. Manages development servers and related services.
Arguments
start [project|all]- Start servicesstop [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 -dIf a shared command exists, offer to use it.
Step 2: Start Individual Projects
If no shared command or user prefers individual starts:
- Find the project's start command (check package.json for
devorstartscripts) - Start the service
- 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 ✓ runningStopping 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)...
✓ StoppedDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.