Verification source selection

Skill YuanshengClaw/yuansheng-kit/plugins/craft/skills/verification-source-selection

Agent-oriented toolkit for RISC-V optimization knowledge extraction, pattern mining, real-hardware performance analysis, root-cause diagnosis, and code generation

Install

npx -y skills add YuanshengClaw/yuansheng-kit --skill verification-source-selection

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Require an explicit official or user-provided verification source for the active Yuansheng Craft patch plan before creating and authorizing a candidate-specific verification manifest.

SKILL.md

2.3 KB, as published. Nobody here has run it

Select Yuansheng Craft Verification Evidence

Use this skill after a PatchCandidate is ready and before any verification command runs. Source selection is a hard workflow gate, not advisory text.

Selection Protocol

Read exact workflow status and confirm the active phase is verifying.
Ask the user to choose exactly one source:
- official: tests maintained by the bound product repository;
- user-provided: a concrete test path or command proposal supplied by the user.
For official, require a ready RepositoryBinding, inspect only the bound product tree, and identify concrete repository-relative tests covering the patch-plan criteria.
For user-provided, require a concrete path or named command proposal. Reject vague descriptions, Store paths, paths outside the bound product, and commands not represented as argv.
Call ys_craft_prepare_verification with the exact selected source. Treat the returned VerificationSource as immutable.
Build one candidate-specific VerificationManifest from that source. It must bind the candidate, every required local or SSH runner group, exact argv, cwd, environment allowlist, timeout, criterion mapping, and log target.
Show the entire manifest for one explicit authorization. Run only the exact authorized manifest through ys_craft_run_verification.

Iteration Rules

Preserve the selected source while the active PatchPlan is unchanged.
Generate a new manifest and authorization for every candidate revision.
If the plan or source changes, repeat selection instead of editing an existing source or manifest.
On candidate failure, preserve criterion evidence, return to building, and wait for a new candidate. Never reset the worktree.
On source, manifest, authorization, runner, or candidate mismatch, stop before executing any command.

Done Criteria

Exactly one explicit source is active for the current plan.
The immutable manifest binds the exact candidate and selected source.
Every required criterion has its own evidence mapping.
Execution uses the authorized manifest unchanged.