skills.rest
endorlabs
endorlabsOFFICIAL
Explore all skills by this author →
Website𝕏@EndorLabsGitHub

endor-namespace-relationship-map

Map consumer-to-producer project relationships across a namespace using package version and dependency metadata.

4|Updated Oct 18, 2025
Search Tags:#dependencies#namespace#blast radius#project map#relationship graph#package coordinates
One-click install
npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-namespace-relationship-map
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: endor-namespace-relationship-map
Source: https://github.com/endorlabs/endorlabs-sdk/tree/main/agent-knowledge/skills/endor-namespace-relationship-map
Command: npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-namespace-relationship-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand which projects in a namespace consume packages produced by a specific repository, so you can assess change impact before shipping breaking updates.

Core Features & Use Cases

  • Namespace-wide relationship mapping: Builds consumer-to-producer edges across projects linked by package coordinates.
  • Blast radius analysis: Focuses on one producer project to see which downstream repositories may be affected by a change.
  • Operational graph outputs: Produces JSON artifacts for relationship graphs, paths, and summary stats that can feed workflows and reviews.

Quick Start

Ask the assistant to map namespace relationships for a chosen producer project UUID and summarize the downstream consumers.

Frequently Asked Questions about endor-namespace-relationship-map

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

FAQPage Schema
How do I map blast radius for breaking changes across a namespace?▼

To map blast radius for breaking changes, this Skill traverses consumer-to-producer project relationships within a namespace using package version and dependency metadata, outputting JSON graphs of affected downstream repositories.

What is a namespace relationship graph and when do I need one?▼

A namespace relationship graph maps consumer-to-producer dependencies across projects using package coordinates. You need one for breaking-change impact analysis and downstream dependency discovery before shipping updates.

How do I discover downstream consumers of a specific producer project?▼

You can discover downstream consumers by providing a producer project UUID for optional filtering. The Skill performs namespace-scoped traversal to identify and map all dependent repositories via package coordinates.

Does this dependency mapping tool work for single-repository SBOM review?▼

No, this dependency mapping tool does not work for single-repository SBOM review. It applies to full namespace graph inspection, breaking-change impact analysis, and downstream dependency discovery across multiple projects.

Can I get JSON outputs for dependency paths and statistics from the relationship graph?▼

Yes, you can get JSON outputs for dependency paths and statistics. The Skill generates operational graph artifacts containing relationship edges, paths, and summary stats to feed directly into your workflows and reviews.

Related Skills

Explore More Software Engineering Skills→
cdrgurucdrguru
1

gemini-cli-init

Initialize Gemini CLI configuration and auditor persona for the PACK workflow.

Community
Intermediate
XSpoonAiXSpoonAi
17

api-contract-diff

Compare OpenAPI and GraphQL schemas to produce categorized JSON diffs.

Official
Advanced
TheBushidoCollectiveTheBushidoCollective
187

maven-dependency-management

Resolve Maven dependency conflicts and optimize dependency trees in Java projects.

Official
Advanced
devCharuzudevCharuzu

pr-review-expert

Analyze pull requests for quality, security, and breaking changes.

Community
Advanced