agentleFS
Sign inStart free
patricio0312revpatricio0312rev/workspaces/skills/workspace-clone/SKILL.md

workspace-clone

Skill9 starsChanged 10 months agoMITView on GitHub

Clone one or all repositories configured in a workspace to their designated paths. Use when user says "clone repos", "clone all", or wants to download workspace repositories.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user wants to clone repositories:

    line 19
  2. Distinctive:

    Read the workspace configuration and get the list of projects with their:

    line 27
  3. Distinctive:

    Create parent directory: if needed

    line 36
  4. Distinctive:

    After successful cloning, suggest:

    line 63

≈ “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.

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

Skill: Workspace Clone

Description

Clone one or all repositories configured in a workspace to their designated paths.

Arguments

  • [project] - Name of a specific project to clone
  • all - Clone all projects (default if no argument)

Instructions

When the user wants to clone repositories:

Step 1: Detect Workspace

Identify the current workspace. If none detected, ask the user to specify one or run /workspaces:init.

Step 2: Parse Configuration

Read the workspace configuration and get the list of projects with their:

  • Repository URL
  • Target path

Step 3: Clone Repositories

For each repository:

  1. Check if already cloned - Skip if directory exists with .git
  2. Create parent directory if needed
  3. Clone the repository
  4. Report status

Output Format

📥 Cloning workspace repositories...

Cloning api...
  git clone git@github.com:acme/api.git ~/work/acme/api
  ✓ api cloned successfully

Cloning admin...
  git clone git@github.com:acme/admin.git ~/work/acme/admin
  ✓ admin cloned successfully

✓ homepage already exists at ~/work/acme/homepage

Summary:
  • Cloned: api, admin
  • Skipped: homepage (already exists)
  • Failed: 0

Post-Clone Actions

After successful cloning, suggest:

Run '/workspaces:setup all' to install dependencies and configure projects.

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.

Check your setup, free