CtrlK
BlogDocsLog inGet started
Tessl Logo

workflow-runner

在 Claude Code / OpenClaw / Cursor 中直接运行 agency-orchestrator YAML 工作流——无需 API key,使用当前会话的 LLM 作为执行引擎。当用户提供 .yaml 工作流文件或要求多角色协作完成任务时触发。

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/workflow-runner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The body is a well-structured, actionable guide with a clear sequenced workflow, concrete tool usage, and explicit error handling. It earns high marks across all dimensions with only minor trimming and validation-loop opportunities preventing top scores.

Suggestions

Add an explicit validation checkpoint before saving results (e.g., verify each step's output is non-empty and role-consistent before writing summary.md) to strengthen the feedback loop for batch operations.

Tighten the YAML schema block by removing field comments Claude can infer (e.g., explaining 'inputs' or 'steps' generically) to improve token efficiency.

Consider moving the metadata.json schema and directory-probing fallback sequence into a short reference section or example so the core 5-step flow reads leaner.

DimensionReasoningScore

Conciseness

Mostly efficient with purposeful sections and concrete tool calls; minor over-explanation in the YAML schema block and the directory-probing sequence could be trimmed without losing clarity.

4 / 5

Actionability

Provides concrete executable guidance — specific Read/Bash/Agent/Write tool usage, exact file path patterns, a metadata.json schema, and a ready subagent prompt — with only minor gaps in a few operational details.

4 / 5

Workflow Clarity

A clear 5-step sequenced process with topological ordering, an execution-plan display, a HARD-GATE checkpoint, and a dedicated error-handling section; a minor validation gap (no explicit validate-output-before-save loop) keeps it just below 5.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested or buried references, and no bundle files exist to misuse; a small amount of inline schema/example content could theoretically be externalized, but the single-file structure is appropriate.

4 / 5

Total

16

/

20

Passed

Description

82%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.

The description is clear, third-person, and explicitly covers both what the skill does and when to trigger it, with concrete trigger phrases. It is slightly light on enumerating multiple specific concrete actions, which keeps specificity at the midpoint.

DimensionReasoningScore

Specificity

Names the domain ('运行 agency-orchestrator YAML 工作流') and a concrete mechanism ('使用当前会话的 LLM 作为执行引擎'), but lists only 1-2 concrete actions rather than a comprehensive set of specific actions.

3 / 5

Completeness

Explicitly answers both 'what' (run agency-orchestrator YAML workflows using the session LLM) and 'when' ('当用户提供 .yaml 工作流文件或要求多角色协作完成任务时触发') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('.yaml 工作流文件', '多角色协作') plus tool names (Claude Code/OpenClaw/Cursor); a few common synonyms or variations are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (agency-orchestrator YAML multi-role workflows) with distinct triggers and tool-name scoping, minimizing conflict with other skills.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
jnMetaCode/superpowers-zh
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.