SKILLEMALL.ai
GitHub ↗ RU Sign in

AC Objection Handling — Turn Resistance Into Revenue

Overcome buyer objections using proven frameworks. Every objection is a buying signal — they're considering it, they just need clarity. Sources: Gong.io (AI sales data), Thriving Tech (sales method...

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 2 139 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Overcome buyer objections using proven frameworks.

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

ProcedureSales and CRMCustomer supporttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

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

    Process rating: all ten parameters 59/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 6 mutating operations with no state check
    • 40Consistency. Frontmatter name (Objection Handling — Turn Resistance Into Revenue) differs from the folder (objection-handling)
    • 50When it triggers. No condition that starts the skill
    • 100Tools and files. No external tools needed
    • 100Steps. 50 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 100Execution cost. Instruction body is 2139 tokens
    • 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
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 200: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 50 items

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