BF iii-functions-and-triggers
Registers functions and triggers on the iii engine across TypeScript, Python, and Rust. Use when creating workers, registering function handlers, binding triggers, or invoking functions across languages.
As a process F 54/100 · Will not run — References files that are not bundled: ../references/functions-and-triggers.js, ../references/functions-and-triggers.py, ../references/functions-and-triggers.rs
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: ../references/functions-and-triggers.js - warning
missing-refreference to a missing file: ../references/functions-and-triggers.py - warning
missing-refreference to a missing file: ../references/functions-and-triggers.rs
Process rating: all ten parameters 54/100
- 0Tools and files. 3 referenced file(s) missing: ../references/functions-and-triggers.js, ../references/functions-and-triggers.py, ../references/functions-and-triggers.rs
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (iii-functions-and-triggers) differs from the folder (iii-functions-triggers)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 38 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1428 tokens
- 100Running it twice. No mutating operations
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 203: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 38 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.