CtrlK
BlogDocsLog inGet started
Tessl Logo

alliance-formation-strategy

Use when creating interstate alliances for mutual defense or joint offensive operations. Covers ally evaluation (military strength, reliability, geography), alliance types (marriage, military, mutual defense pacts), negotiation protocols, and long-term alliance maintenance through gifts and consultation.

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

Passed

No findings from the security scan

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.

A well-organized, lean framework with a clear workflow and an explicit verification checklist. Its main weakness is actionability: several steps describe categories of action rather than giving concrete, executable guidance.

Suggestions

Tighten vague steps into concrete procedures — e.g. replace 'Negotiate terms and obligations' with the specific terms to settle (territorial shares, command division, duration, exit conditions) and a checklist for each.

Add a brief worked example of a full negotiation (proposed terms → counter-offer → finalized oath) so the abstract 'Marriage/Military/Mutual Defense' categories become copy-paste-ready templates.

Give the envoy/communication steps concrete form (who to send, what message to deliver, response deadlines) rather than the generic 'Send envoy' and 'Maintain regular communication'.

DimensionReasoningScore

Conciseness

Lean bullet-point structure with no padding or explanations of concepts Claude already knows; every line carries actionable content. Not a 2 because there is no unnecessary prose to trim.

3 / 3

Actionability

Some steps are concrete ('Send envoy to propose alliance', 'Exchange hostages or marriage partners'), but several are abstract descriptions — 'Negotiate terms and obligations', 'Maintain regular communication', 'Identify Shared Interests' — that instruct by naming a category rather than giving specific how-to guidance. Not a 3 because the guidance is not consistently executable/copy-paste ready; not a 1 because concrete actions do appear.

2 / 3

Workflow Clarity

Implementation Steps are clearly sequenced (1–6) and the closing Verification section supplies explicit validation checkpoints (confirm four-dimension ally evaluation, confirm tangible formalization, confirm ongoing maintenance protocols).

3 / 3

Progressive Disclosure

A compact (~60 line), single-purpose skill organized into clearly labeled sections with no need for external bundle files; per the simple-skills note, well-organized sections alone justify a top score here.

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.

A strong, well-formed description: it states an explicit trigger, enumerates concrete capabilities, and occupies a distinct niche. It is concise yet specific with no over-claims or filler.

DimensionReasoningScore

Specificity

Names multiple concrete capabilities — 'ally evaluation (military strength, reliability, geography)', 'alliance types (marriage, military, mutual defense pacts)', 'negotiation protocols', and 'long-term alliance maintenance through gifts and consultation' — rather than vague abstractions.

3 / 3

Completeness

Opens with an explicit 'Use when creating interstate alliances…' trigger (the when) and follows with a clear enumeration of what the skill covers (the what).

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say ('creating interstate alliances', 'mutual defense', 'joint offensive operations') with good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — interstate/diplomatic alliance formation — with distinct triggers unlikely to fire for unrelated skills.

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.