AF ethical-acquisition
Turn a confirmed Offer Brief and Payable Test Plan into a small, policy-compliant acquisition plan with staged human-reviewed assets and a specific approval checkpoint. Use before outreach, a listing, a partnership request, public content, or any buyer-facing acquisition action.
Turn a confirmed Offer Brief and Payable Test Plan into a small, policy-compliant acquisition plan with staged human-reviewed assets and a specific approval…
As a process F 55/100 · Will not run — References files that are not bundled: references/approval-gates.md
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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/approval-gates.md
Process rating: all ten parameters 55/100
- 0Tools and files. 1 referenced file(s) missing: references/approval-gates.md
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1861 tokens
- 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 279: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 12 items
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.