BF review-engineering-docs
Review Chinese engineering and construction documents in DOCX, text-based PDF, XLSX, or XLSM format. Use when asked to extract project facts, contacts, schedules, quantities, safety measures, missing items, conflicting values, or review questions from construction plans, technical proposals, tender materials, supplier files, and similar project documents. Produces a local, traceable pre-review report and never invents missing engineering data.
Review Chinese engineering and construction documents in DOCX, text-based PDF, XLSX, or XLSM format.
As a process F 45/100 · Will not run — References files that are not bundled: references/review-rules.md, references/review-schema.md, scripts/review_engineering_doc.py
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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/review-rules.md - warning
missing-refreference to a missing file: references/review-schema.md - warning
missing-refreference to a missing file: scripts/review_engineering_doc.py - warning
missing-refreference to a missing file: scripts/requirements.txt
Process rating: all ten parameters 45/100
- 0Tools and files. 4 referenced file(s) missing: references/review-rules.md, references/review-schema.md, scripts/review_engineering_doc.py
- 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
- 100Steps. 36 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1065 tokens
- 100Running it twice. Mutating operations check current state
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
- +1No license
- +2Single-language instructions
- +3Description length 447: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.