SKILLEMALL.ai

BD Negotiation Mastery

Complete negotiation system for business deals, salary talks, vendor contracts, partnerships, and high-stakes conversations. Combines multiple proven frameworks (FBI tactical empathy, Harvard princ...

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 5 720 tokens Open the sourcegithub.com analyzed 2 d ago

Complete negotiation system for business deals, salary talks, vendor contracts, partnerships, and high-stakes conversations.

As a process D 48/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, consistency

ProcedureSales and CRMtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Consistency w 8
40
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning body-long SKILL.md body ≈ 5720 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 48/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 40Consistency. Frontmatter name (Negotiation Mastery) differs from the folder (afrexai-negotiation-mastery)
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Execution cost. Instruction body is 5720 tokens
  • 85Steps. 178 steps, 2 vague phrases
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 200: enough signal without eating the budget
  • +4Structure: 36 headings
  • +3Step-by-step instructions: 178 items
  • +4Has examples (3 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.