Agent skill

Create Skill Sample

by pnp in pnp/copilot-prompts

This skill should be used when the user asks to "create a new skill sample", "add a skill", "scaffold a new skill", "contribute a skill", "create a GitHub Copilot skill", "build a custom skill", or…

MITAuto-check passedDevelopment

Install Create Skill Sample

skills CLI
$ npx skills add pnp/copilot-prompts --skill create-skill-sample -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pnp/copilot-prompts create-skill-sample --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pnp/copilot-prompts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/create-skill-sample .claude/skills/create-skill-sample && rm -rf skills-src

Use ~/.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/

Facts

Skill name
create-skill-sample
GitHub stars
891
Token cost
~3.1k tokens
SKILL.md length
868 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user asks to "create a new skill sample", "add a skill", "scaffold a new skill", "contribute a skill", "create a GitHub Copilot skill", "build a custom skill", or…

  • Works in 4 steps: Create SKILL.md → Create README.md → Create Metadata (assets/sample.json) → …
  • Asks to create a new skill sample
  • SKILL.md covers Before Starting, Sample Directory Structure, Step 1: Create SKILL.md and Step 2: Create README.md, plus 4 more sections
  • Reaches github.com and m365-visitor-stats.azurewebsites.net

What it does

Create Skill Sample is an agent skill from pnp/copilot-prompts. This skill should be used when the user asks to "create a new skill sample", "add a skill", "scaffold a new skill", "contribute a skill", "create a GitHub Copilot skill", "build a custom skill", or needs to create a new GitHub Copilot custom skill sample with proper folder structure, SKILL.md, README, and sample.json metadata inside the skills folder. Do NOT use this skill for simple prompt samples or agent instructions.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Technical documentation, Agent instruction files and File organization. It works with GitHub and C#. The repository describes itself as: Examples of prompts for Microsoft Copilot. The licence is MIT.

When your agent uses it

  • Asks to create a new skill sample
  • Scaffold a new skill
  • Contribute a skill
  • Create a GitHub Copilot skill

Example prompts

  • “create a new skill sample”
  • “add a skill”
  • “scaffold a new skill”
  • “/create-skill-sample”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Create SKILL.md
  2. Create README.md
  3. Create Metadata (assets/sample.json)
  4. Remind About Screenshots

What it can do on your machine

Read from SKILL.md and the folder at commit ce45963. 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 markdown and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • m365-visitor-stats.azurewebsites.net
    • copilot.github.com
    • code.visualstudio.com
    • pnp.github.io

    Also links to:

    • adoption.microsoft.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

Create Skill Sample loads about 3.1k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 868 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~111
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k

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 pnp/copilot-prompts at commit ce45963, republished under its MIT licence (© pnp). 868 words, ~3,077 tokens.

