CtrlK
BlogDocsLog inGet started
Tessl Logo

unified-taskflow

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

74

Quality

93%

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

100%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 lean, actionable, and well-structured with a clear multi-phase workflow and explicit validation/feedback loops. It uses progressive disclosure effectively, offloading detail to verified reference and template files.

DimensionReasoningScore

Conciseness

Lean throughout: it assumes Claude's competence, defines only non-obvious rules and conventions, and every section earns its place without padding concepts Claude already knows.

5 / 5

Actionability

Fully executable guidance — concrete commands (e.g. 'python3 scripts/task-lifecycle.py new demo-task'), exact path/safe-component rules, --project-path/--json flags, and template sources — cover the common cases copy-paste ready.

5 / 5

Workflow Clarity

Clear Phase 0 → Elastic Execution → Completion sequence with explicit validation checkpoints (completeness gate, re-grounding per-item checks, 3-Strike→DEADBAND feedback loops) for destructive/batch operations.

5 / 5

Progressive Disclosure

Clear overview in SKILL.md with well-signaled one-level-deep references to references/*.md and assets/templates/*; all referenced paths (phase0-clarification.md, interaction-design.md, governance.md, regrounding-protocol.md, anchor/checkpoint/design templates) resolve to real bundle files.

5 / 5

Total

20

/

20

Passed

Description

86%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 specific, gives explicit 'use when' guidance with concrete triggers and exclusions, and clearly distinguishes itself from related skills. It is concise and avoids vague fluff.

DimensionReasoningScore

Specificity

Names the domain (heavy complex-task management) and several concrete mechanisms — 'anchor、checkpoint、design、恢复和验收追踪' — with only minor gaps in coverage breadth.

4 / 5

Completeness

Explicitly answers both 'what' (heavy management system using anchor/checkpoint/design/recovery/acceptance) and 'when' ('仅在用户明确要求...或任务确实需要...时使用', plus concrete exclusions).

5 / 5

Trigger Term Quality

Includes natural user phrases such as '使用 unified-taskflow / taskflow / .taskflow' and '跨多轮、多文件、多阶段...可恢复记录', with good keyword coverage though a few plain-language synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche explicitly differentiated from task-mode-router, minimal-implementation and clarify-before-change, with distinct triggers and minimal conflict risk.

5 / 5

Total

18

/

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.