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.

65

Quality

78%

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_097/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is a concise, well-structured framework with concrete steps and a verification section. It would benefit from an explicit error-recovery loop given the irreversible nature of alliance commitments.

Suggestions

Add a feedback loop to the Verification section (e.g., 'If any check fails, revisit the corresponding step before finalizing the alliance') to support recovery from incomplete formalization.

Tighten the Overview to remove the generic filler sentence so every line earns its place.

Optionally include one brief worked example (e.g., a sample negotiation outcome) to lift actionability toward fully copy-paste-ready guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence with terse bullets and no padding of concepts Claude already knows, but the Overview line ('Building effective alliances requires careful assessment of mutual interests and clear agreements') is mild filler that could be trimmed.

4 / 5

Actionability

Concrete, domain-appropriate guidance is given — 'Send envoy to propose alliance', 'Exchange hostages or marriage partners', 'Formalize with oath or written agreement' — with only minor gaps and no vagueness, appropriate for an instruction-only skill.

4 / 5

Workflow Clarity

A clear six-step 'Implementation Steps' sequence is paired with an explicit 'Verification' checklist, but there is no if-fails-then-retry feedback loop for the commitments (hostages, marriage) that are effectively irreversible.

4 / 5

Progressive Disclosure

This is a compact single-purpose skill with no bundle files and no need for external references; its well-organized section structure satisfies the under-50-line exception for progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

78%Weight 40%Scale 1-5

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 specific, well-triggered, and distinct, clearly answering both what the skill does and when to use it. Its main weakness is a slightly narrow 'when' clause that could enumerate more triggering situations.

Suggestions

Expand the 'Use when...' clause to list additional natural trigger situations (e.g., 'when negotiating treaties', 'when seeking coalition partners', 'when a weaker state needs protection').

Add a couple of common synonyms/phrasings users might say (e.g., 'coalitions', 'treaties', 'pacts') to broaden trigger-term coverage toward a 5.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — 'ally evaluation (military strength, reliability, geography)', 'alliance types (marriage, military, mutual defense pacts)', 'negotiation protocols', 'maintenance through gifts and consultation' — with only minor coverage gaps, falling just short of comprehensive.

4 / 5

Completeness

Both 'what' ('Covers ally evaluation... alliance types... maintenance') and 'when' ('Use when creating interstate alliances for mutual defense or joint offensive operations') are present and explicit, but the 'when' is a single scenario rather than an enumerated set of triggers.

4 / 5

Trigger Term Quality

Natural trigger phrases like 'creating interstate alliances', 'mutual defense', and 'joint offensive operations' align with what a user would say, though a few common synonyms or situational variants are missing.

4 / 5

Distinctiveness Conflict Risk

The interstate-alliance / mutual-defense niche is clearly defined with distinct triggers, making conflict with unrelated skills unlikely.

5 / 5

Total

17

/

20

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.