SKILLEMALL.ai

AB linkedin-employee-advocacy

Stand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on "employee advocacy", "get the team posting", "scale LinkedIn across team", "advocacy ROI". Not for planning one person's own calendar (use linkedin-content-planner).

sergebulaev/linkedin-skills Agent Skills author: sergebulaev MIT 4 files body ≈ 1 418 tokens Open the sourcegithub.com↗ analyzed 14 d ago

Stand up and run a LinkedIn employee advocacy program for a marketing or sales team.

As a process B 76/100 · Nearly there — weak spots: failures and branches, running it twice, progress reporting

ProcedureInfrastructureData and analyticsMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
96
Run on models
none yet
Process rating
B
76/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: linkedin-employee-advocacy (sergebulaev/linkedin-skills)

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: 4. 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 76/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 3 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 70 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1418 tokens
    • low 11 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

    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 407: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 70 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (3 of 3)

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