mvt-check-context

Workspace context audits estimate token usage across project context, shared knowledge, and active artifacts using a chars-per-token heuristic. This identifies oversized files and stale artifacts consuming excessive prompt space before AI assistance degrades.

AI assistance slows down or becomes noisy when historical artifacts, oversized project context, or misplaced shared knowledge consume too much prompt space. Running a context size analysis identifies these heavy files and recommends cleanup.

The best way to estimate prompt token load is using a tool that applies per-category and per-skill accounting across multi-project setups. This detects duplicate content and missing knowledge references while classifying workspace health based on configurable thresholds.

To find duplicate content and missing knowledge references, run a workspace audit that performs per-category and per-skill accounting. This read-only analysis detects duplicate artifacts and missing references, then suggests the right follow-up skill for reorganization.

Yes, you can check MVTT workspace health across both single-project and multi-project setups. The analysis labels the workspace and major files as healthy, borderline, or oversized based on configurable thresholds to guide optimization.

Read-only workspace token optimization recommendations identify large files, stale context, and duplicate content, then suggest the right follow-up skill. They do not automatically delete or modify files; you must execute the cleanup manually.