How do I install the Polylith Workspace Inspection skill?

Run npx skillmds@latest add davidvujic/polylith-workspace-inspection in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Polylith Workspace Inspection safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Polylith Workspace Inspection?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Polylith Workspace Inspection free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Polylith Workspace Inspection?

davidvujic (@davidvujic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Polylith Workspace Inspection by davidvujic

Name: Polylith Workspace Inspection
Author: davidvujic

Polylith Workspace Inspection

Show **brick × project usage** with `poly info` — which projects use which bricks, plus workspace counts. Use for "workspace overview", "which projects use X", "find orphaned bricks". For brick-to-brick dependencies, use `polylith-dependency-visualization`.

davidvujic ef7141a 3.4 KB Updated Sep 17, 2026

File contents

Workspace Inspection Skill

Quick command

uv run poly info

Command prefix: If you do not know the package manager, list lock files with ls uv.lock poetry.lock pdm.lock 2>/dev/null (a pyproject.toml is always present, so it tells you nothing on its own). Use uv run poly (uv), poetry poly (poetry), pdm run poly (pdm), hatch run poly (hatch), or poly (activated venv). Examples below use uv run.

poly info vs poly deps:

poly info → brick × project (which project uses which brick).

poly deps → brick × brick (which brick uses which brick). Load polylith-dependency-visualization. 💡 A brick that is - in every project except development is orphaned in production — flag it for the user.

Command reference

Option	Default	Description
`--short`	`false`	Compact view — for workspaces where the full matrix doesn't fit.
`--save`	`false`	Persist the report to a file under the workspace's output dir.
`--group`	—	Show only projects in the named group(s) (comma-separated), defined in `[tool.polylith.projects.groups]`.

Examples

# Full matrix
uv run poly info

# Compact summary
uv run poly info --short

# Filter to a project group
uv run poly info --group hooks

Sample output

Workspace summary
projects: 6  components: 7  bases: 5  development: 1

  brick           consumer   message-api   aws lambda   fastapi   gcp fn   development
 ──────────────────────────────────────────────────────────────────────────────────────
  greeting           -            -             ✔          ✔        ✔          ✔
  kafka              ✔            ✔             -          -        -          ✔
  log                ✔            ✔             ✔          ✔        ✔          ✔
  greet_api          -            -             -          ✔        -          ✔
  message_api        -            ✔             -          -        -          ✔

Rows are bricks; columns are projects (rightmost = development).
✔ = the brick is used by that project; - = not used.
The development column should be ✔ for every brick (enforced by poly sync); a - there means a brick was created but isn't yet known to the development project.

Notes for the agent

poly info exits 0 — it's a report, not a gate.
For wide workspaces, prefer --short or --group <name>.
To turn this report into action: cross-reference orphans (only development = ✔) with poly deps --brick <name> to confirm nothing imports them, then propose deletion to the user.

---name: polylith-workspace-inspectiondescription: Show **brick × project usage** with `poly info` — which projects use which bricks, plus workspace counts. Use for "workspace overview", "which projects use X", "find orphaned bricks". For brick-to-brick dependencies, use `polylith-dependency-visualization`.---# Workspace Inspection Skill## Quick command```bashuv run poly info```**Command prefix:** If you do not know the package manager, list lock files with `ls uv.lock poetry.lock pdm.lock 2>/dev/null` (a `pyproject.toml` is always present, so it tells you nothing on its own). Use `uv run poly` (uv), `poetry poly` (poetry), `pdm run poly` (pdm), `hatch run poly` (hatch), or `poly` (activated venv). Examples below use `uv run`.> **`poly info` vs `poly deps`:**> - `poly info` → **brick × project** (which project uses which brick).> - `poly deps` → **brick × brick** (which brick uses which brick). Load `polylith-dependency-visualization`.> 💡 A brick that is `-` in every project except `development` is **orphaned in production** — flag it for the user.## Command reference| Option | Default | Description ||---------------|---------|-----------------------------------------------------------------------------------------------------------------|| `--short` | `false` | Compact view — for workspaces where the full matrix doesn't fit. || `--save` | `false` | Persist the report to a file under the workspace's output dir. || `--group` | — | Show only projects in the named group(s) (comma-separated), defined in `[tool.polylith.projects.groups]`. |## Examples```bash# Full matrixuv run poly info# Compact summaryuv run poly info --short# Filter to a project groupuv run poly info --group hooks```### Sample output```Workspace summaryprojects: 6 components: 7 bases: 5 development: 1 brick consumer message-api aws lambda fastapi gcp fn development ────────────────────────────────────────────────────────────────────────────────────── greeting - - ✔ ✔ ✔ ✔ kafka ✔ ✔ - - - ✔ log ✔ ✔ ✔ ✔ ✔ ✔ greet_api - - - ✔ - ✔ message_api - ✔ - - - ✔```- Rows are bricks; columns are projects (rightmost = development).- `✔` = the brick is used by that project; `-` = not used.- The `development` column should be `✔` for every brick (enforced by `poly sync`); a `-` there means a brick was created but isn't yet known to the development project.## Notes for the agent- `poly info` exits 0 — it's a report, not a gate.- For wide workspaces, prefer `--short` or `--group <name>`.- To turn this report into action: cross-reference orphans (only `development = ✔`) with `poly deps --brick <name>` to confirm nothing imports them, then propose deletion to the user.

Frequently asked questions