Guides
    github copilot
    skill.md
    comparison

    GitHub Copilot Skills vs SKILL.md — How They Compare (2026)

    Microsoft launched skills for GitHub Copilot. How do they compare to the SKILL.md standard used by Claude Code, Codex CLI, and Cursor? Format, portability, and ecosystem.

    April 11, 20266 min read0 views
    Share:

    Microsoft recently launched official skill support for GitHub Copilot through the dotnet/skills repository and the .github + MCP extension for Visual Studio 2026. This is a major validation of the agent skills concept — but it also creates confusion about how Copilot skills relate to the SKILL.md standard that Claude Code, Codex CLI, Cursor, and 20+ other agents already use.

    Here's how they compare.

    What Microsoft launched

    Microsoft's approach centers on the dotnet/skills GitHub repository. It contains official .NET skill packs — SKILL.md files that teach Copilot about .NET-specific patterns, migrations, performance optimization, and security best practices.

    In Visual Studio 2026, you can register a GitHub repository as a "skill marketplace" and browse/install skills directly from the IDE. Copilot auto-invokes skills when it identifies that a skill would help with the current task.

    In VS Code with Copilot Insiders, you add the marketplace URL in extension settings and browse skills through the extensions explorer.

    The format is the same

    Here's the important part: Microsoft adopted the SKILL.md format. The dotnet/skills repository uses the same YAML frontmatter + markdown body structure as Claude Code skills:

    ---
    name: dotnet-performance
    description: Helps optimize .NET application performance.
    ---
    
    # .NET Performance Optimization
    
    When analyzing .NET code for performance:
    ...
    

    This means a SKILL.md file written for Claude Code can work in Copilot, and vice versa. The open standard is converging across all major agents.

    Key differences

    Activation

    SKILL.md (Claude Code, Codex CLI): Description-based activation. The agent reads the description and decides if the skill matches the current task. No manual invocation needed.

    Copilot (VS 2026): Auto-invoked when Copilot identifies a match. No slash commands yet — you can hint by mentioning the skill name in your prompt. This is effectively the same activation model, just less mature.

    Skill sources

    SKILL.md ecosystem: Multiple sources — Agensi marketplace (curated, security-reviewed), GitHub repositories (unvetted), community shares.

    Copilot: Currently limited to GitHub repositories registered as marketplaces. The dotnet/skills repo is the primary official source. Third-party "marketplace repos" are emerging but the ecosystem is early.

    Scope

    SKILL.md agents: Support both personal skills (global, all projects) and project-level skills (repo-specific). Most agents support ~/.agent/skills/ for personal and .agent/skills/ for project.

    Copilot: Currently focused on per-workspace skills through marketplace registration. The personal/project distinction is still evolving.

    Ecosystem maturity

    SKILL.md: Six months of ecosystem growth. 80+ curated skills on Agensi, hundreds of thousands indexed from GitHub, active creator community, MCP integration, marketplace infrastructure.

    Copilot skills: Weeks old. One official source (dotnet/skills). Limited to .NET-focused skills so far. Microsoft has signaled more will come but the ecosystem is very early.

    What this means for developers

    If you use Copilot

    You can start using skills today through the dotnet/skills repository. But the selection is limited to .NET. For broader coverage, install Claude Code alongside Copilot and use the SKILL.md ecosystem for non-.NET tasks.

    If you use Claude Code

    Nothing changes. The SKILL.md format you already use is the same format Copilot adopted. Your existing skills continue to work. As Copilot's skill support matures, your skills will likely work there too.

    If you use multiple agents

    This is the SKILL.md standard's strongest argument. Write a skill once, and it works in Claude Code, Codex CLI, Cursor, Gemini CLI, and now Copilot. As Microsoft's implementation matures, the same file will work in Visual Studio and VS Code. No vendor lock-in.

    The bigger picture

    Microsoft adopting SKILL.md is significant because it validates the format as the industry standard. When the company behind GitHub Copilot (the most widely-used AI coding tool) adopts the same file format as Claude Code, Codex CLI, and Cursor, the standard is no longer one company's initiative. It's the industry's shared format.

    For skill creators, this means a larger addressable market. A skill published on Agensi now potentially serves users of Claude Code, Codex CLI, Cursor, Gemini CLI, AND GitHub Copilot. One file, every agent.

    For skill buyers, this means your investment is portable. Skills you purchase today work across your entire toolchain and will continue working as new agents adopt the standard.

    How to use SKILL.md skills in Copilot

    Until Copilot's marketplace ecosystem expands, you can:

    1. Create a private GitHub repo with your SKILL.md skills
    2. Register it as a marketplace in VS 2026 or VS Code Copilot settings
    3. Browse and install from the extensions panel

    Or continue using Agensi with Claude Code for the broadest selection of curated, security-reviewed skills.


    Browse cross-agent skills at Agensi — compatible with Claude Code, Codex CLI, Cursor, Gemini CLI, and more.

    Find the right skill for your workflow

    Browse our marketplace of AI agent skills, ready to install in seconds.

    Browse Skills

    Related Articles