BF tilelang-dev-guide
Apply TileLang C++ development conventions and plan focused regression coverage. Use for C++ edits, style reviews or documentation, and before choosing tests for bug fixes, behavior changes, or test extensions. Not for merely running existing builds or tests or publishing PRs.
Apply TileLang C++ development conventions and plan focused regression coverage.
As a process F 29/100 · No process to follow — References files that are not bundled: ../../../docs/developer_guide/cpp_style.md, ../../../docs/developer_guide/testing_style.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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../docs/developer_guide/cpp_style.md - warning
missing-refreference to a missing file: ../../../docs/developer_guide/testing_style.md
Process rating: all ten parameters 29/100
- 0Tools and files. 2 referenced file(s) missing: ../../../docs/developer_guide/cpp_style.md, ../../../docs/developer_guide/testing_style.md
- 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. 2 mutating operations with no state check
- 50Steps. 2 steps
- 50When it triggers. No condition that starts the skill
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 301 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
- +5Description has no quoted example phrases that should trigger the skill
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 277: enough signal without eating the budget
- +4Structure: 3 headings
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.