suggest-awesome-github-copilot-prompts

Analyze current repository context and suggest relevant prompt files from the GitHub awesome-copilot repository that are not already available in this repository.

github/awesome-copilot|Updated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodex

Installation Guide

Select your AI agent

How to use suggest-awesome-github-copilot-prompts on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add suggest-awesome-github-copilot-prompts

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/github/awesome-copilot --skill suggest-awesome-github-copilot-prompts

Fetches suggest-awesome-github-copilot-prompts from github/awesome-copilot and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/suggest-awesome-github-copilot-prompts

Restart Cursor to activate suggest-awesome-github-copilot-prompts. Access via /suggest-awesome-github-copilot-prompts in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Process

Fetch Available Prompts: Extract prompt list and descriptions from awesome-copilot README.prompts.md. Must use #fetch tool.

Scan Local Prompts: Discover existing prompt files in .github/prompts/ folder

Extract Descriptions: Read front matter from local prompt files to get descriptions

Fetch Remote Versions: For each local prompt, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g., https://raw.githubusercontent.com/github/awesome-copilot/main/prompts/<filename>)

Compare Versions: Compare local prompt content with remote versions to identify:

Prompts that are up-to-date (exact match)
Prompts that are outdated (content differs)
Key differences in outdated prompts (tools, description, content)

Analyze Context: Review chat history, repository files, and current project needs

Compare Existing: Check against prompts already available in this repository

Match Relevance: Compare available prompts against identified patterns and requirements

Present Options: Display relevant prompts with descriptions, rationale, and availability status including outdated prompts

Validate: Ensure suggested prompts would add value not already covered by existing prompts

Output: Provide structured table with suggestions, descriptions, and links to both awesome-copilot prompts and similar local prompts AWAIT user request to proceed with installation or updates of specific prompts. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.

Download/Update Assets: For requested prompts, automatically:

Download new prompts to .github/prompts/ folder
Update outdated prompts by replacing with latest version from awesome-copilot
Do NOT adjust content of the files
Use #fetch tool to download assets, but may use curl using #runInTerminal tool to ensure all content is retrieved
Use #todos tool to track progress

Context Analysis Criteria

🔍 Repository Patterns:

Programming languages used (.cs, .js, .py, etc.)

Framework indicators (ASP.NET, React, Azure, etc.)

Project types (web apps, APIs, libraries, tools)

Documentation needs (README, specs, ADRs)

🗨️ Chat History Context:

Recent discussions and pain points

Feature requests or implementation needs

Code review patterns

Development workflow requirements

Output Format

Display analysis results in structured table comparing awesome-copilot prompts with existing repository prompts:

Awesome-Copilot Prompt

Description

Already Installed

Similar Local Prompt

Suggestion Rationale

code-review.prompt.md

Automated code review prompts

❌ No

None

Would enhance development workflow with standardized code review processes

documentation.prompt.md

Generate project documentation

✅ Yes

create_oo_component_documentation.prompt.md

Already covered by existing documentation prompts

debugging.prompt.md

Debug assistance prompts

⚠️ Outdated

debugging.prompt.md

Tools configuration differs: remote uses 'codebase' vs local missing - Update recommended

Version Comparison Process

For each local prompt file, construct the raw GitHub URL to fetch the remote version:

Pattern: https://raw.githubusercontent.com/github/awesome-copilot/main/prompts/<filename>

Fetch the remote version using the #fetch tool

Compare entire file content (including front matter and body)

Identify specific differences:

Front matter changes (description, tools, mode)
Tools array modifications (added, removed, or renamed tools)
Content updates (instructions, examples, guidelines)

Document key differences for outdated prompts

Calculate similarity to determine if update is needed

Requirements

Use githubRepo tool to get content from awesome-copilot repository prompts folder

Scan local file system for existing prompts in .github/prompts/ directory

Read YAML front matter from local prompt files to extract descriptions

Compare local prompts with remote versions to detect outdated prompts

Compare against existing prompts in this repository to avoid duplicates

Focus on gaps in current prompt library coverage

Validate that suggested prompts align with repository's purpose and standards

Provide clear rationale for each suggestion

Include links to both awesome-copilot prompts and similar local prompts

Clearly identify outdated prompts with specific differences noted

Don't provide any additional information or context beyond the table and the analysis

Update Handling

When outdated prompts are identified:

Include them in the output table with ⚠️ status

Document specific differences in the "Suggestion Rationale" column

Provide recommendation to update with key changes noted

When user requests update, replace entire local file with remote version

Preserve file location in .github/prompts/ directory

suggest-awesome-github-copilot-prompts

Installation Guide

How to use suggest-awesome-github-copilot-prompts on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

User Story & Requirements Generation

Competitive Analysis

Roadmap Prioritization

Install Skill

Suggest Awesome GitHub Copilot Prompts

Process

Context Analysis Criteria

Output Format

Local Prompts Discovery Process

Version Comparison Process

Requirements

Icons Reference

Update Handling

Stakeholder Communication

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

premium-frontend-ui

java-springboot

grill-me

premortem

deslop

framer-motion

Reviews

Discussion