CtrlK
BlogDocsLog inGet started
Tessl Logo

high-stakes-negotiation-tactics

Use when breaking deadlocks in stalled negotiations or forcing immediate commitment from a dismissive counterparty. Employs physical proximity to neutralize power imbalance, reframes the deal as serving their interests, invokes historical precedent, and demands on-the-spot formalization (blood oath).

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is concise, well-structured, and action-oriented with a real validation section, fitting a simple instruction-only skill. Main improvement room is adding an explicit retry/feedback loop and slightly more concrete execution detail per step.

Suggestions

Add an explicit validate-and-retry feedback loop in the Validation section (e.g. 'If a check fails, recalibrate and re-attempt formalization before exiting').

Make each step's action more concrete and observable so the guidance is closer to copy-paste executable (specify what 'enter forcefully' concretely entails).

Consider splitting the tactic-specific detail (e.g. shame/honor calibration) into a short reference so the main body stays a pure overview.

DimensionReasoningScore

Conciseness

The body is lean (~31 lines), uses terse numbered steps, and never explains concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Steps are concrete and directive (e.g. 'Approach directly with urgency, bypassing normal protocol', 'Conduct the ritual (blood oath, signing) on the spot'), but guidance is behavioral rather than copy-paste executable, leaving minor gaps versus fully concrete instruction.

4 / 5

Workflow Clarity

A clearly sequenced 10-step process is backed by a dedicated Validation section with three checkpoints, but there is no explicit validate-fix-retry feedback loop for error recovery, which the anchors treat as a minor gap.

4 / 5

Progressive Disclosure

Under 50 lines with no external references, organized into clear sections (Overview, Steps, Critical Techniques, Expected Outcome, Validation), satisfying the simple-skill exception for well-organized single-purpose skills.

5 / 5

Total

18

/

20

Passed

Description

92%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, uses third-person voice, and clearly separates the trigger condition from the tactics employed. It is a strong, low-conflict description with only minor room for additional natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'breaking deadlocks', 'physical proximity to neutralize power imbalance', 'reframes the deal as serving their interests', 'invokes historical precedent', 'demands on-the-spot formalization (blood oath)' — giving comprehensive coverage of the skill's behavior.

5 / 5

Completeness

Explicitly answers both 'what' (the employed tactics) and 'when' via a clear 'Use when breaking deadlocks in stalled negotiations or forcing immediate commitment...' trigger clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'breaking deadlocks', 'stalled negotiations', 'forcing immediate commitment', and 'dismissive counterparty' are terms a user might say, but synonym coverage is incomplete and there are no alternate phrasings, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific — stalled-deadlock negotiation resolved via physical proximity and blood-oath formalization — with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

19

/

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.