CtrlK
BlogDocsLog inGet started
Tessl Logo

diplomatic-negotiation-pressure

Use when negotiating with a stronger adversary who may act in bad faith. Covers establishing baselines, demonstrating resolve through credible threats, demanding reciprocal formality, and preparing escape routes.

65

Quality

77%

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

Quality

Content

70%

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

The body is well-organized with a clear sequenced workflow and verification checklist, and it appropriately keeps everything inline given its small size. It is held back by abstract, non-copy-paste guidance and a slightly padded Expected Outcomes section.

Suggestions

Replace the aspirational 'Expected Outcomes' section with concrete success criteria or remove it, since it adds tokens without actionable guidance.

Tighten abstract steps like 'Demonstrate resolve' and 'Accept calculated risks' with specific, reproducible tactics (e.g., exact phrasing or observable signals) to raise actionability.

Add a brief concrete example of a credible reciprocal threat alongside the existing 'my head and the treasure' quote to make the Key Tactics immediately usable.

DimensionReasoningScore

Conciseness

The body is largely lean, but the 'Expected Outcomes' section ('Adversary respects your position', 'Personal reputation enhanced') is aspirational rather than instructional and does not earn its tokens.

2 / 3

Actionability

Steps give clear directives but remain abstract ('Demonstrate resolve', 'Accept calculated risks'); for an instruction-only skill the guidance lacks the concrete, specific detail needed to be fully actionable.

2 / 3

Workflow Clarity

A clearly numbered 1–7 sequence is paired with a 'Verification' checklist (confirm baselines, validate contingency plans, ensure documentation), providing explicit validation checkpoints.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references and well-organized sections (Steps, Key Tactics, Expected Outcomes, Verification), matching the simple-skill allowance for a top score.

3 / 3

Total

10

/

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 well-structured with an explicit 'Use when' trigger and a concrete list of capabilities, giving it strong completeness and distinctiveness. Its main weakness is trigger-term breadth, as the scenario phrasing is somewhat specialized rather than covering the range of natural user phrasings.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'establishing baselines, demonstrating resolve through credible threats, demanding reciprocal formality, and preparing escape routes' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' ('Covers establishing baselines...') and 'when' ('Use when negotiating with a stronger adversary who may act in bad faith'), satisfying the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Includes relevant natural terms ('negotiating', 'stronger adversary', 'bad faith') but the trigger phrasing is narrow and scenario-specific, missing common variations a user might naturally voice.

2 / 3

Distinctiveness Conflict Risk

The 'stronger adversary who may act in bad faith' framing carves a clear niche with distinct triggers 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.