suggest-awesome-github-copilot-instructions
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: suggest-awesome-github-copilot-instructions
description: Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on c…
category: engineering
runtime: no special runtime
---
# suggest-awesome-github-copilot-instructions output preview
## PART A: Task fit
- Use case: Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository, and identifying outdated instructions that need updates. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Process / Context Analysis Criteria / Output Format” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository, and identifying outdated instructions that need updates. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Process / Context Analysis Criteria / Output Format” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Process / Context Analysis Criteria / Output Format”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: suggest-awesome-github-copilot-instructions
description: Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on c…
category: engineering
source: tomevault-io/skills-registry
---
# suggest-awesome-github-copilot-instructions
## When to use
- Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository cont…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Process / Context Analysis Criteria / Output Format” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "suggest-awesome-github-copilot-instructions" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Process / Context Analysis Criteria / Output Format
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Suggest Awesome GitHub Copilot Instructions
Analyze current repository context and suggest relevant copilot-instruction files from the GitHub awesome-copilot repository that are not already available in this repository.
Process
- Fetch Available Instructions: Extract instruction list and descriptions from awesome-copilot README.instructions.md. Must use
#fetchtool. - Scan Local Instructions: Discover existing instruction files in
.github/instructions/folder - Extract Descriptions: Read front matter from local instruction files to get descriptions and
applyTopatterns - Fetch Remote Versions: For each local instruction, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g.,
https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/<filename>) - Compare Versions: Compare local instruction content with remote versions to identify:
- Instructions that are up-to-date (exact match)
- Instructions that are outdated (content differs)
- Key differences in outdated instructions (description, applyTo patterns, content)
- Analyze Context: Review chat history, repository files, and current project needs
- Compare Existing: Check against instructions already available in this repository
- Match Relevance: Compare available instructions against identified patterns and requirements
- Present Options: Display relevant instructions with descriptions, rationale, and availability status including outdated instructions
- Validate: Ensure suggested instructions would add value not already covered by existing instructions
- Output: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions AWAIT user request to proceed with installation or updates of specific instructions. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
- Download/Update Assets: For requested instructions, automatically:
- Download new instructions to
.github/instructions/folder - Update outdated instructions by replacing with latest version from awesome-copilot
- Do NOT adjust content of the files
- Use
#fetchtool to download assets, but may usecurlusing#runInTerminaltool to ensure all content is retrieved - Use
#todostool to track progress
- Download new instructions to
Context Analysis Criteria
🔍 Repository Patterns:
- Programming languages used (.cs, .js, .py, .ts, etc.)
- Framework indicators (ASP.NET, React, Azure, Next.js, etc.)
- Project types (web apps, APIs, libraries, tools)
- Development workflow requirements (testing, CI/CD, deployment)
🗨️ Chat History Context:
- Recent discussions and pain points
- Technology-specific questions
- Coding standards discussions
- Development workflow requirements
Output Format
Display analysis results in structured table comparing awesome-copilot instructions with existing repository instructions:
| Awesome-Copilot Instruction | Description | Already Installed | Similar Local Instruction | Suggestion Rationale |
|---|---|---|---|---|
| blazor.instructions.md | Blazor development guidelines | ✅ Yes | blazor.instructions.md | Already covered by existing Blazor instructions |
| reactjs.instructions.md | ReactJS development standards | ❌ No | None | Would enhance React development with established patterns |
| java.instructions.md | Java development best practices | ⚠️ Outdated | java.instructions.md | applyTo pattern differs: remote uses '**/*.java' vs local '*.java' - Update recommended |
Local Instructions Discovery Process
- List all
*.instructions.mdfiles in theinstructions/directory - For each discovered file, read front matter to extract
descriptionandapplyTopatterns - Build comprehensive inventory of existing instructions with their applicable file patterns
- Use this inventory to avoid suggesting duplicates
Version Comparison Process
- For each local instruction file, construct the raw GitHub URL to fetch the remote version:
- Pattern:
https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/<filename>
- Pattern:
- Fetch the remote version using the
#fetchtool - Compare entire file content (including front matter and body)
- Identify specific differences:
- Front matter changes (description, applyTo patterns)
- Content updates (guidelines, examples, best practices)
- Document key differences for outdated instructions
- Calculate similarity to determine if update is needed
File Structure Requirements
Based on GitHub documentation, copilot-instructions files should be:
- Repository-wide instructions:
.github/copilot-instructions.md(applies to entire repository) - Path-specific instructions:
.github/instructions/NAME.instructions.md(applies to specific file patterns viaapplyTofrontmatter) - Community instructions:
instructions/NAME.instructions.md(for sharing and distribution)
Front Matter Structure
Instructions files in awesome-copilot use this front matter format:
---
description: 'Brief description of what this instruction provides'
applyTo: '**/*.js,**/*.ts' # Optional: glob patterns for file matching
---Requirements
- Use
githubRepotool to get content from awesome-copilot repository instructions folder - Scan local file system for existing instructions in
.github/instructions/directory - Read YAML front matter from local instruction files to extract descriptions and
applyTopatterns - Compare local instructions with remote versions to detect outdated instructions
- Compare against existing instructions in this repository to avoid duplicates
- Focus on gaps in current instruction library coverage
- Validate that suggested instructions align with repository's purpose and standards
- Provide clear rationale for each suggestion
- Include links to both awesome-copilot instructions and similar local instructions
- Clearly identify outdated instructions with specific differences noted
- Consider technology stack compatibility and project-specific needs
- Don't provide any additional information or context beyond the table and the analysis
Icons Reference
- ✅ Already installed and up-to-date
- ⚠️ Installed but outdated (update available)
- ❌ Not installed in repo
Update Handling
When outdated instructions 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/instructions/directory
Source: calmripple/calmripple.github.io — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review