SKILLEMALL.ai

BF tilegym-cutile-python

Expert cuTile programming assistant. Write high-performance GPU kernels using cuTile's tile-based programming model with proper validation and optimization. Supports deep agent orchestration for complex multi-kernel tasks.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 4 887 tokens Open the sourceclawhub.ai analyzed 35 h ago

Expert cuTile programming assistant.

As a process F 30/100 · Will not run — References files that are not bundled: guidelines/01_implementation_lessons.md, guidelines/02_code_generation_rules.md, guidelines/03_concepts.md

ProcedureSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
F
30/100
Will not run
References files that are not bundled: guidelines/01_implementation_lessons.md, guidelines/02_code_generation_rules.md, guidelines/03_concepts.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: guidelines/01_implementation_lessons.md
  • warning missing-ref reference to a missing file: guidelines/02_code_generation_rules.md
  • warning missing-ref reference to a missing file: guidelines/03_concepts.md
  • warning missing-ref reference to a missing file: examples/tilegym_and_examples_guide.md
  • warning missing-ref reference to a missing file: orchestration/workflow.md
  • warning missing-ref reference to a missing file: orchestration/overview.md

Process rating: all ten parameters 30/100

Will not run. References files that are not bundled: guidelines/01_implementation_lessons.md, guidelines/02_code_generation_rules.md, guidelines/03_concepts.md
  • 0Tools and files. 6 referenced file(s) missing: guidelines/01_implementation_lessons.md, guidelines/02_code_generation_rules.md, guidelines/03_concepts.md
  • 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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 60Steps. 117 steps, 4 vague phrases
  • 70Execution cost. Instruction body is 4887 tokens
  • 100Consistency. Name and required fields are in place
  • low 13 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (7 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)
  • +3Output format is not stated: the model decides each time
  • -218 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 222: enough signal without eating the budget
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 117 items
  • +4Has examples (4 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.