CtrlK
BlogDocsLog inGet started
Tessl Logo

form-alliance-coalition

Use when organizing a multi-party coalition against a dominant threat. Covers envoy dispatch, resource gifting, securing key partners first, establishing coordination structures, and cementing alliances through marriage or exchange in Warring States diplomatic tradition.

70

Quality

85%

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 compact, well-structured instruction-only skill with a clear workflow and an explicit verification checklist. The main gap is actionability: several steps state principles rather than concrete, doable procedure.

Suggestions

Tighten abstract directives into concrete actions, e.g. replace 'Confirm that others perceive the same threat' with a checkable step like 'List each party and note their stated position on the threat before approaching them'.

Add a brief example of an envoy pitch or a sample resource-gift package so the steps become copy-ready rather than advisory.

Specify how coordination leadership is chosen (e.g. criteria or a default rule) so 'Designate leadership for the alliance' is actionable.

DimensionReasoningScore

Conciseness

The body is lean with no concept-explaining padding, each step carrying only one or two terse sub-bullets; the only minor redundancy is the Overview restating the description, which keeps it at the efficient end of the scale.

3 / 3

Actionability

It gives some concrete specifics (gifts of 'horses, gold, silk'; 'marriage, hostage exchange') but many directives read as abstract principles ('Recognize when a powerful actor endangers multiple parties', 'Confirm that others perceive the same threat') rather than executable procedure, landing at 'some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

A clearly numbered five-step sequence is paired with an explicit Verification section that functions as a checklist ('Confirm... Validate... Check...'), matching the anchor for a clear sequence with explicit validation steps.

3 / 3

Progressive Disclosure

At under 50 lines with no bundle files and no need for external references, the well-organized section structure (Overview, Steps, Expected Outcomes, Verification) satisfies the simple-skill allowance for a top score.

3 / 3

Total

11

/

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 that covers what and when with concrete actions and a clear, distinctive niche. Its main weakness is trigger-term naturalness, where domain jargon slightly undercuts the keywords a user would naturally say.

Suggestions

Soften the jargon in the trigger clause so it reads more like what a user would say, e.g. 'Use when building an alliance or coalition to counter a powerful shared enemy or rival'.

Consider dropping or relocating 'Warring States diplomatic tradition' so the natural trigger terms (coalition, alliance, dominant threat) lead the sentence.

Add common phrasings users might say ('form an alliance', 'team up against a stronger faction') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'envoy dispatch, resource gifting, securing key partners first, establishing coordination structures, and cementing alliances through marriage or exchange' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

It explicitly answers both what ('Covers envoy dispatch...cementing alliances through marriage or exchange') and when ('Use when organizing a multi-party coalition against a dominant threat'), matching the anchor for clearly answering both with an explicit trigger.

3 / 3

Trigger Term Quality

It includes some natural terms a user might say ('multi-party coalition', 'alliance', 'dominant threat') but mixes in specialized jargon ('envoy dispatch', 'resource gifting', 'Warring States diplomatic tradition') and misses common phrasings, so it stops at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The niche is sharply defined — multi-party coalition forming in a Warring States diplomatic tradition — giving it distinct triggers that are unlikely to fire for unrelated 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.