You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Known accepted (excluded): 12 groups from previous reviews (π Duplicate Resource ReviewΒ #882, π Duplicate Resource ReviewΒ #981, π Duplicate Resource ReviewΒ #1076, π Duplicate Resource ReviewΒ #1173) β Spring Boot Java/Kotlin skills, MCP Server Generator skills (10 languages), Linux Triage skills, Blueprint Mode variants, Java Version Upgrade instructions (17β21, 21β25), FlowStudio Power Automate skills, GitHub Issue Creation skills, Azure Verified Modules, Microsoft Agent Framework .NET/Python, Semantic Kernel .NET/Python, OO Component Documentation (Create/Update), Beast Mode Agents.
Note: Issue π Duplicate Resource ReviewΒ #1347 is currently open with 12 unreviewed groups (MCP Server Expert Agents, MCP Server Instructions, Copilot SDK Instructions, Doublecheck, Implementation Plan Agent+Skill, Polyglot Test Agents, ColdFusion CFC/CFM, Spring Boot CosmosDB, .NET MAUI vs WPF, PostgreSQL vs MS-SQL DBA agents, Java 11β17 upgrade, Arch Linux triple overlap). The groups below are not covered by π Duplicate Resource ReviewΒ #1347 and represent either genuinely new findings or unreviewed groups from closed issue π Duplicate Resource ReviewΒ #1264.
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.
Potential Duplicates
Group 1: Azure Durable Functions C# vs Azure Functions C# β Near-Identical Descriptions β NEW
Guidelines and best practices for building Azure Functions in C# using the isolated worker model
Why flagged: Descriptions are 90%+ identical (Jaccard similarity). Both apply to the same file patterns (**/*.cs, **/host.json, **/*.csproj). While Durable Functions is a distinct Azure Functions extension for stateful workflows, the structural overlap is significant enough to warrant a review β particularly since azure-functions-typescript.instructions.md exists as a third companion, but there is no azure-durable-functions-typescript.instructions.md.
Group 2: C#/.NET Janitor vs .NET Upgrade β Word-for-Word Identical Descriptions (previously flagged β see #1264)
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.
Why flagged: Both agents share a word-for-word identical description. Body content reveals csharp-dotnet-janitor focuses on code cleanup, while dotnet-upgrade targets .NET Framework migration β but with identical descriptions users have no way to distinguish them. One may be a renamed duplicate or the descriptions need to be updated to reflect distinct purposes.
Group 3: PRD Agent + Skill β Same Name, Same Core Purpose (previously flagged β see #1264)
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: Both share the same name (prd) and the same core purpose β generating PRD documents with user stories, acceptance criteria, and technical specs. Cross-type overlap where one may make the other redundant.
Group 4: Markdown Accessibility β Agent + Instruction (previously flagged β see #1264)
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
Markdown accessibility guidelines based on GitHub's 5 best practices for inclusive documentation
Why flagged: Both explicitly reference the same source material (GitHub's 5 best practices for markdown accessibility) and serve the same purpose β improving markdown accessibility. Strong cross-type overlap.
Group 5: Context7 β Agent + Instruction (previously flagged β see #1264)
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
instructions/context7.instructions.md
Instruction
Use Context7 for authoritative external docs and API references when local context is insufficient
Why flagged: Both exist to integrate Context7 MCP documentation into Copilot. The agent provides an active expert assistant; the instruction passively directs Copilot to use Context7. Very similar scope with cross-type overlap.
Group 6: Gilfoyle Code Review β Agent + Instruction (previously flagged β see #1264)
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: Both implement the same Gilfoyle persona for code review with the same sardonic/elitist style. The agent performs active review sessions; the instruction passively applies the Gilfoyle style. Identical persona and domain β classic cross-type duplication.
Group 7: MS-SQL DBA β Agent + Instruction (previously flagged β see #1264)
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 describes customizing behavior "when the ms-sql-dba.agent.md chat mode is active" β making it a tightly coupled companion with heavily overlapping content. This is a different dimension than the agent-to-agent overlap (PostgreSQL vs MS-SQL) already tracked in #1347 Group 10.
Group 8: Agent Governance + Safety β Agent + Instruction (previously flagged β see #1264)
Reviewed β these are intentionally separate
Resource
Type
Description
agents/agent-governance-reviewer.agent.md
Agent
AI agent governance expert that reviews code for safety issues, missing governance controls, and helps implement policy enforcement, trust scoring, and audit trails in agent systems.
instructions/agent-safety.instructions.md
Instruction
Guidelines for building safe, governed AI agent systems. Apply when writing code that uses agent frameworks, tool-calling LLMs, or multi-agent orchestration to ensure proper safety boundaries, policy enforcement, and auditability.
Why flagged: Both target AI agent safety, governance, and policy enforcement. The agent performs active governance reviews; the instruction passively enforces the same principles. Overlapping domain and identical audience.
Group 9: GitHub Actions Expert + Instruction (previously flagged β see #1264)
Reviewed β these are intentionally separate
Resource
Type
Description
agents/github-actions-expert.agent.md
Agent
GitHub Actions specialist focused on secure CI/CD workflows, action pinning, OIDC authentication, permissions least privilege, and supply-chain security
Comprehensive guide for building robust, secure, and efficient CI/CD pipelines using GitHub Actions.
Why flagged: Both cover GitHub Actions CI/CD best practices including security hardening. The instruction codifies what the agent would advise, making this a cross-type duplication of the same domain knowledge.
Group 10: Bicep Plan/Implement vs Terraform Azure Plan/Implement β Two Parallel Pairs (previously flagged β see #1264)
Reviewed β these are intentionally separate
Resource
Type
Description
agents/bicep-plan.agent.md
Agent
Act as implementation planner for your Azure Bicep Infrastructure as Code task.
agents/bicep-implement.agent.md
Agent
Act as an Azure Bicep Infrastructure as Code coding specialist that creates Bicep templates.
agents/terraform-azure-planning.agent.md
Agent
Act as implementation planner for your Azure Terraform Infrastructure as Code task.
agents/terraform-azure-implement.agent.md
Agent
Act as an Azure Terraform Infrastructure as Code coding specialist that creates and reviews Terraform for Azure resources.
Why flagged: Two structurally identical plan/implement pairs β one for Bicep, one for Terraform. bicep-plan and terraform-azure-planning have near-identical descriptions (only tool name differs); same for the implement pair. Cross-tool duplication within the same agent-pair pattern.
Groups 11β20 (additional duplicate candidates)
Group 11: Playwright Browser Testing β Two Agents (previously flagged β see #1264)
Why flagged: Both agents target Playwright-based browser/E2E testing. gem-browser-tester is broader (also adds UI/UX validation and visual regression), but both are primarily Playwright test agents with significantly overlapping scope.
Group 12: Prompt Engineering β Two Agents + Skill (previously flagged β see #1264)
Reviewed β these are intentionally separate
Resource
Type
Description
agents/prompt-builder.agent.md
Agent
Expert prompt engineering and validation system for creating high-quality prompts
agents/prompt-engineer.agent.md
Agent
A specialized chat mode for analyzing and improving prompts. Every user input is treated as a prompt to be improved.
skills/prompt-builder/SKILL.md
Skill
Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices.
Why flagged:prompt-builder agent and prompt-builder skill share the same name and purpose. prompt-engineer describes the same core workflow (analyzing/improving prompts). All three resources target prompt creation and improvement with only minor framing differences.
Group 13: Implementation Plan Generation Agents β Four Agents with Identical/Near-Identical Descriptions (previously flagged β see #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.
agents/plan.agent.md
Agent
Strategic planning and architecture assistant focused on thoughtful analysis before implementation.
agents/task-planner.agent.md
Agent
Task planner for creating actionable implementation plans
Why flagged:planner.agent.md and implementation-plan.agent.md share a word-for-word identical description. All four agents create implementation plans for code changes with heavily overlapping scope. Note: the related skill-level cross-type overlap is tracked in #1347 Group 5 β this flags the agent-to-agent redundancy specifically.
Group 14: Suggest Awesome Copilot Resources β Three Near-Identical Skills (previously flagged β see #1264)
Suggest relevant GitHub Copilot skills from the awesome-copilot repository based on current repository context and chat history
Why flagged: Three skills with near-identical structure and wording β differing only in which resource type they recommend (agents vs instructions vs skills). Could potentially be a single parameterized skill, or the three might be intentionally granular.
Group 15: Mentor + Mentoring Juniors β Agent + Agent + Skill (previously flagged β see #1264)
Reviewed β these are intentionally separate
Resource
Type
Description
agents/mentor.agent.md
Agent
Help mentor the engineer by providing guidance and support.
agents/mentoring-juniors.agent.md
Agent
Socratic mentor for junior developers. Guides through questions, never gives direct answers.
skills/mentoring-juniors/SKILL.md
Skill
Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers.
Why flagged:mentoring-juniors.agent.md and skills/mentoring-juniors appear to package identical content as both an agent and a skill (same name, same Socratic framing). mentor.agent.md overlaps in domain (engineering guidance/mentoring), though it targets a broader audience.
Group 16: Technical Documentation Writing β Two Agents + Skill (previously flagged β see #1264)
Reviewed β these are intentionally separate
Resource
Type
Description
agents/se-technical-writer.agent.md
Agent
Technical writing specialist for creating developer documentation, technical blogs, tutorials, and educational content
agents/gem-documentation-writer.agent.md
Agent
Generates technical documentation, README files, API docs, diagrams, and walkthroughs.
skills/documentation-writer/SKILL.md
Skill
DiΓ‘taxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation.
Why flagged: All three target technical documentation creation for software projects. The two agents and the skill cover the same core workflow (writing technical docs, READMEs, API docs), though the skill applies the DiΓ‘taxis framework as a differentiator.
Group 17: Security Code Review β Three Overlapping Agents (previously flagged β see #1264)
Reviewed β these are intentionally separate
Resource
Type
Description
agents/se-security-reviewer.agent.md
Agent
Security-focused code review specialist with OWASP Top 10, Zero Trust, LLM security, and enterprise security standards
agents/wg-code-sentinel.agent.md
Agent
Ask WG Code Sentinel to review your code for security issues.
Why flagged: Three agents all performing security-focused code review with OWASP coverage. gem-reviewer is broader (adds PRD compliance), and wg-code-sentinel has a distinct persona, but the core security review function overlaps significantly across all three.
Group 18: Linux Expert Agents + Instructions β CentOS, Debian, Fedora Pairs (previously flagged β see #1264; Arch Linux covered in #1347 Group 12)
Reviewed β these are intentionally separate
Resource
Type
Description
agents/centos-linux-expert.agent.md
Agent
CentOS (Stream/Legacy) Linux specialist focused on RHEL-compatible administration, yum/dnf workflows, and enterprise hardening.
instructions/centos-linux.instructions.md
Instruction
Guidance for CentOS administration, RHEL-compatible tooling, and SELinux-aware operations.
agents/debian-linux-expert.agent.md
Agent
Debian Linux specialist focused on stable system administration, apt-based package management, and Debian policy-aligned practices.
instructions/debian-linux.instructions.md
Instruction
Guidance for Debian-based Linux administration, apt workflows, and Debian policy conventions.
agents/fedora-linux-expert.agent.md
Agent
Fedora (Red Hat family) Linux specialist focused on dnf, SELinux, and modern systemd-based workflows.
instructions/fedora-linux.instructions.md
Instruction
Guidance for Fedora (Red Hat family) systems, dnf workflows, SELinux, and modern systemd practices.
Why flagged: Each Linux distribution has both a dedicated expert agent and a near-identical instruction with overlapping scope. Three parallel cross-type pairs creating potential redundancy. Note: the Arch Linux version of this pattern (which also has a triage skill) is tracked separately in #1347 Group 12.
Group 19: Power BI Cluster β Agents + Instructions + Skills (previously flagged β see #1264)
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.
Why flagged: Multiple parallel triplets (agent + instruction + skill) covering the same Power BI sub-domains β data modeling, DAX, performance, and report design. Within each sub-domain the three resource types may serve overlapping purposes. Additionally, skills/powerbi-modeling overlaps with skills/power-bi-model-design-review within the data modeling sub-domain.
Group 20: Dataverse Python β Large Instruction + Skill Cluster (previously flagged β see #1264)
Generate production code for Dataverse SDK using advanced patterns, error handling, and optimization techniques.
skills/dataverse-python-usecase-builder/SKILL.md
Skill
Generate complete solutions for specific Dataverse SDK use cases with architecture recommendations
Why flagged: 14 instructions + 4 skills all targeting the Microsoft Dataverse SDK for Python. dataverse-python.instructions.md (Getting Started) and dataverse-python-sdk.instructions.md (Official Quickstart) overlap in scope with dataverse-python-quickstart skill. dataverse-python-best-practices overlaps with dataverse-python-production-code skill. The instructions appear intentionally split for selective import β but the cross-type overlap with skills warrants review.
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.
Potential Duplicates
Group 1: Azure Durable Functions C# vs Azure Functions C# β Near-Identical Descriptions β NEW
instructions/azure-durable-functions-csharp.instructions.mdinstructions/azure-functions-csharp.instructions.mdWhy flagged: Descriptions are 90%+ identical (Jaccard similarity). Both apply to the same file patterns (
**/*.cs, **/host.json, **/*.csproj). While Durable Functions is a distinct Azure Functions extension for stateful workflows, the structural overlap is significant enough to warrant a review β particularly sinceazure-functions-typescript.instructions.mdexists as a third companion, but there is noazure-durable-functions-typescript.instructions.md.Group 2: C#/.NET Janitor vs .NET Upgrade β Word-for-Word Identical Descriptions (previously flagged β see #1264)
agents/csharp-dotnet-janitor.agent.mdagents/dotnet-upgrade.agent.mdWhy flagged: Both agents share a word-for-word identical description. Body content reveals
csharp-dotnet-janitorfocuses on code cleanup, whiledotnet-upgradetargets .NET Framework migration β but with identical descriptions users have no way to distinguish them. One may be a renamed duplicate or the descriptions need to be updated to reflect distinct purposes.Group 3: PRD Agent + Skill β Same Name, Same Core Purpose (previously flagged β see #1264)
agents/prd.agent.mdskills/prd/SKILL.mdWhy flagged: Both share the same name (
prd) and the same core purpose β generating PRD documents with user stories, acceptance criteria, and technical specs. Cross-type overlap where one may make the other redundant.Group 4: Markdown Accessibility β Agent + Instruction (previously flagged β see #1264)
agents/markdown-accessibility-assistant.agent.mdinstructions/markdown-accessibility.instructions.mdWhy flagged: Both explicitly reference the same source material (GitHub's 5 best practices for markdown accessibility) and serve the same purpose β improving markdown accessibility. Strong cross-type overlap.
Group 5: Context7 β Agent + Instruction (previously flagged β see #1264)
agents/context7.agent.mdinstructions/context7.instructions.mdWhy flagged: Both exist to integrate Context7 MCP documentation into Copilot. The agent provides an active expert assistant; the instruction passively directs Copilot to use Context7. Very similar scope with cross-type overlap.
Group 6: Gilfoyle Code Review β Agent + Instruction (previously flagged β see #1264)
agents/gilfoyle.agent.mdinstructions/gilfoyle-code-review.instructions.mdWhy flagged: Both implement the same Gilfoyle persona for code review with the same sardonic/elitist style. The agent performs active review sessions; the instruction passively applies the Gilfoyle style. Identical persona and domain β classic cross-type duplication.
Group 7: MS-SQL DBA β Agent + Instruction (previously flagged β see #1264)
agents/ms-sql-dba.agent.mdinstructions/ms-sql-dba.instructions.mdWhy flagged: The instruction explicitly describes customizing behavior "when the
ms-sql-dba.agent.mdchat mode is active" β making it a tightly coupled companion with heavily overlapping content. This is a different dimension than the agent-to-agent overlap (PostgreSQL vs MS-SQL) already tracked in #1347 Group 10.Group 8: Agent Governance + Safety β Agent + Instruction (previously flagged β see #1264)
agents/agent-governance-reviewer.agent.mdinstructions/agent-safety.instructions.mdWhy flagged: Both target AI agent safety, governance, and policy enforcement. The agent performs active governance reviews; the instruction passively enforces the same principles. Overlapping domain and identical audience.
Group 9: GitHub Actions Expert + Instruction (previously flagged β see #1264)
agents/github-actions-expert.agent.mdinstructions/github-actions-ci-cd-best-practices.instructions.mdWhy flagged: Both cover GitHub Actions CI/CD best practices including security hardening. The instruction codifies what the agent would advise, making this a cross-type duplication of the same domain knowledge.
Group 10: Bicep Plan/Implement vs Terraform Azure Plan/Implement β Two Parallel Pairs (previously flagged β see #1264)
agents/bicep-plan.agent.mdagents/bicep-implement.agent.mdagents/terraform-azure-planning.agent.mdagents/terraform-azure-implement.agent.mdWhy flagged: Two structurally identical plan/implement pairs β one for Bicep, one for Terraform.
bicep-planandterraform-azure-planninghave near-identical descriptions (only tool name differs); same for the implement pair. Cross-tool duplication within the same agent-pair pattern.Groups 11β20 (additional duplicate candidates)
Group 11: Playwright Browser Testing β Two Agents (previously flagged β see #1264)
agents/playwright-tester.agent.mdagents/gem-browser-tester.agent.mdWhy flagged: Both agents target Playwright-based browser/E2E testing.
gem-browser-testeris broader (also adds UI/UX validation and visual regression), but both are primarily Playwright test agents with significantly overlapping scope.Group 12: Prompt Engineering β Two Agents + Skill (previously flagged β see #1264)
agents/prompt-builder.agent.mdagents/prompt-engineer.agent.mdskills/prompt-builder/SKILL.mdWhy flagged:
prompt-builderagent andprompt-builderskill share the same name and purpose.prompt-engineerdescribes the same core workflow (analyzing/improving prompts). All three resources target prompt creation and improvement with only minor framing differences.Group 13: Implementation Plan Generation Agents β Four Agents with Identical/Near-Identical Descriptions (previously flagged β see #1264)
agents/planner.agent.mdagents/implementation-plan.agent.mdagents/plan.agent.mdagents/task-planner.agent.mdWhy flagged:
planner.agent.mdandimplementation-plan.agent.mdshare a word-for-word identical description. All four agents create implementation plans for code changes with heavily overlapping scope. Note: the related skill-level cross-type overlap is tracked in #1347 Group 5 β this flags the agent-to-agent redundancy specifically.Group 14: Suggest Awesome Copilot Resources β Three Near-Identical Skills (previously flagged β see #1264)
skills/suggest-awesome-github-copilot-agents/SKILL.mdskills/suggest-awesome-github-copilot-instructions/SKILL.mdskills/suggest-awesome-github-copilot-skills/SKILL.mdWhy flagged: Three skills with near-identical structure and wording β differing only in which resource type they recommend (agents vs instructions vs skills). Could potentially be a single parameterized skill, or the three might be intentionally granular.
Group 15: Mentor + Mentoring Juniors β Agent + Agent + Skill (previously flagged β see #1264)
agents/mentor.agent.mdagents/mentoring-juniors.agent.mdskills/mentoring-juniors/SKILL.mdWhy flagged:
mentoring-juniors.agent.mdandskills/mentoring-juniorsappear to package identical content as both an agent and a skill (same name, same Socratic framing).mentor.agent.mdoverlaps in domain (engineering guidance/mentoring), though it targets a broader audience.Group 16: Technical Documentation Writing β Two Agents + Skill (previously flagged β see #1264)
agents/se-technical-writer.agent.mdagents/gem-documentation-writer.agent.mdskills/documentation-writer/SKILL.mdWhy flagged: All three target technical documentation creation for software projects. The two agents and the skill cover the same core workflow (writing technical docs, READMEs, API docs), though the skill applies the DiΓ‘taxis framework as a differentiator.
Group 17: Security Code Review β Three Overlapping Agents (previously flagged β see #1264)
agents/se-security-reviewer.agent.mdagents/wg-code-sentinel.agent.mdagents/gem-reviewer.agent.mdWhy flagged: Three agents all performing security-focused code review with OWASP coverage.
gem-revieweris broader (adds PRD compliance), andwg-code-sentinelhas a distinct persona, but the core security review function overlaps significantly across all three.Group 18: Linux Expert Agents + Instructions β CentOS, Debian, Fedora Pairs (previously flagged β see #1264; Arch Linux covered in #1347 Group 12)
agents/centos-linux-expert.agent.mdinstructions/centos-linux.instructions.mdagents/debian-linux-expert.agent.mdinstructions/debian-linux.instructions.mdagents/fedora-linux-expert.agent.mdinstructions/fedora-linux.instructions.mdWhy flagged: Each Linux distribution has both a dedicated expert agent and a near-identical instruction with overlapping scope. Three parallel cross-type pairs creating potential redundancy. Note: the Arch Linux version of this pattern (which also has a triage skill) is tracked separately in #1347 Group 12.
Group 19: Power BI Cluster β Agents + Instructions + Skills (previously flagged β see #1264)
agents/power-bi-data-modeling-expert.agent.mdinstructions/power-bi-data-modeling-best-practices.instructions.mdskills/power-bi-model-design-review/SKILL.mdskills/powerbi-modeling/SKILL.mdagents/power-bi-dax-expert.agent.mdinstructions/power-bi-dax-best-practices.instructions.mdskills/power-bi-dax-optimization/SKILL.mdagents/power-bi-performance-expert.agent.mdskills/power-bi-performance-troubleshooting/SKILL.mdagents/power-bi-visualization-expert.agent.mdinstructions/power-bi-report-design-best-practices.instructions.mdskills/power-bi-report-design-consultation/SKILL.mdWhy flagged: Multiple parallel triplets (agent + instruction + skill) covering the same Power BI sub-domains β data modeling, DAX, performance, and report design. Within each sub-domain the three resource types may serve overlapping purposes. Additionally,
skills/powerbi-modelingoverlaps withskills/power-bi-model-design-reviewwithin the data modeling sub-domain.Group 20: Dataverse Python β Large Instruction + Skill Cluster (previously flagged β see #1264)
instructions/dataverse-python.instructions.mdinstructions/dataverse-python-sdk.instructions.mdinstructions/dataverse-python-best-practices.instructions.mdinstructions/dataverse-python-error-handling.instructions.mdinstructions/dataverse-python-authentication-security.instructions.mdinstructions/dataverse-python-performance-optimization.instructions.mdinstructions/dataverse-python-advanced-features.instructions.mdinstructions/dataverse-python-modules.instructions.mdinstructions/dataverse-python-pandas-integration.instructions.mdinstructions/dataverse-python-testing-debugging.instructions.mdinstructions/dataverse-python-file-operations.instructions.mdinstructions/dataverse-python-real-world-usecases.instructions.mdinstructions/dataverse-python-agentic-workflows.instructions.mdinstructions/dataverse-python-api-reference.instructions.mdskills/dataverse-python-quickstart/SKILL.mdskills/dataverse-python-production-code/SKILL.mdskills/dataverse-python-advanced-patterns/SKILL.mdskills/dataverse-python-usecase-builder/SKILL.mdWhy flagged: 14 instructions + 4 skills all targeting the Microsoft Dataverse SDK for Python.
dataverse-python.instructions.md(Getting Started) anddataverse-python-sdk.instructions.md(Official Quickstart) overlap in scope withdataverse-python-quickstartskill.dataverse-python-best-practicesoverlaps withdataverse-python-production-codeskill. The instructions appear intentionally split for selective import β but the cross-type overlap with skills warrants review.Note
π Integrity filter blocked 1 item
The following item were blocked because they don't meet the GitHub integrity level.
issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: