CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

negotiation

Prepare and execute negotiations using tactical empathy, calibrated questions, and the Ackerman method. Use when the user mentions "salary negotiation", "contract terms", "handling objections", "mirroring and labeling", "difficult conversation", "deal terms", "BATNA", or "anchoring". Also trigger when preparing for vendor negotiations, resolving pricing disputes, or navigating high-stakes conversations where both parties need to feel heard. Covers accusation audits, Black Swan discovery, and the "Thats Right" technique. For persuasion in product/marketing, see influence-psychology.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 delivers highly actionable negotiation guidance with concrete phrasings, worked examples, and useful diagnostics backed by a well-organized one-level-deep reference file. Its weaknesses are token efficiency (author bio, affiliate links, repeated links, and duplicated passages) and the absence of an explicitly sequenced end-to-end workflow, since techniques are presented as a catalog rather than ordered stages.

Suggestions

Trim non-operational sections ("About the Author", affiliate-tagged "Further Reading") and replace the eight repeated "See: [references/techniques.md]" lines with a single well-placed pointer, removing duplicated passages such as the irrationality diagnosis that appears in both section 8 and "Handling Common Situations".

Add a short sequenced workflow section (e.g., prepare accusation audit -> open with tactical empathy/labeling -> ask calibrated questions -> pursue "That's right" -> Ackerman sequence -> close) so the techniques become an ordered process rather than a catalog.

Move the per-technique "Product applications" tables (or the deeper "Why it works" detail) into references/techniques.md so SKILL.md reads as a lean overview with clearly signaled one-level-deep references.

DimensionReasoningScore

Conciseness

The technique sections are dense and earn their tokens (copy patterns, application tables), but there is measurable padding: the "About the Author" bio and affiliate-tagged "Further Reading" links add nothing executable, the identical "See: [references/techniques.md]" link is repeated 8 times, and content is duplicated (the "ill-informed / constrained / hiding something" diagnosis appears in both section 8 and "Handling Common Situations"). Mostly efficient but could be tightened, matching anchor 3; anchor 2 would require several sections of unnecessary explanation, whereas ~85% of the body is genuinely operational.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: copy-paste-ready phrasings ("How am I supposed to do that?", "It seems like...", "Have you given up on [the project]?") and a worked numeric Ackerman example ("Target $120K: open discussion at $78K, move to $102K, $114K, final $120,350 + extra PTO"). Concrete conditionals ("They anchor with an extreme number -> 'How did you arrive at that figure?'") cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The eight numbered sections are a technique catalog, not a sequenced negotiation workflow; there is no explicit prep-to-close order of operations. Checkpoints do exist (the Quick Diagnostic table with "If No -> Action" and the Scoring feedback loop of rating and iterating to 10/10), but the sequence is only implicit, fitting anchor 3 ("sequence present but checkpoints missing or implicit") better than anchor 4's "clear sequence".

3 / 5

Progressive Disclosure

The single bundle file (references/techniques.md, 432 lines, table of contents, no nested references) is real, one level deep, clearly signaled per section and summarized in the "Reference Files" section — good structure. It falls short of anchor 5 because the body itself carries substantial per-technique detail that overlaps the reference file and the per-section links are redundant (8 repeats of the same link), a minor organization gap consistent with anchor 4.

4 / 5

Total

15

/

20

Passed

Description

96%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 excellent: it states concrete capabilities, lists comprehensive natural trigger phrases, and explicitly covers both what the skill does and when to use it, with a clear disambiguation pointer to a sibling skill. The only soft spot is a couple of overly broad trigger terms that slightly raise conflict risk with communication/sales skills, and a minor typo ("Thats Right").

DimensionReasoningScore

Specificity

"Prepare and execute negotiations using tactical empathy, calibrated questions, and the Ackerman method" plus "Covers accusation audits, Black Swan discovery, and the 'Thats Right' technique" names multiple concrete capabilities with comprehensive coverage of the framework's methods. It is not merely naming the domain (3) and exceeds 'several specific actions; minor gaps' (4) since every core technique is enumerated.

5 / 5

Completeness

Explicitly answers both questions: what ("Prepare and execute negotiations using tactical empathy, calibrated questions, and the Ackerman method") and when ("Use when the user mentions 'salary negotiation'... Also trigger when preparing for vendor negotiations...") with concrete trigger phrases. This mirrors the 5 anchor example structure exactly; a 4 would have a weaker or less explicit 'when' clause.

5 / 5

Trigger Term Quality

Natural phrases users would actually say are comprehensively listed: "salary negotiation", "contract terms", "handling objections", "deal terms", "BATNA", "anchoring", plus situational triggers like "vendor negotiations" and "pricing disputes". Coverage includes synonyms and both lay and expert jargon, matching the 5 anchor; a 4 would be missing common variations, which is not the case here.

5 / 5

Distinctiveness Conflict Risk

Clear negotiation niche with mostly distinct triggers (BATNA, Ackerman, anchoring) and proactive disambiguation ("For persuasion in product/marketing, see influence-psychology"). However, broad triggers like "difficult conversation" and "handling objections" create minor overlap risk with general communication or sales skills, fitting anchor 4 (mostly distinct, minor overlap) rather than 5 (minimal conflict risk).

4 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

valeriibeck-star/claude-skills

Path

skills/negotiation/SKILL.md

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.