workshop-create

Scaffolds workshop directories locally or as private GitHub repositories.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill workshop-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workshop-create
Source: https://github.com/github/awesome-copilot/tree/main/skills/workshop-create
Command: npx skills add https://github.com/github/awesome-copilot --skill workshop-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up a consistent workshop root directory — with desks, a shared bench, and operating guidelines — is repetitive and error-prone, especially when deciding between using an existing folder or creating a new GitHub-backed repo without nesting repositories.

Core Features & Use Cases

  • Two setup paths: Adopt an existing local directory as a workshop, or create and clone a new private GitHub repo using the signed-in account via gh repo create.
  • Structure scaffolding: Creates desks/, bench/, CAIRN.md, and README.md, adding .gitkeep placeholders so empty folders survive cloning, while preserving any existing content.
  • Repo nesting protection: Validates the parent directory with git rev-parse --is-inside-work-tree before initializing, preventing a repo from being created inside another repo.
  • Use Case: A user says "create a workshop called team-alpha" and the Skill clones a new private repo into a safe parent directory, scaffolds the structure, commits, and pushes it.

Quick Start

Ask the agent to create a new workshop named team-alpha as a private GitHub repo, or to turn an existing local folder into a workshop.

Frequently Asked Questions about workshop-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new workshop backed by a GitHub repo?

Provide a short kebab-case name and a parent directory that is not inside an existing git repo. The Skill runs gh repo create with the --private and --clone flags under your signed-in GitHub account, then scaffolds and pushes the structure.

Can I use an existing local directory as a workshop?

Yes. Point the Skill at the existing path and it detects any existing workshop markers, then adds only the missing pieces like desks/, bench/, CAIRN.md, and README.md. It never runs git init or overwrites existing content.

Why does the workshop setup check git rev-parse before creating a repo?

The check confirms whether the chosen parent directory is already inside a git work tree. Creating a repo inside another repo causes nesting problems, so the Skill picks a different parent or falls back to local-only scaffolding.

Why are .gitkeep files added to the workshop folders?

Git does not track empty directories, so desks/ and bench/ would disappear on the next clone. The .gitkeep placeholder files ensure the scaffolded structure survives committing, pushing, and re-cloning.

What are the limitations of the workshop creation workflow?

It requires the GitHub CLI (gh) with an authenticated account for the repo path, and it only creates private repos in the signed-in account. It does not initialize git in existing directories or manage repos inside other repos.