BF conditional-customer-success
Guide recurring human-relationship practices — success plans, health evidence, renewal and expansion signals, QBRs, handoffs, escalation, and closed-loop Voice of Customer. Do not use this skill for products without accounts, renewals, QBRs, or a customer-success team, including some internal tools, pure transactional products without recurring relationships, and public services without account-based engagement. Load only when the product context includes a recurring human relationship; decline or route away otherwise.
Guide recurring human-relationship practices — success plans, health evidence, renewal and expansion signals, QBRs, handoffs, escalation, and closed-loop…
As a process F 52/100 · Will not run — References files that are not bundled: ../product-analytics-and-measurement/SKILL.md, ../product-adoption/SKILL.md, ../product-experimentation/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../product-analytics-and-measurement/SKILL.md - warning
missing-refreference to a missing file: ../product-adoption/SKILL.md - warning
missing-refreference to a missing file: ../product-experimentation/SKILL.md - warning
missing-refreference to a missing file: ../go-to-market/SKILL.md - warning
missing-refreference to a missing file: ../crm/SKILL.md
Process rating: all ten parameters 52/100
- 0Tools and files. 5 referenced file(s) missing: ../product-analytics-and-measurement/SKILL.md, ../product-adoption/SKILL.md, ../product-experimentation/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 53 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3895 tokens
- 100Running it twice. No mutating operations
- 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
- low No test case covers injection arriving through data
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
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 524: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 53 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.