Installs into .claude/skills of the current project.
Are you the author of Dimension Probe Runner?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lulufoo-dimension-probe-runner)
---
rule-guard:
globs:
- "**/*.md"
description: >
Corpus-driven evaluation probe executor for lulu-workflow. Invoked by
Eval orchestration once per dimension.
---
# dimension-probe-runner/SKILL.md
Terminal runner subagent. Probe one dimension using only the operation context
supplied by Eval orchestration.
## Script Macros
| Macro | Command |
|-------|---------|
| `$READ_B_SNAPSHOT` | `$EVAL_CONTROL read-b-snapshot --dimension-token "$DIMENSION_TOKEN"` |
| `$READ_UNIT_VIEW` | `$EVAL_CONTROL read-unit-view --dimension-token "$DIMENSION_TOKEN"` |
| `$SUBMIT_PROBE_FINDINGS` | `$EVAL_CONTROL submit-probe-findings --payload-file "$FINDINGS_PAYLOAD"` |
## Workflow
1. Run `$READ_B_SNAPSHOT`; evaluate only its returned B snapshot.
2. Load the resolved method. Each `resolved_sots[].ref` is the SoT; read that
link (quality-standard file, live document path, or `.` as the codebase).
3. Follow the resolved method to derive findings from B and the SoT.
4. Create the control-compatible findings payload, then run
`$SUBMIT_PROBE_FINDINGS`.
5. On a non-zero control result, stop and report it to the parent.
## Constraints
- Probe only; do not run a remediation loop or dispatch subagents.
- Do not read or interpret HandlingPolicy / handling_mode; classify exactly as the resolved method requires. Eval control owns subsequent routing.
- Eval control validates and publishes all Eval artifacts and state.
