workflows

触发：当你面临的任务明显需要多个思想武器协作时调用；常见信号包括：从零启动新项目、攻坚复杂疑难问题、对已有方案进行迭代优化。此 skill 提供标准化的跨 skill 工作流组合，解决"应该先用哪个 skill、怎么衔接"的问题。 English: Trigger when a task clearly requires multiple skills in sequence. Use this skill to select a standard workflow that chains skills together, defines data handoff between steps, and specifies termination conditions.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable meta-skill whose core strength is workflow clarity — explicit sequencing, termination conditions, and recovery loops across three workflows. Weakest only in lacking a fully-worked end-to-end example and in modestly repetitive parallel structure.

Suggestions

Add one short worked example (a completed run filling in the templates) for the most common workflow to lift actionability from concrete-skeleton to fully-demonstrated.

Trim the decorative Mao epigraph and tighten the repeated step-detail scaffolding across the three workflows to improve token efficiency.

Consider extracting the per-step output-format templates into a short reference table so the three workflow sections share one canonical format definition instead of repeating it.

Dimension	Reasoning	Score
Conciseness	Efficient and well-organized with high-signal output templates; only minor trimmable fat — a decorative epigraph and the parallel, somewhat repetitive step-detail structure across three workflows.	4 / 5
Actionability	Provides concrete fill-in output templates, explicit per-step termination conditions, a workflow-selection table, and interruption handling; gaps only in that no fully-worked end-to-end example demonstrates a completed run.	4 / 5
Workflow Clarity	Each workflow is clearly sequenced (arrow diagrams + step-by-step) with explicit per-step termination conditions and explicit feedback/recovery loops (e.g., 假说被证伪 → 返回 contradiction-analysis), matching the anchor for clear sequence with validation and error-recovery loops.	5 / 5
Progressive Disclosure	Self-contained with no bundle files; content is well-sectioned under clear headers with a selection guide and cross-references between workflows. Stays at 4 rather than 5 because everything is inlined with no one-level-deep reference structure (acceptable for this skill but not the anchor-5 pattern).	4 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, bilingual description that clearly states both capability and trigger conditions with concrete signal phrases. It is specific and distinctive; the only minor gaps are absent workflow names and a few synonym trigger terms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "chains skills together, defines data handoff between steps, and specifies termination conditions" — but the actual named workflows are not surfaced in the description itself, leaving a minor coverage gap.	4 / 5
Completeness	Explicitly answers both what (select/chain workflows, define data handoff, specify termination) and when (explicit "触发/Trigger" clause with concrete signals), matching the anchor for clearly stated what-and-when with trigger phrases.	5 / 5
Trigger Term Quality	Provides a clear trigger ("Trigger when a task clearly requires multiple skills in sequence") plus natural signal phrases (新项目/MVP, 疑难 bug, 迭代优化); a few common synonyms or variants are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (cross-skill workflow orchestration) with distinct triggers; minor overlap risk only with the underlying skills it references for dispatch.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HughYau/qiushi-skill
Path: skills/workflows/SKILL.md
Commit: cbe6b08

Reviewed: ~17 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.