ClaudeSuperPower

databricks-notebook-analyzer

Subagent

Use this agent when the user has pointed at a single Databricks notebook (.ipynb / .py / .scala) and wants to know what it does, what it depends on, what risks the migrator will hit, and which gotchas (from references/gotchas.md) will apply. Run before manually authoring an entry in a migration mani

When Claude delegates to this

  • Use this agent when the user has pointed at a single Databricks notebook (.ipynb / .py / .scala) and wants to know what it does, what it depends on, what risks the migrator will hit, and which gotchas (from references/gotchas.md) will apply.

What it does

Run before manually authoring an entry in a migration manifest, OR as a one-off "should we migrate this?" assessment. Returns a structured report (markdown), does not modify the notebook.

Model unspecified

No model pin — runs on your session's model.

Default effort

No reasoning budget declared.

Separate context

Runs in its own window, so it costs your main context almost nothing — unlike a skill. Scoped to 4 tools.

Its system prompt

93 lines

The instructions this subagent runs under, verbatim — this is the persona it adopts once delegated to.

Shipped by 1 plugin

Installing any of these installs this subagent.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Run shell commands

Declares Bash

~107 tokens of context used while enabled, before you invoke anything

All declared tools (4)
BashGlobGrepRead

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just subagents.