AC fibek-collections
Interact with the Fibek B2B collections platform API — manage invoices, clients, payment agreements, campaigns, and financial metrics
As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, consistency, running it twice
IntegrationMarketingInfrastructureData and analyticstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 2. 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")
Process rating: all ten parameters 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (fibek-collections) differs from the folder (fibek-cleo)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 48 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 2488 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +1No license
- +2Single-language instructions
- +3Description length 133: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 48 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: suspicious
This skill fits its collections-platform purpose, but it can send sensitive customer communications and execute campaigns without clear final approval steps.
LLM: suspicious (high) · VirusTotal: · 29 May 2026