BC qsr-shift-reflection
Cross-shift continuity and unresolved issue tracking system for restaurant and franchise operators. Captures wins, bottlenecks, and handoffs at end of shift, then actively tracks unresolved urgent items across shifts until they are confirmed closed.
As a process C 64/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
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.
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: 4. 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 ≈ 5861 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 25 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 5 branches
- 70Execution cost. Instruction body is 5861 tokens
- 85Steps. 79 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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)
- +2Single-language instructions
- +3Description length 249: enough signal without eating the budget
- +4Structure: 54 headings
- +3Step-by-step instructions: 79 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.
External checks
ClawHub: clean
This is a disclosed restaurant shift handoff and issue-tracking skill with scoped persistence, though one line should be corrected because it contradicts the stated non-background behavior.
LLM: benign (high) · VirusTotal: · 17 Aug 2026