Skip to content

πŸ” Duplicate Resource ReviewΒ #1793

@github-actions

Description

@github-actions

Summary

How to Use This Report

Review each group below. If the resources are intentionally separate, check the box to mark them as accepted. These will be excluded from future reports.


πŸ†• New Findings

Group 1: Power BI Expert Agents vs Power BI Best Practices Instructions β€” Cross-Type Cluster

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/power-bi-data-modeling-expert.agent.md Agent Expert Power BI data modeling guidance using star schema principles, relationship design, and Microsoft best practices
instructions/power-bi-data-modeling-best-practices.instructions.md Instruction Comprehensive Power BI data modeling best practices based on Microsoft guidance for creating efficient, scalable semantic models using star schema principles
agents/power-bi-dax-expert.agent.md Agent Expert Power BI DAX guidance using Microsoft best practices for performance, readability, and maintainability of DAX formulas
instructions/power-bi-dax-best-practices.instructions.md Instruction Comprehensive Power BI DAX best practices and patterns based on Microsoft guidance for creating efficient, maintainable, and performant DAX formulas
agents/power-bi-visualization-expert.agent.md Agent Expert Power BI report design and visualization guidance using Microsoft best practices for creating effective, performant, and user-friendly reports
instructions/power-bi-report-design-best-practices.instructions.md Instruction Comprehensive Power BI report design and visualization best practices based on Microsoft guidance for creating effective, accessible, and performant reports and dashboards

Why flagged: Three agent+instruction pairs covering the same Power BI sub-domains: (1) data modeling / star schema, (2) DAX formulas / performance, (3) report design / visualization. Each pair shares nearly identical scope β€” the only difference is resource type (agent = interactive expert, instruction = passive guidance). The description wording is 85%+ similar within each pair. A fourth agent (power-bi-performance-expert.agent.md) has no direct instruction counterpart and is not included here.


