CtrlK
BlogDocsLog inGet started
Tessl Logo

military-encirclement-tactics

Use when besieging a fortified enemy or planning encirclement warfare. Based on Bai Qi's victory at Changping (长平) — feign retreat to draw the enemy out, deploy hidden forces to cut retreat routes, sever supply lines, and wait 40+ days for starvation-driven collapse.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 concise, well-structured procedural skill with explicit validation checkpoints and concrete operational specifics. The main improvement area is adding feedback-loop guidance for when validation checks fail.

Suggestions

Add explicit error-recovery guidance after each Validation checkpoint (e.g., what to do if the ambush force is detected before the feigned retreat begins).

Tighten the intro/Overview to remove restatement of the description, or merge them into a single framing line.

Make the vaguer steps more concrete — quantify 'maintain pressure' or specify how leadership is identified and eliminated during the breakout phase.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the intro line and Overview mildly restate the description, leaving minor trimmable redundancy that keeps it just below fully efficient.

4 / 5

Actionability

Concrete specifics like '25,000 troops', '5,000 cavalry', and '40+ days' make the guidance actionable for its domain, though a few steps ('Maintain pressure', 'Kill their leadership') stay high-level rather than fully concrete.

4 / 5

Workflow Clarity

Five clearly sequenced steps plus a dedicated Validation section with explicit checkpoints satisfy most of the anchor, but error-recovery feedback loops (what to do when a checkpoint fails) are only weakly implied, so it does not reach 5.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external references; the well-organized sections (Overview, Steps, Expected Outcomes, Validation) meet the simple-skill exception for a top score.

5 / 5

Total

17

/

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 highly specific, well-triggered description that clearly states both capability and use conditions with minimal padding. The only minor gap is trigger-term synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'feign retreat to draw the enemy out, deploy hidden forces to cut retreat routes, sever supply lines, and wait 40+ days for starvation-driven collapse' — giving comprehensive, specific coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what (the listed encirclement tactics) and when ('Use when besieging a fortified enemy or planning encirclement warfare') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural triggers like 'besieging a fortified enemy' and 'encirclement warfare' are present and domain-appropriate, but coverage lacks synonyms or common variations a user might phrase differently, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — encirclement/besieging warfare anchored to a specific historical battle — making conflict with other skills unlikely.

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
baojie/shiji-kb
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.