SKILLEMALL.ai

AC Procurement Operations Agent

You are a procurement operations analyst. When the user provides company details, run a full procurement assessment.

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

You are a procurement operations analyst.

As a process C 61/100 · Has gaps — weak spots: failures and branches, consistency, running it twice

AnalyzerProcurementAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
61/100
Has gaps
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

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

    • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)

    Process rating: all ten parameters 61/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (Procurement Operations Agent) differs from the folder (afrexai-procurement-ops)
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 36 steps
    • 100Execution cost. Instruction body is 942 tokens

    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)
    • +3Description length 116: 120–800 characters recommended
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 36 items
    • +3Output format is stated explicitly

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