create-custom-prompt

Create reusable VS Code prompt files with correct frontmatter and placement.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Binh230199/ai --skill create-custom-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-custom-prompt
Source: https://github.com/Binh230199/ai/tree/main/.github/skills/create-custom-prompt
Command: npx skills add https://github.com/Binh230199/ai --skill create-custom-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create, update, and review VS Code prompt files so repetitive tasks can be turned into reusable slash commands with the right structure and metadata.

Core Features & Use Cases

  • Prompt file guidance: Explains the correct .prompt.md format, including frontmatter fields and body structure.
  • Placement conventions: Distinguishes between workspace prompts in .github/prompts/ and user-level prompts in ~/.copilot/prompts/.
  • Reusable task design: Helps you define focused prompts for tasks like commit message generation, code scaffolding, and security review.

Quick Start

Create a new prompt file in the correct VS Code prompts folder and write a single, well-scoped instruction set that matches the required frontmatter and usage pattern.

Frequently Asked Questions about create-custom-prompt

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

FAQPage Schema
How do I create reusable VS Code prompts for slash-command workflows?

Reusable VS Code prompt files are `.prompt.md` documents containing specific frontmatter and body instructions, placed in designated workspace or user-level directories to enable slash-command automation.

Where should I place prompt files for VS Code Copilot automation?

Prompt files for VS Code Copilot automation belong in the `.github/prompts/` folder for workspace-level access or the `~/.copilot/prompts/` directory for user-level availability.

What tasks are suitable for prompt-driven automation using prompt files?

Prompt-driven automation using prompt files suits focused, repetitive tasks like code scaffolding, commit message generation, and security review, utilizing manually invoked editor prompts with defined input variables.

Does VS Code prompt file creation require specific frontmatter and input variables?

VS Code prompt file creation requires correct frontmatter to define supported agents, models, tools, and input variables, ensuring the prompt executes properly during manually invoked slash-command workflows.

What is the best way to structure a `.prompt.md` file for slash commands?

The best way to structure a `.prompt.md` file is to define a single, well-scoped instruction set matching the required frontmatter fields, supported agents, models, tools, and input variables.