Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →withkynam/vc-validate-findings
Use when running VALIDATE V2-V3 fan-out. Two-layer investigation (4 dimension agents + per-section feasibility agents) synthesized into PASS/CONDITIONAL/BLOCKED net gate. Strategy-agnostic.
Passed 16 of 21 test cases with the skill, and 6 of 21 without it.
and 14 more in the full report
11 fixed6 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the Section I findings table, how should passing dimensions with no findings or concerns be represented in the proposed fix column?
| Checked | Without skill | With skill |
|---|---|---|
| Formats passing dimension status as a checkmark PASS symbol. | Missed | Passed |
| Uses an em-dash in the proposed fix column for passing findings. | Missed | Passed |
The instructions your model reads when the skill loads.
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Defines the role specs, prompts, and output schemas for the two-layer VALIDATE fan-out (a parallel check across 4 dimensions + per-section feasibility probes). Produces a net gate verdict (PASS / CONDITIONAL / BLOCKED) and all the inputs needed to write the validate-contract — the written checklist that gates EXECUTE.
references/example-validate-output.md — full V4 menu + validate-contract template; calibrate output format against this filevc-validate-agent after V1 pre-check passesThis skill is STRATEGY-AGNOSTIC. It defines the role specs, prompts, and output schemas for each dimension/section agent. It does NOT determine how those agents are executed (Workflow vs parallel Agent tool vs vc-team).
The execution method is determined by vc-agent-strategy-compare, which must be invoked BEFORE vc-validate-findings is called. vc-validate-findings outputs agent role definitions; the caller executes them using the recommended strategy.
Choose before spawning any agents. Pass the selected mode to all Layer 1 and Layer 2 agents in their prompt context.
Runs the Layer 1 + Layer 2 fan-out using context available in the current conversation. Validation agents derive context from the plan file and what was passed in the prompt.
Appropriate when:
test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.