CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

workflows

工作流组合:当一个任务明显需要多件思想武器接力时,提供四种标准组合模式(新项目启动、复杂问题攻坚、方案迭代优化、阶段复盘),定义调用顺序、每步交接物和终止条件。触发信号包括从零启动、疑难攻坚、迭代优化、阶段复盘;单一 skill 就够用时不触发。 English: Workflow patterns. When a task clearly needs several skills in sequence, pick one of four standard patterns (project kickoff, hard-problem assault, iterative improvement, stage retrospective) that fix the order, the handoff artifact between steps, and the stop condition. Skip when a single skill suffices.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 lean, tightly structured orchestration skill that gives per-pattern sequences, handoff artifacts, and stop conditions alongside an interruption-handling section with real feedback loops. Its only gaps are minor: per-step execution is delegated to named sub-skills, and as a single dense file it has no progressive layering.

Suggestions

Add a one-line note for each named sub-skill (e.g. investigation-first) so a reader can execute a step without opening that skill's own SKILL.md, closing the actionability gap.

Consider moving the four pattern tables into a single references file and keeping SKILL.md as the selection overview plus interruption rules, which would let progressive_disclosure reach the top anchor.

Optionally soften the coined trigger labels (e.g. "stage retrospective"→"stage review / retro") so the natural-language triggers align better with what users actually say.

DimensionReasoningScore

Conciseness

Maximally dense — each cell is a deliverable or stop condition, sub-skills are referenced by name without re-explaining them, and no concepts Claude already knows are restated; the single-line Mao epigraph is a deliberate thematic frame rather than padding.

5 / 5

Actionability

Each pattern gives a concrete ordered sub-skill sequence and a (step, handoff artifact, stop condition) table that is directly executable as a procedure; the minor gap is that each step's actual execution is delegated to a named sub-skill rather than specified inline.

4 / 5

Workflow Clarity

Every pattern has an explicit sequence (arrow notation), explicit stop-condition checkpoints, and the dedicated "中断处理" section provides feedback loops (假说被证伪→回到矛盾; 超出声明轮数→停下汇报); the skill is not destructive or batch, so the cap-3 rule does not apply.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is appropriately self-contained with a selection table plus four well-named sections and clear navigation; at ~68 lines (just over the simple-skill threshold) it is a single dense page with no progressive layering, so it sits below the 5 anchor.

4 / 5

Total

18

/

20

Passed

Description

92%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 precise, bilingual description that clearly scopes a workflow-composition skill: it names four standard patterns and their three deliverables and gives explicit positive and negative trigger guidance. Its only weakness is that several trigger phrases are the skill's own coined labels rather than the most common user utterances.

DimensionReasoningScore

Specificity

Lists multiple concrete patterns — "project kickoff, hard-problem assault, iterative improvement, stage retrospective" — and pins each to three deliverables ("order, the handoff artifact between steps, and the stop condition"), giving comprehensive coverage for a composition skill.

5 / 5

Completeness

Explicitly answers both what (four standard patterns fixing order/handoff/stop condition) and when ("When a task clearly needs several skills in sequence" plus an explicit negative trigger), matching the anchor for concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with "needs several skills in sequence", "Skip when a single skill suffices", and four named trigger scenarios, but the coined phrasings ("hard-problem assault", "stage retrospective") are not the most natural terms users would spontaneously say.

4 / 5

Distinctiveness Conflict Risk

Clear niche (multi-skill workflow composition) with a sharp negative trigger ("Skip when a single skill suffices") that minimizes overlap with single-purpose skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.