BF laravel-dusk-skill
Generates Laravel Dusk browser tests in PHP. Chrome-based E2E testing for Laravel apps. Use when user mentions "Dusk", "Laravel Dusk", "$browser->visit", "DuskTestCase". Triggers on: "Laravel Dusk", "Dusk test", "$browser->visit", "DuskTestCase".
Generates Laravel Dusk browser tests in PHP.
As a process F 24/100 · No process to follow — References files that are not bundled: ../shared/testmu-cloud-reference.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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
- warning
missing-refreference to a missing file: ../shared/testmu-cloud-reference.md - note
frontmatter-keyunknown frontmatter key "languages"
Process rating: all ten parameters 24/100
- 0Tools and files. 1 referenced file(s) missing: ../shared/testmu-cloud-reference.md
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 70When it triggers. States when to use, but not when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1157 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
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 246: enough signal without eating the budget
- +4Structure: 10 headings
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (2 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.