endor-duplicate-projects

Identify duplicate Project registrations across tenant namespaces and output CSV reports.

4|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-duplicate-projects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: endor-duplicate-projects
Source: https://github.com/endorlabs/endorlabs-sdk/tree/main/agent-knowledge/skills/endor-duplicate-projects
Command: npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-duplicate-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires endorlabs, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you audit a tenant’s project inventory and identify likely duplicate Project registrations across namespaces, so you can clean up redundant entries and review naming collisions.

Core Features & Use Cases

  • Tenant-wide duplicate detection: Scans all projects, including child namespaces, and groups exact-name matches across different namespaces.
  • Optional canonical-name clustering: Supports token stripping for customer-specific naming conventions such as mirror, shadow, and clone to surface near-duplicates.
  • Audit-ready reporting: Produces a flat CSV with project metadata and a grouped canvas for review, while excluding SBOM-only projects and preserving source versus latest scan execution context.

Quick Start

Ask the skill to find tenant-wide duplicate projects and generate the standard CSV and grouped review canvas for the target tenant.

Frequently Asked Questions about endor-duplicate-projects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find duplicate project registrations across a tenant and child namespaces?

To find duplicate project registrations across a tenant, scan all projects including child namespaces and group exact-name matches. This process outputs a flat CSV with project metadata and a grouped canvas for review.

What is canonical-name clustering for project naming conventions?

Canonical-name clustering is a duplicate detection technique that applies token stripping for customer-specific naming conventions like mirror, shadow, and clone. It surfaces near-duplicate projects to help clean up redundant inventory entries.

How do I generate an audit-ready CSV export of duplicate projects?

Generate an audit-ready CSV export by running a tenant-wide duplicate detection scan that preserves source versus latest scan execution context. The output excludes SBOM-only projects and enriches each duplicate row with registration data.

Does the duplicate project detection exclude SBOM-only projects?

Yes, tenant-wide duplicate project detection excludes SBOM-only projects from the final audit results. The scan strictly focuses on registered projects and provides registration-versus-scan enrichment for each identified duplicate row.

Can I use token stripping to identify near-duplicate projects?

Yes, you can use optional canonical-name clustering with token stripping to identify near-duplicate projects. This handles customer-specific naming conventions such as mirror, shadow, and clone to surface matching project names across different namespaces.

What is the best way to audit a tenant's project inventory for naming collisions?

The best way to audit a tenant's project inventory for naming collisions is to perform a tenant-wide scan that groups exact-name matches across child namespaces. This generates a grouped review canvas and a detailed CSV export.