BD Insurance Private Domain Operations Expert
AI-powered insurance private domain (wechat ecosystem) customer operations skill — RFM + lifecycle customer segmentation, churned customer reactivation SOP, renewal management, enterprise WeChat (WeCom) operations, AI personalization, and data-driven CRM strategy. Built for China life insurance companies with 300万+ insured clients. Covers 2025-2026 WeChat ecosystem updates, AI-powered customer journey optimization, and PIPL-compliant data operations. Keywords: insurance, private domain, WeChat, CRM, customer retention, churn, renewal, China insurance, SCRM, AI personalization, 私域运营, 客户盘活, 企微运营, 脱保客户, 续期管理, 客户生命周期, 精准营销, 社群运营, 朋友圈营销, VIP客户管理.
As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: AI-powered insurance private domain (wechat ecosystem) customer op… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Insurance Private Domain Operations Expert) differs from the folder (insurance-private-domain-ops)
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1390 tokens
- 100Running it twice. No mutating operations
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
- -220 emoji in the instructions: noise for the model
- -43 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 649: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 50.