negotiation-under-imminent-threat

Use when negotiating for survival under threat of execution or hostage situations. Restructures hostage transactions by demonstrating a living captive's leverage value, sequencing agreements to protect all parties, and buying time for allied intervention.

Quality

86%

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

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 body is a tight, well-structured instruction skill with a clear sequence and validation checklist. Promoting the Validation section into an explicit feedback loop and making a couple of high-level steps more concrete would lift actionability and workflow_clarity to 5.

Suggestions

Convert the Validation checklist into an explicit feedback loop (e.g., 'If a check fails, revise the sequenced agreement and re-verify before proceeding') to strengthen workflow_clarity.

Make step 4 ('Seek Additional Advocacy') more concrete by specifying what to ask of allies and how to frame the precedent argument.

Consider adding a brief fallback/branch when the executing authority rejects the sequenced agreement, so the workflow covers the main failure mode.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or over-explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Concrete, specific instructional guidance ('Secure the payment/territory first, Then proceed with the execution') rather than vague direction; instruction-only so absence of code is not penalized, but a few steps remain high-level.	4 / 5
Workflow Clarity	Steps are clearly sequenced (1-4) and a Validation section provides checkpoints, but the validation reads as a checklist rather than an explicit validate-fix-retry feedback loop.	4 / 5
Progressive Disclosure	A short (<50 line) single-purpose skill with well-organized sections (Overview, Steps, Decision Point, Expected Outcome, Validation) and no need for external references, qualifying for the simple-skill exception.	5 / 5
	Total	18 / 20 Passed

Description

87%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 well-crafted: third-person voice, explicit 'Use when' trigger, concrete actions, and a distinctive niche. Minor room for more comprehensive keyword synonyms keeps specificity and trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('demonstrating a living captive's leverage value, sequencing agreements to protect all parties, and buying time for allied intervention'), though coverage of the domain is not exhaustive.	4 / 5
Completeness	Explicitly answers both what ('Restructures hostage transactions by...') and when ('Use when negotiating for survival under threat of execution or hostage situations') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('negotiating for survival', 'threat of execution', 'hostage situations') with good coverage, missing only minor synonyms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (survival negotiation under threat of execution/hostage situations) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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_121/SKILL.md
Commit: 6b836e3

Reviewed: 5 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.