CtrlK
BlogDocsLog inGet started
Tessl Logo

rapid-military-advance-strategy

Use when commanding infantry-heavy forces against cavalry on flat terrain. Prioritizes speed over siege warfare, bypasses fortified cities, and seizes strategic objectives (armories like Luoyang武库, granaries like Ao) to neutralize cavalry advantages.

69

Quality

85%

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

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, clearly sequenced strategy skill with explicit verification steps and appropriate structure for its size. Its main weaknesses are minor redundancy across sections and actionability that stays at a strategic rather than operational level.

Suggestions

Trim redundancy: collapse the Overview, Decision Points, and Expected Outcomes sections into the Steps or fold them into the description, since they largely restate existing content.

Add operational specifics to the steps (e.g., force ratios, timing/pace guidance, garrison sizing) to move the guidance from strategic abstraction toward concrete, executable instruction.

Tighten the Verification checks into measurable pass/fail criteria rather than confirmatory statements (e.g., 'no siege underway against resisting cities' rather than 'validate that the advance maintains speed').

DimensionReasoningScore

Conciseness

The body is mostly lean, but the Overview, Decision Points, and Expected Outcomes sections restate content already present in the description and Steps, so it could be tightened.

2 / 3

Actionability

Guidance is concrete at the strategic level (named locations, "leave garrisons behind", "occupy mountain passes and river crossings") but remains largely abstract and lacks operational specifics, falling short of fully executable instruction.

2 / 3

Workflow Clarity

A clearly sequenced five-step process is paired with a dedicated Verification section listing explicit confirmation checks, satisfying the validation requirement.

3 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references, and is organized into clear sections (Overview, Steps, Decision Points, Expected Outcomes, Verification), meeting the simple-skill bar.

3 / 3

Total

10

/

12

Passed

Description

100%

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, concise description with an explicit trigger, concrete actions, and a distinctive niche. It scores maximally across all four dimensions.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "bypasses fortified cities, and seizes strategic objectives (armories like Luoyang武库, granaries like Ao)" — rather than vague language.

3 / 3

Completeness

It explicitly answers both what (prioritize speed, bypass cities, seize objectives) and when (explicit "Use when commanding infantry-heavy forces against cavalry on flat terrain").

3 / 3

Trigger Term Quality

The trigger "Use when commanding infantry-heavy forces against cavalry on flat terrain" uses natural domain phrasing a user would say, with good coverage (infantry, cavalry, flat terrain, siege warfare, fortified cities, armories, granaries).

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific — infantry-versus-cavalry on flat terrain — making it clearly distinguishable and unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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