SKILLEMALL.ai
GitHub ↗ RU Sign in

AB alibabacloud-alb-ingress-doctor

Diagnose Alibaba Cloud ACK cluster ALB Ingress reconcile errors, Warning events, and configuration issues. Use this Skill when users report: ALB Ingress errors, reconcile failures, AlbConfig sync problems, Ingress not working, ALB configuration not taking effect, actions/conditions annotations not working as expected, certificate not updating, listener errors, or any ALB Ingress related abnormal behavior. Supports matching 61+ known error patterns from the knowledge base.

ClawHub Agent Skills author: alibabacloud-skills-team v0.0.1 MIT-0 10 files · 3 scripts body ≈ 2 466 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

Diagnose Alibaba Cloud ACK cluster ALB Ingress reconcile errors, Warning events, and configuration issues.

As a process B 74/100 · Nearly there — weak spots: running it twice, progress reporting

AnalyzerKubernetesFinanceInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
95
Quality 40%
95
Run on models
none yet
Process rating
B
74/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
When it triggers w 12
50
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

    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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Bash Read

    Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 74/100

    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 6 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 41 steps, 2 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2466 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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)
    • +2Single-language instructions
    • +3Description length 476: enough signal without eating the budget
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 41 items
    • +3Output format is stated explicitly
    • +4Has examples (11 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)
    • +3All 3 scripts are documented
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.

    External checks

    ClawHub: suspicious
    This diagnostic skill is mostly purpose-aligned, but it can fetch and persist kubeconfig credentials for every running ACK cluster without tight scoping or explicit per-cluster approval.
    LLM: suspicious (high) · 28 Jul 2026