CtrlK
BlogDocsLog inGet started
Tessl Logo

judge-long-distance-military-campaign

Use when evaluating the feasibility of a long-distance surprise military attack. Assesses distance risks, intelligence reliability, supply line vulnerabilities, and contingency planning. Based on Qin's failed attack on Zheng as a cautionary example.

65

Quality

77%

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 ./kg/ontology/ontology-v1/skus/procedural/skill_026/SKILL.md
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 clearly structured instruction-only decision framework with strong workflow sequencing and validation. The main weaknesses are mild conciseness padding (Overview/Expected Outcomes) and actionability that names what to consider without specifying decision criteria or thresholds.

Suggestions

Tighten conciseness by removing the Expected Outcomes section (benefit justification, not operational guidance) and de-duplicating the Qin/Zheng reference already in the description.

Strengthen actionability by adding concrete decision criteria — e.g., a distance or territories-crossed threshold beyond which a surprise attack is judged infeasible, and reliability markers for evaluating informants.

Make the Validation section executable as a checklist with pass/fail conditions tied to each step rather than prose assertions.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but the Overview repeats the description ('failed Qin attack on Zheng') and the Expected Outcomes section is justification/benefit text rather than operational guidance.

2 / 3

Actionability

Steps give concrete considerations ('Calculate the distance to target', 'Consider how many territories must be crossed'), but lack decision criteria or thresholds, so guidance is incomplete for an actual feasibility determination.

2 / 3

Workflow Clarity

A clearly numbered six-step sequence is paired with a dedicated Validation section that provides explicit verification checkpoints, and step 6 adds contingency feedback for the forewarned-target case.

3 / 3

Progressive Disclosure

A compact (<50 lines) single-purpose skill with well-organized sections (Overview, Steps, Warning Signs, Expected Outcomes, Validation) and no need for external references.

3 / 3

Total

10

/

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 well-constructed description with an explicit trigger clause, specific capability list, and a distinctive niche. Voice is correctly third person. Only minor weakness is limited coverage of natural term variations in a narrow domain.

DimensionReasoningScore

Specificity

Lists multiple concrete assessments — 'Assesses distance risks, intelligence reliability, supply line vulnerabilities, and contingency planning' — naming specific capabilities rather than vague language.

3 / 3

Completeness

Clearly answers both what ('Assesses distance risks, intelligence reliability, supply line vulnerabilities, and contingency planning') and when via an explicit 'Use when evaluating the feasibility...' clause.

3 / 3

Trigger Term Quality

The trigger phrase 'evaluating the feasibility of a long-distance surprise military attack' is natural for the domain, but the niche terminology ('supply line vulnerabilities', 'contingency planning') lacks common variations a user might phrase differently.

2 / 3

Distinctiveness Conflict Risk

A highly specific niche — long-distance surprise military attack feasibility grounded in Qin's failed attack on Zheng — with distinct triggers unlikely to overlap with other skills.

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.