inspector-operations

Inspect 3Lens entities to reveal identity, dependencies, cost attribution, and lifecycle changes.

Updated Jul 29, 2025

Search Tags:#debugging #dependencies #query #entity #inspect #cost-attribution

Ready to run

npx skills add https://github.com/adriandarian/3Lens --skill inspector-operations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: inspector-operations
Source: https://github.com/adriandarian/3Lens/tree/main/.cursor/skills/inspector-operations
Command: npx skills add https://github.com/adriandarian/3Lens --skill inspector-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigate and inspect 3Lens entities including meshes, materials, textures, and shaders. Use when examining specific entities, understanding dependencies, tracing cost attribution, or selecting entities by query.

Core Features & Use Cases

Inspect an entity to reveal identity, dependencies, cost attribution, and lifecycle changes
Query-based selection: find entities by type, texture usage, or relationships
Trace attribution: render blame chains for expensive GPU hotspots
Dependency mapping: explore incoming and outgoing edges to understand impact
Use Case: root-cause analysis, dependency tracking, cost attribution, bulk selection

Quick Start

Inspect a specific entity by ID to view its identity, dependencies, and cost attribution.

Frequently Asked Questions about inspector-operations

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

FAQPage Schema

How do I inspect 3Lens entities to map dependencies and trace cost attribution?▼

Inspecting 3Lens entities reveals identity, dependency mapping, cost attribution with blame chains, and lifecycle changes. You query specific entities by ID or type to trace relationships across meshes, materials, textures, and shaders.

What is the best way to find meshes and textures by relationship or usage?▼

Finding meshes and textures by relationship uses query-based selection. You select entities by type, texture usage, or incoming and outgoing dependency edges to understand impact and perform bulk selections.

How does dependency mapping work for shaders and materials?▼

Dependency mapping for shaders and materials explores incoming and outgoing edges to understand impact. It traces attribution across entity relationships, enabling root-cause analysis for expensive GPU hotspots.

Can I trace render blame chains for expensive GPU hotspots?▼

Tracing render blame chains for expensive GPU hotspots is supported. Cost attribution maps expenses across entity dependencies, allowing you to pinpoint the root cause of rendering performance issues.

Does 3Lens entity inspection require any external dependencies?▼

3Lens entity inspection requires no external dependencies. You perform root-cause analysis, dependency tracking, and bulk selection via queries directly through the unified inspector workflow.

When do I need to query entity lifecycle changes across time?▼

Querying entity lifecycle changes across time is needed for root-cause analysis. Inspecting a specific entity by ID reveals its history, dependencies, and cost attribution to track shifting performance impacts.