prompt-builder

Build structured GitHub Copilot prompt files with YAML frontmatter and validation criteria.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill prompt-builder-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-builder
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/prompt-builder
Command: npx skills add https://github.com/selfagency/agentsy --skill prompt-builder-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn vague intentions into clear, structured GitHub Copilot prompts that yield reliable outputs by capturing prompt identity, persona, task requirements, context variables, and validation criteria.

Core Features & Use Cases

  • Requirement gathering: Systematically elicits prompt filename, purpose, category, persona expertise, and measurable task constraints.
  • Context and variable specification: Defines how Copilot should use selections, files, inputs, and workspace variables to ensure the prompt is executable in your environment.
  • Output and quality standards: Enforces output formatting, tool/capability requirements, and success/validation checks to reduce failure modes.

Quick Start

Start by answering the Section 1 questions (Prompt Identity & Purpose) so the assistant can iteratively build a complete .prompt.md file.

Frequently Asked Questions about prompt-builder

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

FAQPage Schema
How do I create structured GitHub Copilot prompts from scratch?

To create structured GitHub Copilot prompts, you must capture prompt identity, persona, task scope, and constraints. This approach systematically elicits filename, purpose, and context variables to generate a production-ready `.prompt.md` file.

What is the best way to define context variables for Copilot prompt templates?

Defining context variables for prompt templates requires specifying how Copilot should use selections, files, and workspace inputs. This ensures the generated prompt is executable within your specific development environment.

Does GitHub Copilot require YAML frontmatter for custom prompt files?

Yes, GitHub Copilot custom prompt files require YAML frontmatter. Your prompt must include mandatory `name` and `description` fields to be properly recognized and executed by the system.

How do I add validation criteria to AI prompt engineering workflows?

Adding validation criteria to AI prompt engineering workflows involves defining output formatting, tool capability requirements, and success checks. This enforces quality standards and reduces failure modes during code generation.

Can I use prompt templates for tool-integrated automation with Copilot?

Yes, you can use prompt templates for tool-integrated automation with Copilot. The templates support workflows where context variables, tool expectations, and specific output formats matter for automated execution.