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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

71%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 concise, well-structured, and includes a clear sequenced workflow with explicit verification. Its weakest point is actionability, where the negotiation guidance leans strategic and abstract rather than offering fully concrete, executable detail.

Suggestions

Tighten the 'Expected Outcomes' section or fold it into the steps to remove the small amount of redundancy and lift conciseness toward a 5.

Add more concrete, actionable detail to the steps and Key Tactics (e.g., specific phrasing templates or escalation/de-escalation moves) to move actionability from strategic directives to executable guidance.

Convert the Verification section into a validate-fix-retry feedback loop (e.g., if a baseline was not defined before discussions, pause and define it) to earn a 5 on workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining background concepts; minor trimming possible in the 'Expected Outcomes' section, so it sits just below a 5.	4 / 5
Actionability	Steps give concrete directives (e.g. 'Determine what you absolutely cannot concede') and one concrete example quote, but much of the guidance is strategic and abstract ('Never show fear', 'Be willing to face personal danger') without fully executable detail, matching the some-concrete-guidance-but-incomplete anchor.	3 / 5
Workflow Clarity	A clearly sequenced 7-step process is paired with an explicit 3-item Verification section; it lacks a validate-fix-retry feedback loop, so it falls just below a 5.	4 / 5
Progressive Disclosure	A short, single-purpose skill (under 50 lines, no external references needed) that is well-organized into clearly labeled sections (Steps, Key Tactics, Expected Outcomes, Verification), qualifying for the top anchor under the simple-skill exception.	5 / 5
	Total	16 / 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 answers both what and when with a distinctive niche. It stops just short of the top anchors on specificity, trigger terms, and completeness because it offers one consolidated trigger phrase and a conceptual rather than fully detailed action list.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions ('establishing baselines, demonstrating resolve through credible threats, demanding reciprocal formality, and preparing escape routes'), matching the anchor for several specific actions with minor coverage gaps; not a 5 because the actions are conceptual rather than fully enumerated.	4 / 5
Completeness	Both 'what' (the 'Covers ...' action list) and 'when' (the 'Use when negotiating ...' clause) are present and explicit, but the 'when' offers a single trigger phrase rather than multiple concrete triggers, keeping it just below a 5.	4 / 5
Trigger Term Quality	'Use when negotiating with a stronger adversary who may act in bad faith' uses natural phrasing a user would say; good keyword coverage but missing common synonyms/variations, so it sits just below a 5.	4 / 5
Distinctiveness Conflict Risk	'negotiating with a stronger adversary who may act in bad faith' carves a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: baojie/shiji-kb
Path: kg/ontology/ontology-v1/skus/procedural/skill_175/SKILL.md
Commit: 6b836e3

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.