agentleFS
patricio0312revpatricio0312rev/workspaces/skills/workspace-setup/SKILL.md

workspace-setup

Skill9 starsChanged 10 months agoMITView on GitHub

Run setup scripts for workspace projects including dependency installation, migrations, and environment configuration. Use when user says "setup projects", "install dependencies", or "run setup".

  • Reads credentials
  • Installs packages

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run setup scripts for one or all projects in the workspace, including dependency installation, environment configuration, and database …

    line 10
  2. Distinctive:

    When the user wants to set up projects:

    line 19
  3. Very specific:

    Read the ## Setup Scripts section from WORKSPACE.md:

    line 27
  4. Distinctive:

    After successful setup, suggest:

    line 72

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 up
  • all - 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):

  1. Check if project is cloned - Skip if not
  2. Run setup script in the project directory
  3. 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.

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.