CtrlK
BlogDocsLog inGet started
Tessl Logo

military-campaign-planning

Use when planning military campaigns from intelligence through post-victory consolidation. Covers terrain assessment (知水草处), supply logistics for 60,000+ troops, alliance coordination, siege tactics, and garrison establishment (置使者护田积粟).

61

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./kg/ontology/ontology-v1/skus/procedural/skill_241/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A well-structured, mostly lean methodology skill with a clear sequenced workflow and verification checklist. It is held back by abstract operational guidance, terminal rather than inline validation, and a lightly padded outcomes section.

Suggestions

Replace abstract steps like "Calculate provisions needed" with a concrete method or worked example so the guidance is directly actionable.

Add inline feedback loops (e.g. if intelligence gaps are found, re-gather before launch) rather than only a terminal Verification checklist, since campaigns are destructive operations.

Trim the largely obvious "Expected Outcomes" section to improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly lean bullet points with no basic-concept filler, but the "Expected Outcomes" section (Territorial expansion, Enemy neutralization, etc.) is largely obvious padding that could be trimmed. Not a 3 because not every token earns its place.

2 / 3

Actionability

Gives concrete strategic steps and specific historical examples (60,000 troops, 2,000 cavalry, named passes), but the operational guidance stays abstract ("Calculate provisions needed", "Control key passes") without concrete methods. Not a 3 because key operational details are missing; not a 1 because it instructs rather than merely describes.

2 / 3

Workflow Clarity

Clear sequence (Pre-Campaign -> Execution -> Post-Campaign) with a dedicated Verification checklist, but for destructive campaign operations the checks are terminal rather than inline feedback loops (validate -> fix -> retry). Not a 3 because there are no explicit error-recovery feedback loops, which the rubric caps at 2 for destructive operations.

2 / 3

Progressive Disclosure

A single, well-organized SKILL.md with clear section headers and no need for external bundle files (none exist), matching the guideline that well-organized sections with no required references can score 3. Not a 2 because navigation and structure are clear.

3 / 3

Total

9

/

12

Passed

Description

85%

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 specific, distinctive description with explicit what-and-when guidance in third person. Its main weakness is trigger-term coverage, which lists relevant terms but few natural variations a user would say.

Suggestions

Add common natural trigger variations such as 'battle plans', 'war strategy', or 'troop deployment' so the description matches a wider range of user phrasings.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: "terrain assessment", "supply logistics for 60,000+ troops", "alliance coordination", "siege tactics", and "garrison establishment". Not a 2 because it enumerates several distinct capabilities rather than naming only a domain and a few actions.

3 / 3

Completeness

Explicitly answers both what ("Covers terrain assessment ... siege tactics ... garrison establishment") and when ("Use when planning military campaigns from intelligence through post-victory consolidation"). Not a 2 because the trigger clause is explicit rather than implied.

3 / 3

Trigger Term Quality

"planning military campaigns", "siege tactics", and "supply logistics" are natural terms, but coverage is thin on common variations (e.g. battle plans, war strategy, troop deployment). Not a 3 because it lacks good coverage of the variations a user might naturally say.

2 / 3

Distinctiveness Conflict Risk

A clear niche (classical military campaign planning) with distinctive triggers including the classical Chinese phrases, making it unlikely to fire for unrelated skills. Not a 2 because the scope is specific rather than broadly overlapping.

3 / 3

Total

11

/

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.