Group 2: Implementation Plan Generation Agents β€” Identical Descriptions (dropped carryover from #1264)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/planner.agent.md Agent Generate an implementation plan for new features or refactoring existing code.
agents/implementation-plan.agent.md Agent Generate an implementation plan for new features or refactoring existing code.

Why flagged: Both agents share a word-for-word identical description. This pair was originally flagged in #1076 and #1264 but was inadvertently dropped from subsequent reports. Both target the same goal (generating implementation plans before coding), and without clear differentiation in their descriptions, one may make the other redundant.


♻️ Unresolved from Previous Reviews

Groups 3–10: High-confidence pairs (previously flagged in #1641, unresolved)

Group 3: Caveman Mode β€” Agent + Instruction with Identical Description (previously reviewed β€” see #1641 Group 9)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/caveman-mode.agent.md Agent Terse, low-token responses. Minimal words, no fluff. Full capabilities preserved.
instructions/caveman-mode.instructions.md Instruction Terse, low-token responses. Minimal words, no fluff. Full capabilities preserved.

Why flagged: Word-for-word identical description. Same behavior, same directives. One applies passively (applyTo: '**'), the other is explicitly invoked.


Group 4: C#/.NET Janitor Cluster β€” Two Agents with Identical Descriptions + Universal Variant (previously reviewed β€” see #1641 Group 10)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/csharp-dotnet-janitor.agent.md Agent Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
agents/dotnet-upgrade.agent.md Agent Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
agents/janitor.agent.md Agent Perform janitorial tasks on any codebase including cleanup, simplification, and tech debt remediation.

Why flagged: csharp-dotnet-janitor and dotnet-upgrade share a word-for-word identical description. janitor.agent.md broadens the same workflow to any language, potentially making both C#-specific agents redundant.


Group 5: Doublecheck β€” Agent + Skill with Identical Functionality (previously reviewed β€” see #1641 Group 15)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/doublecheck.agent.md Agent Interactive verification agent for AI-generated output. Runs a three-layer pipeline (self-audit, source verification, adversarial review).
skills/doublecheck/SKILL.md Skill Three-layer verification pipeline for AI output. Extracts verifiable claims, finds supporting/contradicting sources, runs adversarial review for hallucination patterns.

Why flagged: Both describe the exact same three-layer verification pipeline for AI output. They differ only in resource type (agent vs skill).


Group 6: Gilfoyle Code Review β€” Agent + Instruction (previously reviewed β€” see #1641 Group 13)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/gilfoyle.agent.md Agent Code review and analysis with the sardonic wit and technical elitism of Bertram Gilfoyle from Silicon Valley.
instructions/gilfoyle-code-review.instructions.md Instruction Gilfoyle-style code review instructions that channel the sardonic technical supremacy of Silicon Valley's most arrogant systems architect.

Why flagged: Same Gilfoyle persona, same code review domain. One performs active review sessions; the other passively applies the same style to all interactions.


Group 7: PRD β€” Agent + Skill (previously reviewed β€” see #1641 Group 14)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/prd.agent.md Agent Generate a comprehensive Product Requirements Document (PRD) in Markdown, detailing user stories, acceptance criteria, technical considerations, and metrics.
skills/prd/SKILL.md Skill Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

Why flagged: Same name (prd), same core purpose β€” generating PRD documents with user stories and acceptance criteria. Cross-type overlap (agent vs skill).


Group 8: MS-SQL DBA β€” Agent + Instruction (previously reviewed β€” see #1641 Group 12)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/ms-sql-dba.agent.md Agent Work with Microsoft SQL Server databases using the MS SQL extension.
instructions/ms-sql-dba.instructions.md Instruction Instructions for customizing GitHub Copilot behavior for MS-SQL DBA chat mode.

Why flagged: The instruction explicitly targets use alongside the ms-sql-dba agent, creating heavily overlapping content for the same SQL Server DBA use case.


Group 9: Context7 β€” Agent + Instruction (previously reviewed β€” see #1641 Group 11)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/context7.agent.md Agent Expert in latest library versions, best practices, and correct syntax using up-to-date documentation via Context7 MCP
instructions/context7.instructions.md Instruction Use Context7 for authoritative external docs and API references when local context is insufficient

Why flagged: Identical name, nearly identical scope (using Context7 MCP for documentation lookup), differing only in resource type.


Group 10: Markdown Accessibility β€” Agent + Instruction (previously reviewed β€” see #1641 Group 17)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/markdown-accessibility-assistant.agent.md Agent Improves the accessibility of markdown files using five GitHub best practices
instructions/markdown-accessibility.instructions.md Instruction Markdown accessibility guidelines based on GitHub's 5 best practices for inclusive documentation

Why flagged: Both reference the same source (GitHub's 5 best practices for markdown accessibility). Identical domain and source material, cross-type overlap.


Groups 11–20: Broader clusters and multi-resource families (previously flagged in #1641, unresolved)

Group 11: Azure Functions vs Durable Functions C# β€” Near-Identical Instructions (previously reviewed β€” see #1641 Group 1)

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/azure-functions-csharp.instructions.md Instruction Guidelines and best practices for building Azure Functions in C# using the isolated worker model
instructions/azure-durable-functions-csharp.instructions.md Instruction Guidelines and best practices for building Azure Durable Functions in C# using the isolated worker model

Why flagged: Descriptions are 95%+ identical (only difference is "Durable"), same applyTo patterns, closely overlapping content. Durable Functions is a specific extension of Azure Functions and may warrant a merged instruction with clear delineation.


Group 12: Dataverse Python β€” Advanced Patterns vs Production Code Skills (previously reviewed β€” see #1641 Group 2)

  • Reviewed β€” these are intentionally separate
Resource Type Description
skills/dataverse-python-advanced-patterns/SKILL.md Skill Generate production code for Dataverse SDK using advanced patterns, error handling, and optimization techniques.
skills/dataverse-python-production-code/SKILL.md Skill Generate production-ready Python code using Dataverse SDK with error handling, optimization, and best practices

Why flagged: Both generate production-ready Python code for the same Dataverse SDK with the same themes (error handling, retry logic, OData optimization). Descriptions differ only in wording.


Group 13: Spring Data Cosmos Migration Guides β€” Cassandra vs JPA (previously reviewed β€” see #1641 Group 3)

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/convert-cassandra-to-spring-data-cosmos.instructions.md Instruction Step-by-step guide for converting Spring Boot Cassandra applications to use Azure Cosmos DB with Spring Data Cosmos
instructions/convert-jpa-to-spring-data-cosmos.instructions.md Instruction Step-by-step guide for converting Spring Boot JPA applications to use Azure Cosmos DB with Spring Data Cosmos

Why flagged: Both describe a "step-by-step guide for converting Spring Boot X applications to use Azure Cosmos DB with Spring Data Cosmos" β€” differing only in source technology (Cassandra vs JPA). Same destination, likely shared structural content.


Group 14: Azure Logic Apps β€” Agent + Instruction Cross-Type Overlap (previously reviewed β€” see #1641 Group 4)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/azure-logic-apps-expert.agent.md Agent Expert guidance for Azure Logic Apps development focusing on workflow design, integration patterns, and JSON-based Workflow Definition Language.
instructions/azure-logic-apps-power-automate.instructions.md Instruction Guidelines for developing Azure Logic Apps and Power Automate workflows with best practices for Workflow Definition Language (WDL), integration patterns, and enterprise automation

Why flagged: Both target Azure Logic Apps development with the same focus areas: Workflow Definition Language, integration patterns, and enterprise automation. Core content domain is identical.


Group 15: Declarative Agents β€” Instruction + Skill Cross-Type Overlap (previously reviewed β€” see #1641 Group 5)

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/declarative-agents-microsoft365.instructions.md Instruction Comprehensive development guidelines for Microsoft 365 Copilot declarative agents with schema v1.5, TypeSpec integration, and Microsoft 365 Agents Toolkit workflows
skills/declarative-agents/SKILL.md Skill Complete development kit for Microsoft 365 Copilot declarative agents with three comprehensive workflows (basic, advanced, validation), TypeSpec support, and Microsoft 365 Agents Toolkit integration

Why flagged: Both cover M365 Copilot declarative agent development with the same technologies: TypeSpec, M365 Agents Toolkit, schema v1.5. Significant overlap in purpose; differ only in passive (instruction) vs active (skill) delivery.


Group 16: Structured Autonomy Skills β€” Plan / Generate / Implement (previously reviewed β€” see #1641 Group 6)

  • Reviewed β€” these are intentionally separate
Resource Type Description
skills/structured-autonomy-plan/SKILL.md Skill Structured Autonomy Planning Prompt
skills/structured-autonomy-generate/SKILL.md Skill Structured Autonomy Implementation Generator Prompt
skills/structured-autonomy-implement/SKILL.md Skill Structured Autonomy Implementation Prompt

Why flagged: Three skills sharing the "Structured Autonomy" prefix β€” all described as "[phase] Prompt" for the same workflow. Descriptions are extremely terse and don't explain their differentiation from each other or from general implementation-plan skills.


Group 17: Prompt Engineering Safety β€” Instruction + Skill Cross-Type Overlap (previously reviewed β€” see #1641 Group 7)

  • Reviewed β€” these are intentionally separate
Resource Type Description
instructions/ai-prompt-engineering-safety-best-practices.instructions.md Instruction Comprehensive best practices for AI prompt engineering, safety frameworks, bias mitigation, and responsible AI usage
skills/ai-prompt-engineering-safety-review/SKILL.md Skill Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and hallucination risks.

Why flagged: Both cover AI prompt engineering safety with the same focus areas (bias mitigation, safety frameworks, security). Significant thematic overlap across both types.


Group 18: Expert Software Engineers β€” C++ vs .NET Generic Agents (previously reviewed β€” see #1641 Group 8)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/expert-cpp-software-engineer.agent.md Agent Provide expert C++ software engineering guidance using modern C++ and industry best practices.
agents/expert-dotnet-software-engineer.agent.md Agent Provide expert .NET software engineering guidance using modern software design patterns.

Why flagged: Nearly identical templated descriptions ("Provide expert X software engineering guidance..."). Both share an identical tools list with 20+ entries. Note that agents/CSharpExpert.agent.md also exists for C#/.NET, potentially forming a three-way overlap.


Group 19: Code Tour β€” Agent + Skill Cross-Type Overlap (previously reviewed β€” see #1641 Group 16)

  • Reviewed β€” these are intentionally separate
Resource Type Description
agents/code-tour.agent.md Agent Expert agent for creating and maintaining VSCode CodeTour files with comprehensive schema support and best practices
skills/code-tour/SKILL.md Skill Use this skill to create CodeTour .tour files β€” persona-targeted, step-by-step walkthroughs that link to real files and line numbers.

Why flagged: Both create VSCode CodeTour .tour files for the same use cases. Core purpose is identical; the skill adds persona targeting while the agent adds schema depth.


Group 20: Suggest Awesome Copilot Resources β€” Three Near-Identical Skills (previously reviewed β€” see #1641 Group 18)

  • Reviewed β€” these are intentionally separate
Resource Type Description
skills/suggest-awesome-github-copilot-agents/SKILL.md Skill Suggest relevant GitHub Copilot Custom Agents files from the awesome-copilot repository based on current repository context and chat history
skills/suggest-awesome-github-copilot-instructions/SKILL.md Skill Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history
skills/suggest-awesome-github-copilot-skills/SKILL.md Skill Suggest relevant GitHub Copilot skills from the awesome-copilot repository based on current repository context and chat history

Why flagged: Three skills with nearly identical structure and wording β€” differing only in the resource type they suggest (agents vs instructions vs skills). Could potentially be a single parameterized skill.


Generated by Duplicate Resource Detector

Generated by Duplicate Resource Detector Β· ● 10.4M Β· β—·

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions