SKILLEMALL.ai

BC managing-third-party-vendor-risk

Build and run a third-party/vendor risk management (TPRM) program aligned to NIST SP 800-161 C-SCRM: inventory and tier vendors, issue SIG/CAIQ questionnaires, review SOC 2/ISO 27001 evidence, set contractual right-to-audit clauses, monitor vendors continuously, and offboard securely. Use when assessing a new vendor, standing up a vendor-risk program, tiering a portfolio, reviewing a SOC 2/CAIQ, or writing security terms into a contract.

mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 5 files · 1 script body ≈ 1 939 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Build and run a third-party/vendor risk management (TPRM) program aligned to NIST SP 800-161 C-SCRM: inventory and tier vendors, issue SIG/CAIQ…

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

GeneratorAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
64/100
Has gaps
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
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: 5. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "domain"
    • note frontmatter-key unknown frontmatter key "subdomain"
    • note frontmatter-key unknown frontmatter key "nist_csf"
    • note frontmatter-key unknown frontmatter key "mitre_attack"

    Process rating: all ten parameters 64/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 39 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1939 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)
    • +4No input/output examples
    • -41 reference files, but SKILL.md never points to them: the model will not open them
    • +2Single-language instructions
    • +3Description length 441: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 39 items
    • +3Output format is stated explicitly
    • +3All 1 scripts are documented
    • +1License stated

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