suggest-awesome-github-copilot-prompts
Suggest relevant GitHub Copilot prompt files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing prompts in this repository, and identifying outdated prompts that need updates.
77
72%
Does it follow best practices?
Impact
75%
1.47xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/awesome-copilot/skills/suggest-awesome-github-copilot-prompts/SKILL.mdQuality
Discovery
67%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 effectively communicates specific capabilities around GitHub Copilot prompt management with good distinctiveness. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords. The technical specificity is strong but the discoverability for users could be improved.
Suggestions
Add a 'Use when...' clause with trigger terms like 'copilot prompts', 'find prompts', 'prompt suggestions', or 'update prompts'
Include natural variations users might say such as 'copilot instructions', '.prompt files', or 'prompt templates'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Suggest relevant GitHub Copilot prompt files', 'avoiding duplicates with existing prompts', and 'identifying outdated prompts that need updates'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through context clues. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'GitHub Copilot', 'prompt files', 'awesome-copilot repository', but missing natural user phrases like 'find prompts', 'copilot prompts', 'prompt suggestions', or file extensions users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific references to 'awesome-copilot repository', 'GitHub Copilot prompt files', and the unique combination of suggesting, deduplicating, and updating prompts. Unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides clear, actionable guidance for suggesting and managing GitHub Copilot prompts with good workflow structure and explicit validation checkpoints. The main weakness is some redundancy between sections (version comparison described twice) and inline content that could potentially be consolidated. The output format with example table rows and icon reference is particularly well done.
Suggestions
Consolidate the 'Version Comparison Process' and 'Local Prompts Discovery Process' sections into the main Process steps to eliminate redundancy
Remove duplicate descriptions of steps 4-5 that appear both in the numbered process and in dedicated sections below
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., the version comparison process is described twice - once in Process steps 4-5 and again in a dedicated section). Some sections could be consolidated. | 2 / 3 |
Actionability | Provides concrete, specific guidance with exact file paths (.github/prompts/), specific URLs (raw.githubusercontent.com pattern), tool names (#fetch, #runInTerminal, #todos), and clear output format with example table rows. | 3 / 3 |
Workflow Clarity | Clear 12-step numbered process with explicit validation step (step 10), a critical checkpoint before installation (step 11 with AWAIT directive), and feedback loops for comparing versions. The workflow handles both new installs and updates with clear sequencing. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but everything is inline in a single file. Some sections like 'Version Comparison Process' and 'Local Prompts Discovery Process' repeat information from the main Process section, suggesting content could be better structured. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- github/awesome-copilot
- Commit
9ef5453
- Reviewed
Table of Contents
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.