Menu
Use when auditing registered Miller workspaces for dangerous strings, deprecated APIs, compatibility markers, secrets-like terms, or other exact text across source, docs, logs, external files, and web imports.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use before changing existing indexed files with Miller edit, especially symbol rewrites, text replacements, renames, or refactors.
Use when an agent needs extractor-recognized code-shape facts such as routes, htmx attributes, Alpine directives, SQL DDL/DML, or data-document structure.
Use when starting a Miller task, choosing a Miller tool, or choosing a Miller search mode.
Use when tracing Miller bridge paths in supported providers: dotnet-web URL literals and fetch/axios client requests to ASP.NET signals, client requests to Next.js route handlers or Nuxt server routes, Next.js/Nuxt route references to file routes, Vue/React references to route definitions, or backend-http client requests to Express/FastAPI/Flask/Django/Spring/Go/gin/echo/Rails/NestJS/Laravel/Phoenix/axum/actix/Symfony/Ktor route facts.
Use when orienting on an unfamiliar code area with Miller, explaining a module, finding entry points, or gathering context before a change.
Use when assessing blast radius with Miller, choosing tests for a change, answering who uses a symbol, or planning a refactor.
| name | miller-text-audit |
| description | Use when auditing registered Miller workspaces for dangerous strings, deprecated APIs, compatibility markers, secrets-like terms, or other exact text across source, docs, logs, external files, and web imports. |
| user-invocable | true |
| arguments | <audit terms or term file> |
| allowed-tools | mcp__miller__content, mcp__miller__search, mcp__miller__workspace |
Use this workflow for token-efficient text audits. Prefer content-corpus search over raw grep because it returns ranked snippets, workspace identity, and bounded read coordinates.
miller workspace list
miller content search "dangerous phrase" --workspace-id all --kind source --limit 20 --json
miller content search "deprecated config key" --workspace-id all --kind config --limit 20 --json
miller content search "old docs phrase" --workspace-id all --kind docs --limit 20 --json
Use --kind external_file for imported logs/reports and --kind web for imported web markdown. Use search --mode all-text only when a broad one-workspace union query is more useful than a registered-workspace audit.
miller content read --source-id SOURCE_ID --line 120 --context-lines 8
Use the source_id from each content search hit or content list. When the hit came from
--workspace-id all, pass its workspace_id back to content read so Miller reads the right registered
workspace.
context unless the user asks for code context around a finding.--limit or switch kind only after the targeted query misses.content export only for integration feeds, not for interactive audit output.diagnostic_code/next_actions; follow those before falling back to shell search.--workspace-id all returns no rows, confirm workspaces are registered and content DBs are built before falling back to shell search.