SKILLEMALL.ai
GitHub ↗ RU Sign in

AB auto-dealer-marketing

When the user wants to create, optimize, or plan automotive dealership marketing — including inventory merchandising, VDP copy, seasonal campaigns, conquest ads, service retention, OEM co-op compliant creative, local SEO, database mining, or BDC scripts. Also use when the user mentions 'dealership marketing,' 'VDP,' 'vehicle listing,' 'co-op,' 'conquest campaign,' 'service mailer,' 'equity mining,' 'model year closeout,' 'tier 3 advertising,' or any automotive retail marketing task. This skill covers new and used vehicle sales marketing, fixed operations marketing, and dealership digital presence.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 2 files body ≈ 4 226 tokens Open the sourcegithub.com↗ analyzed 2 d ago

When the user wants to create, optimize, or plan automotive dealership marketing — including inventory merchandising, VDP copy, seasonal campaigns, conquest…

As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, running it twice

GeneratorMarketingtype 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
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
B
65/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 65/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 8 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70Execution cost. Instruction body is 4226 tokens
    • 85Steps. 137 steps, 3 vague phrases
    • 100Tools and files. No external tools needed
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 604: enough signal without eating the budget
    • +4Structure: 51 headings
    • +3Step-by-step instructions: 137 items
    • +3Output format is stated explicitly
    • +4Has examples (7 code blocks)

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