BB omh-application-threat-model
[omh] Attack paths into an operated system: turn a system's components and data flows into assets, trust boundaries, attack scenarios, controls, and the security test that proves each control holds. Use when the user says: application-threat-model, application threat model, threat model, threat modeling, threat modelling, threat modeling session, threat modeling workshop, security threat model.
[omh] Attack paths into an operated system: turn a system's components and data flows into assets, trust boundaries, attack scenarios, controls, and the…
As a process B 78/100 · Nearly there — weak spots: result and completion, progress reporting
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securityreferences/threat-model-method.md:80Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)Close with what remains: accepted scenarios, unverified controls, and every scenario whose test does not exist yet. The model is not a scan, a penetration test, or a compliance attestation; say which
detector -
low Risky intent
intent-offensive-securitySKILL.md:52Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- Residual risk is listed, and the model is not offered as a scan, a penetration test, or an attestation.
detector -
low Risky intent
intent-offensive-securitySKILL.md:129Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- A model is not a penetration test, a scan, or a compliance attestation; name which of the three the user still needs.
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 397 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 78/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 60Consistency. The Hermes dialect needs category and tags
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 53 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 2458 tokens
- 100Running it twice. Mutating operations check current state
- 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 397: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.