Agent skill · Data & Analytics

lineage-analysis

Trace relationships between semantic models and downstream reports across Fabric workspaces. Automatically invoke when the user asks to "find downstream reports", "show report lineage", "impact analysis", "what depends on this dataset", "cross-workspace lineage", "which reports are connected", "get model dependencies", or mentions model-to-report dependency tracing.

data-goblingithub.com/data-goblinGitHub ↗
claude-codecopilotships scriptsGPL-3.0
Install
npx skills add data-goblin/power-bi-agentic-development --skill lineage-analysis --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: yes
Path: plugins/semantic-models/skills/lineage-analysis/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 833
Language: C#

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Lineage Analysis Trace downstream dependencies from a semantic model to all connected reports across the tenant. No admin permissions required -- workspace contributor access is sufficient. ## When to Use - Before modifying or deleting a semantic model, to understand impact - Auditing which reports are connected to a model and where they live - Identifying orphaned or test reports connected to production models - Cross-workspace dependency mapping ## Downstream Reports Run `scripts/get-downstream-reports.py` to find all reports bound to a semantic model. ```bash # By workspace and model name python3 scripts/get-downstream-reports.py "Workspace Name" "Model Name" # By dataset GUID directly python3 scripts/get-downstream-reports.py --dataset-id <guid> # JSON output for further processing python3 scripts/get-downstream-reports.py "Workspace" "Model" --json ``` **Requirements:** `azure-identity`, `requests` (`pip install azure-identity requests`). Authenticated via `DefaultAzureCredential` (works with `az login`, managed identity, or environment variables). **How it works:** Lists all workspaces the user can access, then queries each workspace's reports in parallel (8 workers) checki

What's inside
Steps it walks through
  1. When to Use
  2. Downstream Reports
  3. Limitations
  4. Interpreting Results
  5. Related Skills
Ships with 1 file
  • scripts/get-downstream-reports.py
Commands it runs
By workspace and model name
python3 scripts/get-downstream-reports.py "Workspace Name" "Model Name"
By dataset GUID directly
python3 scripts/get-downstream-reports.py --dataset-id <guid>
JSON output for further processing
python3 scripts/get-downstream-reports.py "Workspace" "Model" --json
More from power-bi-agentic-development
All skills →
About this skill
What does the lineage-analysis skill do?

Trace relationships between semantic models and downstream reports across Fabric workspaces. Automatically invoke when the user asks to "find downstream reports", "show report lineage", "impact analysis", "what depends on this dataset", "cross-workspace lineage", "which reports are connected", "get model dependencies", or mentions model-to-report dependency tracing.

How do I install it?

Run `npx skills add data-goblin/power-bi-agentic-development --skill lineage-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From data-goblin/power-bi-agentic-development, a repository with 833 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going