DB arbitration-clause-design-and-review-hafez-virjee
(no description)
Use this skill to help users draft, review and stress-test arbitration clauses in commercial contracts.
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, execution cost, running it twice
AnalyzerData and analyticsSales and CRMResearchtype and topics are labelled automatically from the skill text
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger - warning
body-longSKILL.md body ≈ 20104 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 10Execution cost. Instruction body is 20104 tokens: crowds the task out of the window
- 30Running it twice. 11 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 80When it triggers. States when to use and when not to
- 85Steps. 441 steps, 3 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 9 branches, has a failure section
- 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
- low 63 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
- +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 0: 120–800 characters recommended
- +2Single-language instructions
- +4Structure: 94 headings
- +3Step-by-step instructions: 441 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.