AF remix-v2-forms-review
Reviews Remix v2 form code for manual fetch() mutations, native <form> misuse, wrong useNavigation/useFetcher choice, missing pending state, unbounded uploads, and intent-pattern violations. Use when reviewing form/mutation code in a Remix v2 codebase.
As a process F 38/100 · Will not run — References files that are not bundled: ../remix-v2-forms/SKILL.md, ../../../beagle-core/skills/review-verification-protocol/SKILL.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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../remix-v2-forms/SKILL.md - warning
missing-refreference to a missing file: ../../../beagle-core/skills/review-verification-protocol/SKILL.md
Process rating: all ten parameters 38/100
- 0Tools and files. 2 referenced file(s) missing: ../remix-v2-forms/SKILL.md, ../../../beagle-core/skills/review-verification-protocol/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 47 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2228 tokens
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (17 tags): a typed call is more reliable
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
- +1No license
- +2Single-language instructions
- +3Description length 252: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 47 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.