agentsclimarketplace

Workflow coordination

Skill YuanshengClaw/yuansheng-kit/plugins/craft/skills/workflow-coordination

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 workflow-coordination

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

Coordinate an exact Yuansheng Craft workflow without bypassing phase ownership, trusted identity, immutable evidence, or fail-closed guards.

SKILL.md

1.4 KB, as published. Nobody here has run it

Coordinate a Yuansheng Craft Workflow

  1. Use only the workflow entry explicitly selected by the user.
  2. Treat the platform-provided principal as authoritative. Never infer identity from a phase or accept a model-provided identity claim.
  3. Read status and invoke lifecycle tools only for an exact workflow ID.
  4. Delegate each active phase to the owner reported by the workflow state.
  5. Require the owner to record its immutable evidence before requesting its allowed transition.
  6. Preserve stale evidence and blocked remediation; never make old evidence active by changing only the phase.
  7. Stop when a guard, authorization, artifact, Store check, or required implementation is unavailable.
  8. Never create a commit, push, reset, stash, rebase, clean a worktree, synchronize a remote, or perform an unplanned file operation.

Terminal Behavior

  • active: hand off only to the current phase owner.
  • blocked: report the exact reason and remediation, then stop until explicit resume or remediation.
  • completed: report the stored delivery and stop permanently.
  • Unknown ID, missing store anchor, stale session, or ambiguous active workflow: do not guess or mutate anything.

Keep looking

Skills are one crate of 328,083. 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.