CtrlK
BlogDocsLog inGet started
Tessl Logo

unified-taskflow

面向真正复杂任务的重型管理系统,使用 anchor、checkpoint、design、恢复和验收追踪。 仅在用户明确要求使用 unified-taskflow、taskflow、.taskflow,或任务确实需要跨多轮、多文件、多阶段的可恢复记录时使用。 不用于小修、普通优化、普通重构、单个 Skill 小改、日常 bug fix,或 task-mode-router / minimal-implementation 已足够处理的任务。

72

Quality

89%

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

85%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 skill body with a clear multi-phase workflow, explicit validation/feedback loops, and clean progressive disclosure to real bundle files. Verbosity is the weakest dimension due to cross-section repetition of the same rules.

Suggestions

Dedupe the 续接语义 and 3-Strike rules: state each once in its primary section and reference it elsewhere rather than restating, to tighten conciseness.

Consolidate the rule-priority block (Safety > Correctness > ...) with the anti-pattern table so the cross-stage-reasoning constraints live in one place.

Move the compatibility note about historical `archived` status (currently inline under Completion) into governance.md to keep the main workflow lean.

DimensionReasoningScore

Conciseness

Instruction-dense with no padding of concepts Claude already knows, but some rules recur across the priority, workflow, and anti-pattern sections (e.g., 续接语义, 3-Strike semantics) and could be tightened.

4 / 5

Actionability

Provides concrete executable commands ("python3 scripts/task-lifecycle.py new demo-task"), a real directory tree, and explicit script-boundary rules, with minor gaps where guidance stays process-oriented rather than command-level.

4 / 5

Workflow Clarity

Phase 0 → Execution → Completion is clearly sequenced with explicit validation checkpoints (完备性门禁, Re-grounding 逐项核对) and a 3-Strike→DEADBAND feedback loop for error recovery; destructive/lifecycle operations carry validation, so no cap applies.

5 / 5

Progressive Disclosure

The body is a clear overview with well-signaled one-level-deep references (phase0-clarification.md, regrounding-protocol.md, governance.md, interaction-design.md) and template files, all of which exist in the bundle, plus a 引用文件 navigation table.

5 / 5

Total

18

/

20

Passed

Description

95%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 description: third-person, explicit what/when, comprehensive trigger terms including the .taskflow extension, and clear distinctiveness via negative carve-outs. The only minor gap is that mechanisms are named as labels rather than fully spelled-out concrete actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete mechanisms ("anchor、checkpoint、design、恢复和验收追踪"), but these are noun-labels for mechanisms rather than verb-phrased concrete actions, leaving minor gaps versus fully comprehensive coverage.

4 / 5

Completeness

Explicitly answers both "what" (重型管理系统 using anchor/checkpoint/design/recovery/acceptance tracking) and "when" with concrete positive and negative trigger guidance ("仅在...使用" / "不用于...").

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including name synonyms ("unified-taskflow、taskflow") and the file extension (".taskflow"), plus use-case phrases users would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (heavyweight multi-round/multi-file task management) with explicit negative carve-outs against task-mode-router / minimal-implementation / clarify-before-change, minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 3 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
ooooooooooooooooooop/agent-tools
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.