AF alibabacloud-ecs-vpc-publicnetwork-troubleshoot
Use when an ECS instance cannot reach the internet, its public IP is unreachable, ping to the public network times out, a security group blocks public access, or a VPC cloud service (DataWorks / SAE / ACK) cannot access the public network. Diagnoses Alibaba Cloud ECS public network access and VPC cloud service public egress: ECS public IP reachability and security-group blocking (auto-handling the NAT-gateway egress path for instances without a public IP), plus NAT gateway / SNAT / route / EIP checks for DataWorks, SAE, ACK and others. Triggers: "ECS public network access diagnosis", "ECS public IP reachability", "ECS security group blocking public access", "ECS cannot access the public network", "ECS NAT gateway SNAT egress troubleshooting", "VPC cloud service public network access", "DataWorks cannot access the public network", "SAE public network egress failure", "ACK public network unreachable", "VPC NAT gateway SNAT route EIP check"
Use when an ECS instance cannot reach the internet, its public IP is unreachable, ping to the public network times out, a security group blocks public access…
As a process F 46/100 · Will not run — References files that are not bundled: scripts/.sts_cache.json
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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/.sts_cache.json
Process rating: all ten parameters 46/100
- 0Tools and files. 1 referenced file(s) missing: scripts/.sts_cache.json
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 55 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3295 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 951: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 10 example trigger phrases
- +4Structure: 18 headings
- +3Step-by-step instructions: 55 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.