Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
Creates new Agent Skills for GitHub Copilot: scaffolds the skill folder under .github/skills, writes SKILL.md with proper frontmatter and adds optional scripts, references and assets.
Install Skill Scaffolding for GitHub Copilot
$ npx skills add ruby-git/ruby-git --skill make-skill-template -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ruby-git/ruby-git make-skill-template --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/make-skill-template .claude/skills/make-skill-template && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "make-skill-template" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/make-skill-template into .claude/skills/make-skill-template/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-skill-template", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ruby-git/ruby-git/tree/main/.github/skills/make-skill-templateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ruby-git/ruby-git --skill make-skill-template -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ruby-git/ruby-git make-skill-template --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/make-skill-template .agents/skills/make-skill-template && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "make-skill-template" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/make-skill-template into .agents/skills/make-skill-template/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-skill-template", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruby-git/ruby-git --skill make-skill-template -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ruby-git/ruby-git make-skill-template --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/make-skill-template .cursor/skills/make-skill-template && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "make-skill-template" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/make-skill-template into .cursor/skills/make-skill-template/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-skill-template", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ruby-git/ruby-git.git --path .github/skills/make-skill-template--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ruby-git/ruby-git --skill make-skill-template -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ruby-git/ruby-git make-skill-template --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/make-skill-template .gemini/skills/make-skill-template && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "make-skill-template" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/make-skill-template into .gemini/skills/make-skill-template/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-skill-template", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ruby-git/ruby-git make-skill-templateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ruby-git/ruby-git --skill make-skill-template -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/make-skill-template .github/skills/make-skill-template && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "make-skill-template" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/make-skill-template into .github/skills/make-skill-template/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-skill-template", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruby-git/ruby-git --skill make-skill-template -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ruby-git/ruby-git make-skill-template --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruby-git/ruby-git.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/make-skill-template .opencode/skills/make-skill-template && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "make-skill-template" agent skill from https://github.com/ruby-git/ruby-git/tree/main/.github/skills/make-skill-template into .opencode/skills/make-skill-template/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "make-skill-template", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
make-skill-template- GitHub stars
- 1.8k
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,007 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Creates new Agent Skills for GitHub Copilot: scaffolds the skill folder under .github/skills, writes SKILL.md with proper frontmatter and adds optional scripts, references and assets.
- Works in 4 steps: Create the Skill Directory → Generate SKILL.md with Frontmatter → Write the Skill Body → …
- Creating a new skill for a GitHub Copilot setup
- SKILL.md covers Contents, How to use this skill, Related skills and When to Use This Skill, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
A meta-skill for authoring other skills. The agent creates the skill directory, generates a SKILL.md with valid frontmatter, writes the body and adds optional scripts, references and assets folders only when they are needed. Its outline includes frontmatter field requirements, description best practices, how to organize the body and a full example of a skill structure.
You attach the file to Copilot Chat when creating or refining a skill under .github/skills/, and it also helps check discoverability before committing. A validation checklist and a troubleshooting section close it out, and it points to sibling skills for reviewing skills, the repository development workflow and PR readiness review. A quick-start route duplicates the template itself as a starting point.
When your agent uses it
- Creating a new skill for a GitHub Copilot setup
- Scaffolding a skill folder with scripts, references or assets
- Improving a skill's description so it is easier to trigger
- Learning what the Agent Skills specification expects
Example prompts
- “Create a skill for generating release notes and put it under .github/skills.”
- “Scaffold a new skill called dependency-audit with a scripts folder.”
- “Check this skill's description and frontmatter for discoverability problems.”
Requirements
- GitHub Copilot Chat with the skill file attached
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit f3bf20f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
agentskills.ioplatform.claude.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skill Scaffolding for GitHub Copilot loads about 2.5k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 1,007 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ruby-git/ruby-git at commit f3bf20f, republished under its MIT licence (© ruby-git). 1,007 words, ~2,462 tokens.
Download SKILL.mdSave it as
.claude/skills/make-skill-template/SKILL.md (or your agent's skills folder).- name
- make-skill-template
- description
- Create new Agent Skills for GitHub Copilot from user requests or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders.
Make Skill Template
A meta-skill for creating new Agent Skills. Use this skill when you need to scaffold a new skill folder, generate a SKILL.md file, or help users understand the Agent Skills specification.
Contents
- Contents
- How to use this skill
- Related skills
- When to Use This Skill
- Prerequisites
- Creating a New Skill
- Skill Body Organization
- Example: Complete Skill Structure
- Quick Start: Duplicate This Template
- Validation Checklist
- Troubleshooting
- References
How to use this skill
Attach this file to your Copilot Chat context, then invoke it when creating or
refining a skill under .github/skills/. Use it to scaffold new skills and to
check discoverability quality before committing.
Related skills
- Reviewing Skills — audit a skill for quality, discoverability, and best-practice compliance after authoring
- Development Workflow — integrate skill creation changes into the repository workflow
- PR Readiness Review — final validation before opening a pull request with new or updated skills
When to Use This Skill
- User asks to "create a skill", "make a new skill", or "scaffold a skill"
- User wants to add a specialized capability to their GitHub Copilot setup
- User needs help structuring a skill with bundled resources
- User wants to duplicate this template as a starting point
Prerequisites
- Understanding of what the skill should accomplish
- A clear, keyword-rich description of capabilities and triggers
- Knowledge of any bundled resources needed (scripts, references, assets, templates)
Creating a New Skill
Step 1: Create the Skill Directory
Create a new folder with a lowercase, hyphenated name:
.github/skills/<skill-name>/
└── SKILL.md # RequiredStep 2: Generate SKILL.md with Frontmatter
Every skill requires YAML frontmatter with name and description:
---
name: <skill-name>
description: '<What it does>. Use when <specific triggers, scenarios, keywords users might say>.'
---Frontmatter Field Requirements
| Field | Required | Constraints |
|---|---|---|
name | Yes | 1-64 chars, lowercase letters/numbers/hyphens only, must match folder name |
description | Yes | 10-1024 chars, must describe WHAT it does AND WHEN to use it |
license | No | License name or reference to bundled LICENSE.txt |
compatibility | No | 1-500 chars, environment requirements if needed |
metadata | No | Key-value pairs for additional properties |
allowed-tools | No | Space-delimited list of pre-approved tools (experimental) |
Description Best Practices
CRITICAL: The description is the PRIMARY mechanism for automatic skill discovery. Include:
- WHAT the skill does (capabilities)
- WHEN to use it (triggers, scenarios, file types)
- Keywords users might mention in requests
Good example:
description: 'Toolkit for testing local web applications using Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or view browser console logs. Supports Chrome, Firefox, and WebKit.'Poor example:
description: 'Web testing helpers'Step 3: Write the Skill Body
After the frontmatter, add markdown instructions. Recommended sections:
| Section | Purpose |
|---|---|
# Title | Brief overview |
## When to Use This Skill | Reinforces description triggers |
## Prerequisites | Required tools, dependencies |
## Step-by-Step Workflows | Numbered steps for tasks |
## Troubleshooting | Common issues and solutions |
## References | Links to bundled docs |
For standards and review skills, rules are mandatory unless explicitly marked
Optional. For advisory skills, distinguish requirements, recommendations, and
examples with consistent labels.
Define named thresholds, modes, phases, or terms before first use, and keep one authoritative definition for each concept.
State each policy definition (what the policy is, its exceptions, their criteria) once, in a single designated authority section, and link to that authority by anchor from every other skill or section that needs the policy. Keep role-specific operational instructions (what to do, flag, or test) inline in the document whose role they serve. Restated definitions silently rot when the authority changes, while a link cannot drift and an instruction stated in only one place cannot drift. A reader executing a workflow or checklist must never need the linked definition to perform an action — they follow the link only to understand why.
Use real markdown headings for durable rule sections. Avoid bold paragraphs as pseudo-headings when the section may need a table-of-contents entry, deep link, or review reference.
Show full SKILL.md (400 more words)Show less
Step 4: Add Optional Directories (If Needed)
| Folder | Purpose | When to Use |
|---|---|---|
scripts/ | Executable code (Python, Bash, JS) | Automation that performs operations |
references/ | Documentation agent reads | API references, schemas, guides |
assets/ | Static files used AS-IS | Images, fonts, templates |
templates/ | Starter code agent modifies | Scaffolds to extend |
Skill Body Organization
Target SKILL.md under 500 lines; review carefully above 600 lines. Exceeding
the target is acceptable when splitting always-needed workflow or review rules
would make the skill less effective. Split situational references first.
Keep these in SKILL.md:
- Routing, prerequisites, and precedence rules
- The main workflow and required feedback loops
- Mandatory validation or review checklists
- Rules needed on nearly every invocation
Move these to reference files:
- Element-specific, type-specific, or platform-specific rules
- Long examples and templates
- Rare edge cases and background material
- Appendices or migration notes
Each reference file should state its purpose and when the agent should load it.
Keep references one level deep from SKILL.md.
When one skill extends another, state what it inherits, overrides, or adds. Link to the parent skill or reference file and keep child-skill overrides narrow.
Example: Complete Skill Structure
my-awesome-skill/
├── SKILL.md # Required instructions
├── LICENSE.txt # Optional license file
├── scripts/
│ └── helper.py # Executable automation
├── references/
│ ├── api-reference.md # Detailed docs
│ └── examples.md # Usage examples
├── assets/
│ └── diagram.png # Static resources
└── templates/
└── starter.ts # Code scaffoldQuick Start: Duplicate This Template
- Copy the
make-skill-template/folder - Rename to your skill name (lowercase, hyphens)
- Update
SKILL.md:- Change
name:to match folder name - Write a keyword-rich
description: - Replace body content with your instructions
- Change
- Add bundled resources as needed
- Review with the Reviewing Skills skill
Validation Checklist
- Folder name is lowercase with hyphens
-
namefield matches folder name exactly -
descriptionis 10-1024 characters -
descriptionexplains WHAT and WHEN -
descriptionis wrapped in single quotes - Body content targets under 500 lines and is reviewed carefully above 600 lines
- Always-needed workflow and review rules remain in
SKILL.md - Situational details are split into reference files with clear load conditions
- Named thresholds, modes, phases, or terms are defined before first use
- Policy definitions are stated once in a designated authority section and linked from everywhere else; role-specific instructions stay inline
- Standards/review rules are mandatory unless explicitly marked
Optional - Deep links, TOC anchors, and referenced files resolve after heading changes
- Bundled assets are under 5MB each
Troubleshooting
| Issue | Solution |
|---|---|
| Skill not discovered | Improve description with more keywords and triggers |
| Validation fails on name | Ensure lowercase, no consecutive hyphens, matches folder |
| Description too short | Add capabilities, triggers, and keywords |
| Assets not found | Use relative paths from skill root |
References
- Agent Skills official spec: https://agentskills.io/specification
- Skill authoring best practices: https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices
© ruby-git, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/make-skill-template of ruby-git/ruby-git.
Open the folder on GitHubat commit f3bf20f
Compare with similar skills
Skill Scaffolding for GitHub Copilot next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Scaffolding for GitHub Copilot this skillruby-git/ruby-git | 1.8k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 794 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase | 10k | 10 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Claude Code Command Developmentanthropics/claude-plugins-official | 37k | 10 repos | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Plugin Structureanthropics/claude-plugins-official | 37k | 10 repos | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Claude Code Skill Developer Guide
diet103/claude-code-infrastructure-showcase
A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.
Darwin Skill Optimizer
alchaincyf/darwin-skill
Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.
- Official
Claude Code Command Development
anthropics/claude-plugins-official
Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.
- Official
Claude Code Plugin Structure
anthropics/claude-plugins-official
Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.
Skill Release Gate
rohitg00/ai-engineering-from-scratch
Evaluates an Agent Skill bundle before release for structure, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity and host portability.
More from ruby-git/ruby-git
All 30 skills in this repoAddress PR Feedback for ruby-git
ruby-git/ruby-git
Addresses unresolved pull request review threads and suppressed (low-confidence) Copilot review comments on the current branch, folds each fix into the…
Breaking Change Analysis
ruby-git/ruby-git
Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.
CI/CD Failure Troubleshooting
ruby-git/ruby-git
Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.
Git Command Class Implementation
ruby-git/ruby-git
Scaffolds and reviews `Git::Commands::*` classes in the ruby-git library, with unit tests, integration tests and YARD docs, using the Base command architecture.
Gem Dependency Management
ruby-git/ruby-git
Workflow for updating gem dependencies and fixing CVEs in the ruby-git project: assess with bundle outdated and audit, edit the gemspec, test, then commit with conventional messages.
Extract Command from Git::Lib
ruby-git/ruby-git
Migrates a direct command call in Ruby Git's Git::Lib to a Git::Commands class, as part of a Strangler Fig redesign, with a plan, legacy tests and a pull request.
Related
Categories
Questions about Skill Scaffolding for GitHub Copilot
What does Skill Scaffolding for GitHub Copilot do?
Creates new Agent Skills for GitHub Copilot: scaffolds the skill folder under .github/skills, writes SKILL.md with proper frontmatter and adds optional scripts, references and assets. A meta-skill for authoring other skills.md with valid frontmatter, writes the body and adds optional scripts, references and assets folders only when they are needed.
When should I use Skill Scaffolding for GitHub Copilot?
Skill Scaffolding for GitHub Copilot fits situations like: creating a new skill for a GitHub Copilot setup; scaffolding a skill folder with scripts, references or assets; improving a skill's description so it is easier to trigger; learning what the Agent Skills specification expects.
How do I install Skill Scaffolding for GitHub Copilot in Claude Code?
Run `npx skills add ruby-git/ruby-git --skill make-skill-template -a claude-code`. Or copy the skill folder (.github/skills/make-skill-template in ruby-git/ruby-git) into .claude/skills/make-skill-template in your project. Claude Code loads it when a task matches its description.
How do I install Skill Scaffolding for GitHub Copilot in Codex?
Run `npx skills add ruby-git/ruby-git --skill make-skill-template -a codex`. Or copy the skill folder (.github/skills/make-skill-template in ruby-git/ruby-git) into .agents/skills/make-skill-template in your project. Codex loads it when a task matches its description.
Can I use Skill Scaffolding for GitHub Copilot in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruby-git/ruby-git --skill make-skill-template -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/make-skill-template, .gemini/skills/make-skill-template, .github/skills/make-skill-template and .opencode/skills/make-skill-template in your project.
What does Skill Scaffolding for GitHub Copilot need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill Scaffolding for GitHub Copilot is instructions for the agent only. Our summary lists: GitHub Copilot Chat with the skill file attached.
Does Skill Scaffolding for GitHub Copilot access the network?
SKILL.md names 2 domains. As links in the text: agentskills.io and platform.claude.com. This is read from the text; nothing was executed.
Is Skill Scaffolding for GitHub Copilot safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Skill Scaffolding for GitHub Copilot use?
Skill Scaffolding for GitHub Copilot is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill Scaffolding for GitHub Copilot use?
About 2.5k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Skill Scaffolding for GitHub Copilot?
Skills that share tags, products or a category with Skill Scaffolding for GitHub Copilot: Skill Creator (Azure/azqr, 794 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars) and Claude Code Command Development (anthropics/claude-plugins-official, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Scaffolding for GitHub Copilot?
ruby-git (a GitHub organization) maintains it in ruby-git/ruby-git, which has 1,799 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 2, 2026.
Source: ruby-git/ruby-git on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.