BC zayn-cross-functional-collaboration
处理跨部门协同、进度确认、信息补充、风险同步和内部沟通表达，区分已确认事实、用户判断和待确认信息，避免过早承诺、推责、情绪化表达和未经确认的责任认定。
处理跨部门协同、进度确认、信息补充、风险同步和内部沟通表达，区分已确认事实、用户判断和待确认信息，避免过早承诺、推责、情绪化表达和未经确认的责任认定。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
Proceduretype 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: 9. 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")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 78 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 787 tokens
- 100Running it twice. No mutating operations
- low 15 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 75: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 23 headings
- +3Step-by-step instructions: 78 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: clean
This is a benign collaboration-writing skill that helps structure internal coordination messages and does not request credentials, tool execution, persistence, or broad data access.
LLM: benign (high) · VirusTotal: · 1 Aug 2026