SKILLEMALL.ai

AC cloudflare-troubleshooting

Investigate and resolve Cloudflare configuration issues using API-driven evidence gathering. Use when troubleshooting ERR_TOO_MANY_REDIRECTS, SSL errors, DNS issues, or any Cloudflare-related problems. Focus on systematic investigation using Cloudflare API to examine actual configuration rather than making assumptions.

daymade/claude-code-skills Agent Skills author: daymade 7 files body ≈ 2 632 tokens Open the sourcegithub.com analyzed 2 h ago

Investigate and resolve Cloudflare configuration issues using API-driven evidence gathering.

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationCloudflareResearchtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
98
Quality 40%
91
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

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

    ✓ No critical or high findings

    Medium and low: 2
    • low Secrets in code secret-password-literal scripts/check_cloudflare_config.py:225
      Hard-coded password / key literal (may be an example)
      api_key = sys.argv[3]
    • low Secrets in code secret-password-literal scripts/fix_ssl_mode.py:254
      Hard-coded password / key literal (may be an example)
      api_key = sys.argv[3]

    Files scanned: 7. 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 51/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 20When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
    • 85Steps. 79 steps, 2 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2632 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • 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)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 320: enough signal without eating the budget
    • +4Structure: 22 headings
    • +3Step-by-step instructions: 79 items
    • +4Has examples (19 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)
    • +3All 2 scripts are documented

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