CtrlK
BlogDocsLog inGet started
Tessl Logo

military-oath-and-mobilization

Use when mobilizing troops, establishing military authority, or enforcing battlefield discipline. Covers the ritualized oath procedure with 黄钺 and 白旄 symbols, troop assembly, consequence announcements, and campaign execution.

75

Quality

92%

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

85%

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

The body is concise, well-structured, and includes explicit validation steps, but several procedural steps are phrased abstractly rather than with concrete, actionable specifics. Tightening the vague steps would raise the actionability score.

Suggestions

Replace abstract steps with concrete guidance — e.g., specify how deadlines are set and announced, and what "maintain formation" concretely requires, rather than leaving them as directives.

The Overview restates the frontmatter description; consider trimming it to avoid redundancy, or repurpose it to add concrete detail the description lacks.

Make the Decision Points actionable by giving the explicit condition checks (e.g., criteria for "conditions favor victory") instead of open-ended assessment prompts.

DimensionReasoningScore

Conciseness

The body is lean and instruction-oriented; the symbol explanations (黄钺/白旄 = delegated military authority) are domain-specific rather than general concepts Claude already knows, and there is only mild Overview/description overlap. It is not below 3 because no padding of general knowledge is present.

3 / 3

Actionability

Some concrete specifics exist ("Hold the yellow battle-axe (黄钺) in the left hand", example phrases "苍兕苍兕" / "後至者斩"), but several steps remain abstract — "Set clear deadlines", "Maintain formation and discipline", "assess whether conditions favor victory" — so it is not fully copy-paste-ready. It is above 1 because concrete actions and examples are present.

2 / 3

Workflow Clarity

A clearly numbered 4-step sequence is paired with a dedicated "## Validation" checklist (confirm symbols, verify consequences, check strategic assessment), matching the explicit-validation-and-checklist anchor. It is not below 3 because validation checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external references; the well-organized sections (Overview, Steps, Decision Points, Expected Outcomes, Validation) satisfy the simple-skill allowance for a top score. No bundle files exist, so structure is judged on section organization.

3 / 3

Total

11

/

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.

The description is strong across all dimensions: it states concrete capabilities, opens with a natural "Use when" trigger, covers what-and-when explicitly, and occupies a distinct niche. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "mobilizing troops, establishing military authority", "ritualized oath procedure with 黄钺 and 白旄 symbols, troop assembly, consequence announcements, and campaign execution" — matching the multiple-concrete-actions anchor.

3 / 3

Completeness

Explicitly answers both: what ("Covers the ritualized oath procedure...") and when ("Use when mobilizing troops...") with an explicit "Use when" trigger clause.

3 / 3

Trigger Term Quality

Natural domain phrasing a user would actually say ("mobilizing troops", "establishing military authority", "enforcing battlefield discipline", "troop assembly") gives good coverage; it is not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

The 黄钺/白旄 ritual-oath-and-mobilization niche is highly specific and unlikely to overlap with unrelated skills, matching the clear-distinct-niche anchor.

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.