BF funnel-builder
Builds complete multi-channel revenue funnels adapted to any business model. Combines proven frameworks from elite operators: Yomi Denzel's viral top-of-funnel and deadline conversion system, Antoine Blanco's C4 business method (niche → offer → content → book → close → deliver) and Growth Operator model, and Andrew Tate's affiliate army and ticket ladder strategy. The agent detects the right niche, builds the full funnel architecture, writes the offer, sequences the emails, and maps every reconversion channel. Use when launching a new offer, rebuilding a funnel that doesn't convert, detecting a profitable niche, or setting up multi-channel retargeting.
As a process F 24/100 · Will not run — References files that are not bundled: references/masters_frameworks.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitymasters_frameworks.md:277Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Step 1: Define the offer with the creator (use C2 framework)
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6989 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/masters_frameworks.md
Process rating: all ten parameters 24/100
- 0Tools and files. 1 referenced file(s) missing: references/masters_frameworks.md
- 0Steps. Prose only: no discrete steps
- 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
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 6989 tokens
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 12 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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 660: enough signal without eating the budget
- +4Structure: 26 headings
- +4Has examples (21 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.