Automated summary
Automates the setup of multiple projects in a workspace by running predefined scripts.
Strengths
- Saves time on repetitive setup tasks
- Ensures consistent environment configuration
- Provides clear progress and summary
- Handles multiple projects at once
Limitations
- Depends on the presence and correctness of WORKSPACE.md
- Does not handle complex errors or rollbacks
- Assumes all dependencies are available
When onboarding to a new workspace or after pulling fresh code.
When projects require manual steps or custom configurations not captured in setup scripts.
Security analysis
SafeThe skill executes predefined setup commands from a local configuration file (WORKSPACE.md). It does not involve downloading remote scripts, destructive operations, exfiltration, or obfuscation. The risk is minimal.
No concerns found
How this analysis is madeExamples
Set up all projects in the workspaceSetup api projectInstall dependencies for workspacename: workspace-setup description: Run setup scripts for workspace projects including dependency installation, migrations, and environment configuration. Use when user says "setup projects", "install dependencies", or "run setup".
Skill: Workspace Setup
Description
Run setup scripts for one or all projects in the workspace, including dependency installation, environment configuration, and database migrations.
Arguments
[project]- Name of a specific project to set upall- Set up all projects (default)
Instructions
When the user wants to set up projects:
Step 1: Detect Workspace
Identify the current workspace and load the configuration.
Step 2: Parse Setup Scripts
Read the ## Setup Scripts section from WORKSPACE.md:
## Setup Scripts
api: npm install && cp .env.example .env && npm run db:migrate
admin: npm install && cp .env.example .env
homepage: npm install
mobile: npm install && cd ios && pod install
Step 3: Run Setup for Each Project
For each project (or the specified one):
- Check if project is cloned - Skip if not
- Run setup script in the project directory
- Report progress
Output Format
🔧 Setting up workspace projects...
Setting up api...
→ npm install
Installing dependencies... done
→ cp .env.example .env
✓ Environment file created
→ npm run db:migrate
Running migrations... done
✓ api setup complete
Setting up admin...
→ npm install
Installing dependencies... done
✓ admin setup complete
Summary:
• Set up: api, admin
• Skipped: homepage (no setup script)
• Failed: 0
Post-Setup
After successful setup, suggest:
Run '/workspaces:start all' to start the services.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/workspace-setup-mm5t8bts/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/workspace-setup-mm5t8bts' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/workspace-setup-mm5t8bts/download' --output '.skill-downloads/workspace-setup-mm5t8bts/SKILL.md.part' && mv '.skill-downloads/workspace-setup-mm5t8bts/SKILL.md.part' '.skill-downloads/workspace-setup-mm5t8bts/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/workspace-setup-mm5t8bts/SKILL.md' && test -s '.skill-downloads/workspace-setup-mm5t8bts/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/workspace-setup' && cp -R '.skill-downloads/workspace-setup-mm5t8bts' '.claude/skills/workspace-setup'Cursor
test -f '.skill-downloads/workspace-setup-mm5t8bts/SKILL.md' && test -s '.skill-downloads/workspace-setup-mm5t8bts/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/workspace-setup' && cp -R '.skill-downloads/workspace-setup-mm5t8bts' '.cursor/skills/workspace-setup'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/workspace-setup-mm5t8bts'openskills read 'workspace-setup-mm5t8bts'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/workspace-setup-mm5t8bts/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.