AB franchise-decoder
Decode a franchise offering before you sign away a decade — the earnings claims and their absence, the territory that is not exclusive, the renewal terms that expire your equity, the mandatory-supplier margins, and the validation calls that reveal what the brochure will not. Use when asked to evaluate a franchise, review an FDD or franchise agreement, is this franchise a good deal, or what to ask existing franchisees. Produces a clause-by-clause decode organised by where the money leaks, the earnings-claim reality check, the validation-call script, and the walk-away list. Not legal or financial advice — a franchise lawyer reviews before any signature.
Decode a franchise offering before you sign away a decade — the earnings claims and their absence, the territory that is not exclusive, the renewal terms that…
As a process B 70/100 · Nearly there — weak spots: when it triggers, failures and branches, progress reporting
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 70/100
- 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
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1646 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 659: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 28 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.