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).

76

Quality

93%

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

87%

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

The body is a concise, actionable, well-organized procedure with an explicit validation section. Its main gap is that validation reads as terminal assessment rather than embedded error-recovery feedback loops, capping workflow clarity at 2.

Suggestions

Convert the Validation section into embedded validate-then-retry checkpoints within the step sequence (e.g., after reframing, verify mutual benefit and adjust before proceeding) to provide genuine error-recovery feedback loops.

Add an explicit failure/abort condition so Claude knows when to stop the procedure rather than push forward, given its coercive nature.

Clarify the calibration step for shame/honor motivators as an inline check during execution rather than only a post-hoc assessment.

DimensionReasoningScore

Conciseness

The body is lean and efficient — terse imperative steps with brief glosses and no padding explaining what negotiation is or other concepts Claude already knows. It is not score 2 because there is no unnecessary explanation to trim; every section earns its place.

3 / 3

Actionability

As an instruction-only skill it provides concrete, specific guidance such as "Approach directly with urgency, bypassing normal protocol" and "Conduct the ritual (blood oath, signing) on the spot before doubts resurface". It is not score 2 because the instructions are concrete and specific rather than vague or pseudocode-like; the absence of code is not penalized for an instruction-only skill.

3 / 3

Workflow Clarity

The 10 steps are clearly sequenced and a Validation section is present, but the validation items are terminal assessment checks (verify reframing, confirm formalization, assess motivator calibration) rather than embedded validate→fix→retry feedback loops within the workflow. It is not score 3 because there are no explicit error-recovery feedback loops, and not score 1 because the sequence and validation are clearly present.

2 / 3

Progressive Disclosure

The skill is a single self-contained ~30-line file with no bundle files, organized into clear sections (Overview, Steps, Critical Techniques, Expected Outcome, Validation). Per the simple-skills scoring note, well-organized short content with no external references can score 3. It is not score 2 because the organization is clear and there are no nested or poorly signaled references.

3 / 3

Total

11

/

12

Passed

Description

100%

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, complete, and distinctive, with an explicit 'Use when' trigger and a list of concrete actions. It is a strong, well-scoped description.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "physical proximity to neutralize power imbalance", "reframes the deal as serving their interests", "invokes historical precedent", and "demands on-the-spot formalization (blood oath)" — matching the anchor for listing multiple specific concrete actions. It is not score 2 because the actions are concrete and comprehensive rather than partial.

3 / 3

Completeness

It explicitly answers both what ("Employs physical proximity... reframes... invokes... demands... formalization") and when ("Use when breaking deadlocks...") with an explicit trigger clause. It is not score 2 because the when is stated explicitly, not merely implied.

3 / 3

Trigger Term Quality

The clause "Use when breaking deadlocks in stalled negotiations or forcing immediate commitment from a dismissive counterparty" supplies natural trigger terms a user would say (deadlocks, stalled negotiations, dismissive counterparty). It is not score 2 because coverage is broad and phrased in user-natural language rather than missing common variations.

3 / 3

Distinctiveness Conflict Risk

The niche is highly specific — high-stakes negotiation deadlocks and blood-oath formalization — making it clearly distinguishable and unlikely to trigger for the wrong skill. It is not score 2 because the trigger set is distinct rather than overlapping with similar skills.

3 / 3

Total

12

/

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.