BB alibabacloud-flink-knowledge
阿里云实时计算 Flink 版专家助手。Use when you need expert assistance with Alibaba Cloud Realtime Compute for Flink (阿里云实时计算 Flink 版), including product parameters, engine versions, billing information, general troubleshooting, Flink SQL generation (DDL/pipeline/risk-monitoring scenarios), and explicit file output requests. Covers: parameter/version/billing queries, problem diagnosis, SQL generation, file output.
阿里云实时计算 Flink 版专家助手。Use when you need expert assistance with Alibaba Cloud Realtime Compute for Flink (阿里云实时计算 Flink 版), including product parameters, engine…
As a process B 65/100 · Nearly there — weak spots: when it triggers, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5555 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 65/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Steps. 57 steps, 4 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5555 tokens
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- low The response is described with custom markup (5 tags): a typed call is more reliable
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)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 402: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 57 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.