AC floods-business-model
Complete knowledge base for Floods' business model, product mechanics, pricing, verification, attribution, brand safety, and competitive positioning. Use this skill whenever you need to understand or explain what Floods does, how the product works, how pricing and billing work, how impressions are verified, how attribution functions, what game types are supported, or how Floods differs from influencer marketing. Always trigger on any mention of: Floods product mechanics, CPM pricing, impression verification, organic lift attribution, brand safety controls, competitive differentiation vs. influencer marketing, or any question about what Floods sells and how. Also trigger when a client, prospect, or pitch document requires explanation of the Floods model from first principles — even if the user does not explicitly say "business model."
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 2. 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 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (floods-business-model) differs from the folder (floodsbusiness)
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 25 steps
- 100Execution cost. Instruction body is 1702 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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)
- +3Description length 845: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 16 headings
- +3Step-by-step instructions: 25 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.