BF customer-acquisition-automation
Customer-acquisition desk for indie tools. Collects public pain-point leads from Reddit, X, and public competitor threads, writes channel-native drafts, and builds a human approval queue. Does not post until the user confirms. Use when the user says run acquisition, today's acquisition, start the acquisition pipeline, collect promo leads, or draft outreach.
Customer-acquisition desk for indie tools.
As a process F 51/100 · Will not run — References files that are not bundled: references/lead-pool.csv, assets/daily-content-[YYYY-MM-DD].md, references/approval-log.csv
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/lead-pool.csv - warning
missing-refreference to a missing file: assets/daily-content-[YYYY-MM-DD].md - warning
missing-refreference to a missing file: references/approval-log.csv - warning
missing-refreference to a missing file: references/publish-log.csv - warning
missing-refreference to a missing file: references/feedback-log.csv
Process rating: all ten parameters 51/100
- 0Tools and files. 5 referenced file(s) missing: references/lead-pool.csv, assets/daily-content-[YYYY-MM-DD].md, references/approval-log.csv
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 13 mutating operations with no state check
- 70Failures and branches. 5 branches
- 100Steps. 20 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1073 tokens
- 100Progress reporting. Reports progress
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 359: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 20 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.