BF onepilot
Connect local agents to OnePilot for event recommendations, optional mailbox-code and calendar availability help, consent-based memory and feedback, application form support, and organizer-only event management or registration export.
Connect local agents to OnePilot for event recommendations, optional mailbox-code and calendar availability help, consent-based memory and feedback…
As a process F 42/100 · Will not run — References files that are not bundled: groupQrImageUrl
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 13. 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
body-longSKILL.md body ≈ 6638 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: groupQrImageUrl
Process rating: all ten parameters 42/100
- 0Tools and files. 1 referenced file(s) missing: groupQrImageUrl
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (onepilot) differs from the folder (onepilot-cli)
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 6638 tokens
- 85Steps. 58 steps, 1 vague phrases
- 100Failures and branches. 20 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
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
- +2Single-language instructions
- +3Description length 234: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 58 items
- +4Has examples (30 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.