BD pinkr-crm
品氪后台 API 调用工具，用于 AI 模型自动调用品氪 CRM 系统。所有接口均为 POST，参数通过 JSON 请求体传递，包含会员查询等常用接口。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationSales and CRMInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "required_env_vars" - note
frontmatter-keyunknown frontmatter key "primary_credential"
Process rating: all ten parameters 49/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 (pinkr-crm) differs from the folder (pinkr-admin-api)
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 33 steps
- 100Execution cost. Instruction body is 406 tokens
- 100Running it twice. No mutating operations
- low 10 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)
- +3Description length 76: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 13 headings
- +3Step-by-step instructions: 33 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.
External checks
ClawHub: suspicious
This CRM skill has a legitimate purpose, but it gives an agent broad authenticated CRM access and can expose CRM bearer tokens outside the intended service boundary.
LLM: suspicious (high) · VirusTotal: · 29 May 2026