CtrlK
BlogDocsLog inGet started
Tessl Logo

evaluating-peace-negotiations

Use when assessing whether to enter peace talks or risk signaling weakness. Evaluates adversary incentives, ally perceptions, and negotiation leverage to determine if peace overtures will succeed or backfire.

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.

The body is concise and well-structured, with a sequenced analysis workflow and an explicit verification checkpoint. The main weakness is actionability: the analytical steps name what to consider but not how to judge it.

Suggestions

Tighten each Analysis Step by adding the specific evidence or decision criteria to look for (e.g., what signals indicate the adversary is committed to victory vs. willing to settle).

For "Predict adversary's behavior", specify concrete indicators that distinguish propaganda use of negotiations from genuine engagement.

Make the Expected Outcome section tie back to the Verification checks so the reader knows which condition failing should steer them toward the Alternative Approach.

DimensionReasoningScore

Conciseness

Lean throughout with no over-explanation of concepts Claude already knows; every line is directed at the decision and earns its place in context.

3 / 3

Actionability

Steps and warning signs are concrete and well-framed, but the guidance is conceptual/analytical ("Assess adversary's goal", "Predict adversary's behavior") rather than specifying the evidence or criteria to apply at each step.

2 / 3

Workflow Clarity

A clear five-step analysis sequence is paired with an explicit Verification section whose checks act as validation checkpoints before a recommendation is made.

3 / 3

Progressive Disclosure

A short (under 50 lines), single-purpose skill with no need for external references; its well-organized sections satisfy the simple-skill progressive-disclosure bar.

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.

The description is strong: it specifies concrete analytical actions, includes an explicit use-when trigger, and carves out a distinctive niche. Its only weak spot is trigger-term breadth, which stays within a narrow negotiation vocabulary.

Suggestions

Broaden trigger terms to include natural user phrasings like "ceasefire", "settlement", "diplomacy", or "treaty talks" so the skill surfaces for more varied requests.

DimensionReasoningScore

Specificity

Lists multiple concrete analysis actions — "Evaluates adversary incentives, ally perceptions, and negotiation leverage" — naming distinct analytical capabilities rather than vague activity.

3 / 3

Completeness

Explicitly answers both what (evaluates incentives, perceptions, leverage to judge success or backfire) and when via a "Use when assessing whether to enter peace talks..." trigger clause.

3 / 3

Trigger Term Quality

Includes relevant natural terms like "peace talks", "negotiations", and "peace overtures", but misses common variations users might say such as ceasefire, settlement, diplomacy, or treaty.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — the decision to enter peace negotiations — with distinct triggers unlikely to overlap with 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.