AF crm-analysis
Analyze outbound campaign performance, reply rates, open-to-reply conversion, follow-up prioritization, platform attribution, and deliverability using OutboundSync engagement signals in HubSpot or Salesforce. Use when someone asks about campaign replies, which sequences are working, who to follow up with, bounce or unsubscribe trends, or how platforms like Instantly, Smartlead, EmailBison, or HeyReach are performing. Also handles exploratory HeyReach social signal analysis. Read-only, local-only, deterministic preflight routing.
As a process F 62/100 · Will not run — References files that are not bundled: ../../SECURITY.md, ../../LICENSE
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: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../SECURITY.md - warning
missing-refreference to a missing file: ../../LICENSE
Process rating: all ten parameters 62/100
- 0Tools and files. 2 referenced file(s) missing: ../../SECURITY.md, ../../LICENSE
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 76 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1752 tokens
- 100Running it twice. Mutating operations check current state
- 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)
- +2Single-language instructions
- +3Description length 534: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 76 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.