CtrlK
BlogDocsLog inGet started
Tessl Logo

protracted-strategy

触发:当目标长期、任务复杂、资源暂时处于劣势,或短期无法速胜但又不能放弃时调用;常见信号包括 long-term effort、phased plan、endurance、战略耐心、需要分阶段推进。 English: Trigger when the work is long-horizon, difficult, and unlikely to be won quickly. Use this skill to divide the effort into stages, keep strategic confidence, and accumulate small wins into overall victory.

64

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/protracted-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers a structured, actionable phased-strategy workflow with a concrete operating protocol and clear sequencing. Its main weaknesses are verbosity from illustrative quotes/mindset prose and a dangling reference to a non-existent original-texts.md file.

Suggestions

Trim the Mao quotes and attitude/mindset bullet lists that restate familiar ideas; keep only the lines that drive a concrete action, to tighten conciseness.

Either create references/original-texts.md with the cited source material or remove the '详细原著依据见 original-texts.md' pointer so no referenced file is missing.

Strengthen workflow_clarity by making the stage-progression checkpoint a hard gate (verify the listed transition conditions are met before advancing) rather than a soft 're-call this skill' suggestion.

DimensionReasoningScore

Conciseness

The ~160-line body carries substantive methodology (three-phase framework, operating protocol, error table) but is padded with extensive Mao quotes and attitude/mindstate bullets that could be tightened; it is mostly efficient but includes unnecessary explanation.

3 / 5

Actionability

Provides a concrete operating protocol — output a stage-assessment table with defined fields, pick one of three stages, name a '局部进攻点', set checkpoints — plus a corrective error table, giving mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

A clear six-step method flow (第一步–第六步) is sequenced, with stage-transition conditions and a re-call checkpoint ('设置阶段检查点…重新调用此 skill 评估阶段') providing most validation checkpoints; minor gaps remain versus a hard verify-before-proceed gate.

4 / 5

Progressive Disclosure

Sections are well organized and references are one level deep, but the body cites 'original-texts.md' for detailed source material while no bundle file by that name exists in references/scripts/assets — a minor organization gap.

4 / 5

Total

15

/

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.

The description cleanly states both capability and trigger conditions with concrete, natural-language signal terms and a well-scoped niche. It is comprehensive on the what/when axis and only slightly thin on trigger-term synonyms.

DimensionReasoningScore

Specificity

Names the domain (long-horizon difficult work) and lists several concrete actions — 'divide the effort into stages', 'keep strategic confidence', 'accumulate small wins into overall victory' — with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (divide into stages, keep confidence, accumulate small wins) and when via concrete trigger clauses — '触发:当…时调用' and 'Trigger when the work is long-horizon…' — matching the anchor-5 example.

5 / 5

Trigger Term Quality

Good coverage of natural trigger terms ('long-horizon', 'long-term effort', 'phased plan', 'endurance', '战略耐心', '分阶段推进') with explicit signal list; a few synonyms/extensions are missing, so it falls short of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The trigger is narrowly scoped to unwinnable-quickly, long-horizon phased-strategy situations, giving it a clear niche with only minor overlap risk against general planning skills.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HughYau/qiushi-skill
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.