agentsclimarketplace
Sign in

Write root cause blueprint

Skill YuanshengClaw/yuansheng-kit/plugins/trace/skills/write-root-cause-blueprint

Produce and semantically review evidence-grounded Yuansheng Root Cause Blueprint v1-lite candidates from validated perf evidence and a confirmed hardware profile. Use when Yuansheng Trace requests a per-function Blueprint candidate or an independent review of one.From its SKILL.md

Install
npx -y skills add YuanshengClaw/yuansheng-kit --skill write-root-cause-blueprint

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

2 things to look at

  • 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.
  • 4 stars4 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.

SKILL.md

1.5 KB, 273 tokens by cl100k_base, as published. Nobody here has run it

Write a Root Cause Blueprint

  1. Bind the candidate to the supplied software, test case, ranked function, and confirmed hardware profile.
  2. Use only the supplied perf statistics, annotate output, metadata, hardware profile, and their recorded hashes. Do not read source code or acquire new evidence.
  3. Distinguish observations from hypotheses. Copy measured values exactly and keep unsupported facts as null with the required machine-readable gap codes.
  4. Keep every rvv_pattern and pattern_confidence value null, and include pattern_catalog_unavailable. Do not name or infer a Pattern.
  5. Do not invent a source file, line, code location, metric, baseline, or hardware capability. Keep recommendations within what the evidence can support.
  6. Set needs_human_review to true and allow_auto_forward_to_ys_craft to false.
  7. Return strict JSON conforming to the supplied v1-lite Schema and preserve the workflow-requested claim-to-evidence references.

For semantic review, compare every material claim with the immutable candidate and supplied evidence. Report unsupported, conflicting, or uncited claims without modifying the candidate. Require a new candidate and full validation when correction is necessary.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.