Download SKILL.mdSave it as .claude/skills/create-skill-sample/SKILL.md (or your agent's skills folder).
name
create-skill-sample
description
This skill should be used when the user asks to "create a new skill sample", "add a skill", "scaffold a new skill", "contribute a skill", "create a GitHub Copilot skill", "build a custom skill", or needs to create a new GitHub Copilot custom skill sample with proper folder structure, SKILL.md, README, and sample.json metadata inside the skills folder. Do NOT use this skill for simple prompt samples or agent instructions.

Create a New GitHub Copilot Skill Sample

This skill guides creating new custom skill samples for the pnp/copilot-prompts repository. These samples live inside samples/skills/ and represent reusable instruction files (SKILL.md) that teach GitHub Copilot how to perform specific, repeatable tasks.

Before Starting

Critical: Always ask the user for the following information before scaffolding:

  1. Skill name — a short, descriptive name for the skill (e.g., "Code Review for C#", "API Documentation Generator", "Unit Test Scaffolder")
  2. Skill purpose — a clear description of what the skill does. What task does it teach GitHub Copilot to perform?
  3. Trigger phrases — 3–5 example phrases a user might say to activate the skill (e.g., "review my C# code", "generate API docs")
  4. Inputs needed — what information the skill needs from the user before it can proceed (e.g., a source file, a framework version, a language)
  5. Output format — what the skill produces (e.g., a Markdown report, generated code files, a checklist)
  6. Steps — the high-level steps the skill follows (3–7 steps). Each step should be a discrete action.
  7. Rules — any hard constraints the skill must always follow (e.g., "never modify source files directly")
  8. Author name — the contributor's full name
  9. Author GitHub username — the contributor's GitHub handle

If the user doesn't provide all details upfront, ask for the missing ones before proceeding.

Sample Directory Structure

Create the sample in samples/skills/{skill-name}/:

samples/skills/{skill-name}/
├── SKILL.md                  # The skill definition file (core contribution)
├── README.md                 # Documentation and usage instructions
├── assets/
│   └── sample.json           # Metadata for the M365 Solution Gallery

Folder naming rules:

  • Use lowercase and hyphens only (e.g., code-review-csharp, api-docs-generator, unit-test-scaffolder)
  • Do NOT use periods/dots in the folder name
  • Keep it concise but descriptive — 2–5 words
  • Do NOT include prefixes like m365- or github- — skill folders use plain descriptive names

Step 1: Create SKILL.md

Create samples/skills/{skill-name}/SKILL.md following the schema defined in SKILL-SCHEMA.md.

The file must have:

  1. YAML frontmatter with name and description fields
  2. Title — # <Skill Title>
  3. Before Starting — inputs the skill needs from the user
  4. Output Structure — what the skill produces (template, format, file structure)
  5. Steps — ## Step N: <Action> sections with detailed instructions
  6. Rules — non-negotiable constraints
  7. Examples (recommended) — at least one worked input → output example
  8. Validation Checklist (recommended) — self-verification checks
  9. References (optional) — links to documentation or standards
markdown
---
name: {skill-name}
description: This skill should be used when the user asks to "{trigger phrase 1}", "{trigger phrase 2}", "{trigger phrase 3}", or needs to {general description of when to use}.
---

# {Skill Title}

{One-paragraph description of what this skill does.}

## Before Starting

**Critical**: Always gather the following before proceeding:

1. **{Input 1 name}** — {description}
2. **{Input 2 name}** — {description}
3. ...

If the user doesn't provide all details upfront, ask for the missing ones before proceeding.

## Output Structure

{Define the format/template of what the skill produces.}

## Step 1: {First Action}

{Detailed instructions for step 1.}

## Step 2: {Second Action}

{Detailed instructions for step 2.}

...

## Rules

- {Rule 1}
- {Rule 2}
- ...

## Examples

### Example: {Scenario name}

**Input:**
{example input}

**Output:**
{example output}

## Validation Checklist

Before finalizing, verify:
- [ ] {Check 1}
- [ ] {Check 2}
- ...

## References

- [{Reference name}]({url})

SKILL.md rules:

  • NEVER rephrase, rewrite, or modify the user's skill instructions. Copy the steps and rules exactly as provided by the user — word for word, character for character.
  • The name field in frontmatter must match the folder name exactly
  • The description must include specific trigger phrases so Copilot can match user requests
  • Include at least one worked example
  • Keep steps atomic — one action per step
  • Rules should prevent common mistakes

Step 2: Create README.md

Create samples/skills/{skill-name}/README.md using this structure:

markdown
# {Emoji} {Skill Title} for GitHub Copilot

![Screenshot of the skill in use](./assets/demo.png)

## Summary

{Short summary of what this skill does and why it's useful.}

## Skill 💡

The full skill definition is in [`SKILL.md`](./SKILL.md). To use it, copy the `SKILL.md` file into your repository's `.github/skills/{skill-name}/` folder.

### Trigger Phrases

Say any of these to GitHub Copilot to activate the skill:

- *"{Trigger phrase 1}"*
- *"{Trigger phrase 2}"*
- *"{Trigger phrase 3}"*

## Description ℹ️

{A more detailed description of how the skill works — list the steps it follows and what it produces.}

## Contributors 👨💻

[{Author Name}](https://github.com/{github-username})

## Version history

Version|Date|Comments
-------|----|--------
1.0|{Month DD, YYYY}|Initial release

## Instructions 📝

1. Copy the [`SKILL.md`](./SKILL.md) file into your repository at `.github/skills/{skill-name}/SKILL.md`
2. Open the relevant file(s) in VS Code
3. Open GitHub Copilot Chat
4. Say: *"{Primary trigger phrase}"*
5. Copilot will ask for any missing details and then perform the task

### Customization 🚀

{Suggestions for how the user can modify or extend the skill for their own needs.}

## Prerequisites

* [GitHub Copilot](https://copilot.github.com/)
* [Visual Studio Code](https://code.visualstudio.com/)

## Help

We do not support samples, but this community is always willing to help, and we want to improve these samples. We use GitHub to track issues, which makes it easy for community members to volunteer their time and help resolve issues.

You can try looking at [issues related to this sample](https://github.com/pnp/copilot-prompts/issues?q=label%3A%22sample%3A%20{skill-name}%22) to see if anybody else is having the same issues.

If you encounter any issues using this sample, [create a new issue](https://github.com/pnp/copilot-prompts/issues/new).

Finally, if you have an idea for improvement, [make a suggestion](https://github.com/pnp/copilot-prompts/issues/new).

## Disclaimer

**THIS CODE IS PROVIDED *AS IS* WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.**

![](https://m365-visitor-stats.azurewebsites.net/copilot-prompts/copilotprompts-skill-{skill-name})

README rules:

  • The file MUST be named README.md (capital letters)
  • Always include a screenshot reference at the top (use ./assets/demo.png as placeholder)
  • The tracking image at the bottom MUST follow the pattern: https://m365-visitor-stats.azurewebsites.net/copilot-prompts/copilotprompts-skill-{skill-name}
  • Include the Help and Disclaimer sections exactly as shown
  • Use the current date for the version history in {Month DD, YYYY} format
  • Prerequisites always include GitHub Copilot and VS Code
  • The Instructions section should explain how to install the SKILL.md file
Show full SKILL.md (361 more words)Show less

Step 3: Create Metadata (assets/sample.json)

Create samples/skills/{skill-name}/assets/sample.json:

json
[
  {
    "name": "copilotprompts-skill-{skill-name}",
    "source": "pnp",
    "title": "{Skill Title} for GitHub Copilot",
    "shortDescription": "{Short description of what the skill does}",
    "url": "https://github.com/pnp/copilot-prompts/tree/main/samples/skills/{skill-name}",
    "downloadUrl": "https://pnp.github.io/download-partial/?url=https://github.com/pnp/copilot-prompts/tree/main/samples/skills/{skill-name}",
    "longDescription": [
      "{A longer description of what the skill does and why it's useful. Mention how to install it.}"
    ],
    "creationDateTime": "{YYYY-MM-DD}",
    "updateDateTime": "{YYYY-MM-DD}",
    "products": [
      "GitHub Copilot"
    ],
    "metadata": [],
    "thumbnails": [
      {
        "type": "image",
        "order": 100,
        "url": "https://github.com/pnp/copilot-prompts/raw/main/samples/skills/{skill-name}/assets/demo.png",
        "alt": "{Description of the screenshot}"
      }
    ],
    "authors": [
      {
        "gitHubAccount": "{github-username}",
        "pictureUrl": "https://github.com/{github-username}.png",
        "name": "{Author Name}"
      }
    ],
    "references": [
      {
        "name": "GitHub Copilot",
        "description": "GitHub Copilot",
        "url": "https://copilot.github.com/"
      }
    ]
  }
]

Key metadata rules:

  • name: Always copilotprompts-skill-{skill-name} (matches the tracking image ID)
  • products: Always ["GitHub Copilot"] for skill samples
  • source: Always "pnp"
  • url: Points to samples/skills/{skill-name} on GitHub main branch
  • downloadUrl: Uses the pnp partial download service URL
  • creationDateTime and updateDateTime: Use YYYY-MM-DD format with the current date
  • pictureUrl for authors: Use https://github.com/{username}.png as a shortcut

Step 4: Remind About Screenshots

After creating the files, remind the user to:

  1. Add a screenshot of the skill in action as assets/demo.png (or .gif)
  2. Use a resolution of 1920x1080 if possible
  3. The screenshot should show GitHub Copilot executing the skill and producing output
  4. At minimum, provide one static .png file

Validation Checklist

Before finalizing, verify:

  • Folder is inside samples/skills/ (NOT under samples/agent-instructions/ or directly under samples/)
  • Folder name is lowercase with hyphens only, no dots, matches the name in SKILL.md frontmatter
  • SKILL.md exists with valid YAML frontmatter (name and description)
  • SKILL.md follows the schema in SKILL-SCHEMA.md (has Before Starting, Output Structure, Steps, Rules)
  • SKILL.md has at least one worked example
  • README.md exists with correct capitalization
  • README.md explains how to install the skill (copy to .github/skills/)
  • assets/ folder exists
  • assets/sample.json exists with valid JSON
  • sample.json name field matches pattern copilotprompts-skill-{skill-name}
  • sample.json products is ["GitHub Copilot"]
  • sample.json dates are in YYYY-MM-DD format
  • sample.json URLs include the full path samples/skills/{skill-name}
  • README tracking image URL matches copilotprompts-skill-{skill-name}
  • README contains Instructions, Help, and Disclaimer sections
  • Author information is filled in

Key Rules

  • NEVER rephrase, rewrite, or modify the user's skill logic. Always copy their steps and rules verbatim into the SKILL.md. The user's exact wording is the contribution.
  • This skill is for GitHub Copilot custom skill samples ONLY — not for simple prompts or agent instructions
  • Samples MUST go in samples/skills/{skill-name}/, never directly under samples/ or in agent-instructions/
  • Every sample needs exactly: SKILL.md + README.md + assets/sample.json
  • The core contribution is the SKILL.md file — it must follow the schema in SKILL-SCHEMA.md
  • The products field in sample.json is always ["GitHub Copilot"] (these are GitHub Copilot skills)
  • Prerequisites always include GitHub Copilot and VS Code
  • The sample.json feeds the M365 Solution Gallery — accuracy matters
  • Follow existing naming patterns in the skills folder for consistency

© pnp, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. 1 hidden character (zero-width or bidirectional) removed. Raw file

Files

Just SKILL.md in .github/skills/create-skill-sample of pnp/copilot-prompts.

Open the folder on GitHubat commit ce45963

Compare with similar skills

Create Skill Sample 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.

Create Skill Sample compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Skill Sample this skillpnp/copilot-prompts891—~3.1kAutomated safety check: PassMIT
Readme Blueprint Generatorgithub/awesome-copilot40k2 repos~729Automated safety check: PassMIT
Readme Blueprint Generatorappleweiping/WEIPING_WIKI119—~880Automated safety check: PassMIT
Workflow Creatornicepkg/ai-workflow285—~2.6kAutomated safety check: PassMIT
Sync Agentthun-res/vlink115—~893Automated safety check: PassApache-2.0
Export TemplateHurricaHjz/second-yourself113—~4.8kAutomated safety check: WarnMIT

Similar skills

  • Readme Blueprint Generator

    github/awesome-copilot

    Official

    Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation.

    40k GitHub starsUsed in 2 repos~729 tokens
    DevelopmentAuto-check passed
  • Readme Blueprint Generator

    appleweiping/WEIPING_WIKI

    Create, rewrite, or critique high-quality project README.md files.

    119 GitHub stars~880 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Workflow Creator

    nicepkg/ai-workflow

    Create complete Claude Code workflow directories with curated skills.

    285 GitHub stars~2.6k tokensUpdated 8 mo ago
    Agent WorkflowsAuto-check passed
  • Sync Agent

    thun-res/vlink

    基于 VLink 当前代码、doc、目录、工具和 GitHub 工作流事实,审计并同步 AGENTS.md、AI-POLICY.md、Copilot 指令、.agents 路由/索引/语言分册/ CI 说明、skill frontmatter、agents/openai.yaml 与 README 清单.用户 要求"同步 Agent 文件"、"根据代码更新 .agents"、"检查…

    115 GitHub stars~893 tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed
  • Export Template

    HurricaHjz/second-yourself

    Sync THIS LLM-Wiki framework with its public GitHub repo, ONE direction per run: --push (vault → repo) publishes your framework; --pull (repo → vault) updates your framework from a newer repo version.

    113 GitHub stars~4.8k tokensUpdated 5 days ago
    Knowledge ManagementAuto-check: warnings
  • Official

    Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.

    22k GitHub stars~2.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from pnp/copilot-prompts

  • Create Simple Prompt

    pnp/copilot-prompts

    This skill should be used when the user asks to "create a new prompt sample", "add a new prompt sample", "scaffold a new prompt sample", "create a prompt contribution", "add a prompt", or needs to…

    891 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed
  • Create System Prompt

    pnp/copilot-prompts

    This skill should be used when the user asks to "create an agent instruction", "add agent instructions", "scaffold an agent sample", "create a system prompt sample", "add a system prompt", "create a…

    891 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Create Skill Sample

What does Create Skill Sample do?

This skill should be used when the user asks to "create a new skill sample", "add a skill", "scaffold a new skill", "contribute a skill", "create a GitHub Copilot skill", "build a custom skill", or…. Create Skill Sample is an agent skill from pnp/copilot-prompts.json metadata inside the skills folder.

When should I use Create Skill Sample?

Create Skill Sample fits situations like: asks to create a new skill sample; scaffold a new skill; contribute a skill; create a GitHub Copilot skill.

How do I install Create Skill Sample in Claude Code?

Run `npx skills add pnp/copilot-prompts --skill create-skill-sample -a claude-code`. Or copy the skill folder (.github/skills/create-skill-sample in pnp/copilot-prompts) into .claude/skills/create-skill-sample in your project. Claude Code loads it when a task matches its description.

How do I install Create Skill Sample in Codex?

Run `npx skills add pnp/copilot-prompts --skill create-skill-sample -a codex`. Or copy the skill folder (.github/skills/create-skill-sample in pnp/copilot-prompts) into .agents/skills/create-skill-sample in your project. Codex loads it when a task matches its description.

Can I use Create Skill Sample 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 pnp/copilot-prompts --skill create-skill-sample -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-skill-sample, .gemini/skills/create-skill-sample, .github/skills/create-skill-sample and .opencode/skills/create-skill-sample in your project.

What does Create Skill Sample need to run?

SKILL.md names no scripts, command-line tools or credentials: Create Skill Sample is instructions for the agent only.

Does Create Skill Sample access the network?

SKILL.md names 6 domains. In commands or code: github.com, m365-visitor-stats.azurewebsites.net, copilot.github.com, code.visualstudio.com and pnp.github.io; the agent is likely to contact these when it follows the instructions. As links in the text: adoption.microsoft.com. This is read from the text; nothing was executed.

Is Create Skill Sample 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 Create Skill Sample use?

Create Skill Sample 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 Create Skill Sample use?

About 3.1k tokens (SKILL.md is roughly 12k 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 Create Skill Sample?

Skills that share tags, products or a category with Create Skill Sample: Readme Blueprint Generator (github/awesome-copilot, 40k stars), Readme Blueprint Generator (appleweiping/WEIPING_WIKI, 119 stars), Workflow Creator (nicepkg/ai-workflow, 285 stars) and Sync Agent (thun-res/vlink, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Skill Sample?

pnp (a GitHub organization) maintains it in pnp/copilot-prompts, which has 891 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 6, 2026.

Source: pnp/copilot-prompts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.