BF djtu-vehicle-eng-thesis-check
Activated ONLY by the explicit slash command /djtu-vehicle-eng-thesis-check. Do NOT activate on generic phrases like "check my thesis", "format my paper", or "convert to Word". This skill validates and builds DJTU Vehicle Engineering thesis documents from a Markdown draft into a formatted .docx file.
Activated ONLY by the explicit slash command /djtu-vehicle-eng-thesis-check.
As a process F 52/100 · Will not run — References files that are not bundled: references/requirements.txt, references/formatting-spec.md, references/glossary.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/requirements.txt - warning
missing-refreference to a missing file: references/formatting-spec.md - warning
missing-refreference to a missing file: references/glossary.md - warning
missing-refreference to a missing file: references/examples/chapter-sample.md - warning
missing-refreference to a missing file: references/examples/bad-vs-good.md
Process rating: all ten parameters 52/100
- 0Tools and files. 5 referenced file(s) missing: references/requirements.txt, references/formatting-spec.md, references/glossary.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 13 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1227 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 301: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.