Name: copilot-instructions-blueprint-generator
Rating: 67.80000000000001 (1 reviews)
Author: github

copilot-instructions-blueprint-generator

Technology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns and avoiding assumptions.

1.40x

Quality

53%

Does it follow best practices?

Impact

91%

1.40x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/copilot-instructions-blueprint-generator/SKILL.md

Quality

Content

31%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a verbose, monolithic template that relies on boilerplate and pseudo-code interpolation rather than executable, well-structured guidance. Splitting the template into reference files and trimming repeated patterns would materially improve it.

Suggestions

Move the large generated-prompt template and per-technology guideline blocks into separate reference files (e.g. references/prompt-template.md, references/tech-guidelines.md) and keep SKILL.md as a concise overview that points to them.

Replace the repeated "Follow existing patterns / Match... from existing code" boilerplate with a single concise principle and remove generalized best-practice text Claude already knows.

Add concrete, executable steps for how to produce the file (e.g. an actual command or script that emits copilot-instructions.md from detected codebase patterns) instead of only an instruction template.

Dimension	Reasoning	Score
Conciseness	The body is a ~250-line template that repeats boilerplate ("Follow existing patterns", "Match... patterns from existing code") across .NET/Java/JS/React/Angular/Python blocks and restates generalized best practices Claude already knows, making it noticeably verbose and padded.	2 / 5
Actionability	It provides a high-level prompt template and conditional `${...}` interpolation rather than concrete, executable guidance for the skill itself — there is no runnable script or copy-paste command, only abstract instruction text.	2 / 5
Workflow Clarity	A rough 3-part sequence (Core Instruction Structure, Codebase Analysis, Implementation Notes) with numbered steps is present, but there are no validation checkpoints or feedback loops and the generation step is only implicitly defined.	3 / 5
Progressive Disclosure	All content is inlined into a single monolithic SKILL.md with no bundle files and no split references; the large generated-prompt template and per-technology blocks should live in separate files rather than being inlined.	2 / 5
	Total	9 / 20 Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct with strong trigger keywords, but it omits an explicit "Use when..." trigger clause, which caps its completeness. Adding a usage-trigger sentence would lift it into the top tier.

Suggestions

Append an explicit trigger clause such as "Use when the user wants to generate or update a copilot-instructions.md file for a repository" to satisfy the completeness dimension.

Add natural phrasings a user might actually say (e.g. "set up GitHub Copilot", "generate copilot instructions") to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "creating comprehensive copilot-instructions.md files", "analyzing existing codebase patterns", and "guide GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions" — with comprehensive coverage of what the skill does.	5 / 5
Completeness	The "what" is clearly stated, but there is no explicit "Use when..." trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Good keyword coverage including "copilot-instructions.md", "GitHub Copilot", "architecture patterns", "technology versions", and "codebase patterns", but a few natural trigger phrases a user would say (e.g. "generate copilot instructions", "set up copilot for my repo") are not literally present.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — generating copilot-instructions.md blueprints — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: github/awesome-copilot
Path: skills/copilot-instructions-blueprint-generator/SKILL.md
Commit: f38fb6c

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.